{
  "$schema": "https://ndcodex.com/schemas/object/v1.json",
  "id": "codex://object/nd-codex-object-classification",
  "archive_id": "nd-codex-object-classification",
  "slug": "nd-codex-object-classification",
  "url": "https://ndcodex.com/objects/nd-codex-object-classification/",
  "type": "codex",
  "object_form": null,
  "title": "ND Codex Object Classification",
  "summary": "The ND Codex archive organizes all entries into eight object classes. Each class describes the role an object plays in the archive, not the topic it discusses. Objects may share themes or subject matter, but each object…",
  "content_text": "The ND Codex archive organizes all entries into eight object classes.\n\nEach class describes the role an object plays in the archive, not the topic it discusses.\n\nObjects may share themes or subject matter, but each object belongs to exactly one class.\n\nThis classification keeps the archive readable, navigable, and structurally stable.\n\n---\n\nThe Eight Object Classes\n\nSignal\n\nShort, high-clarity statements intended for immediate interpretation and use.\n\nSignals act as compressed transmissions.\n\nThey are designed to communicate meaning quickly and clearly without requiring extended context.\n\nTypical characteristics:\n\nconcise\n\ndirect\n\nimmediately interpretable\n\nhigh signal-to-noise ratio\n\nSignals often function as entry points into larger structures.\n\n---\n\nFragment\n\nSmall units of meaning meant to remain useful alone while remaining expandable later.\n\nFragments preserve ideas before they fully develop into larger structures such as scrolls or codex entries.\n\nTypical characteristics:\n\nincomplete but self-contained\n\nconceptually dense\n\nexpandable\n\nportable\n\nFragments frequently become seeds for future work.\n\n---\n\nField Log\n\nDated records describing system condition, constraints, and directional adjustments.\n\nField logs document what is happening in the system over time.\n\nTypical characteristics:\n\ntimestamped\n\nobservational\n\noperational\n\nsituational\n\nField logs provide context for how the archive evolves.\n\n---\n\nArtifact\n\nPhysical or digital outputs that document what was made and how it holds up.\n\nArtifacts are evidence objects.\n\nTypical characteristics:\n\nvisual or material focus\n\ndocumentation of process\n\ndemonstration of construction\n\nobservable results\n\nArtifacts answer:\n\nwhat exists\n\nhow it was made\n\nwhat condition it holds\n\n---\n\nScroll\n\nExtended writing that carries context, sequence, and sustained argument.\n\nScrolls represent narrative or conceptual movement.\n\nTypical characteristics:\n\nstructured progression\n\nextended reasoning or storytelling\n\nthematic continuity\n\nlongform composition\n\nA scroll should feel like a path the reader follows.\n\n---\n\nCodex\n\nCore references that define stable standards for structure, classification, or publishing.\n\nCodex entries act as structural anchors for the archive.\n\nTypical characteristics:\n\ndefinitional\n\nstable\n\nprocedural\n\narchitectural\n\nCodex entries change rarely and provide shared reference points for the system.\n\n---\n\nLoremap\n\nPlace-anchored field definitions mapping terrain, symbolic layers, and recurring signals.\n\nLoremaps organize knowledge spatially rather than narratively.\n\nTypical characteristics:\n\ngeographic anchoring\n\nsymbolic geography\n\nlayered interpretation\n\nlong-term observation\n\nLoremaps help readers understand how place shapes signal.\n\n---\n\nNexus\n\nCurated reading chains that connect multiple objects into coherent narrative movement.\n\nA nexus functions as a navigation structure.\n\nTypical characteristics:\n\nlinking\n\nsequencing\n\ncontextualizing\n\nguiding interpretation\n\nNexus entries do not introduce new objects;\n\nthey reveal relationships between existing ones.\n\n---\n\nStructural Principle\n\nEvery object belongs to exactly one class.\n\nObject classes describe role, not topic.\n\nFor example:\n\na collage may be an artifact\n\na reflection about that collage may be a field log\n\nan extended essay about the process may be a scroll\n\nEach class contributes a different function within the archive.\n\n---\n\nArchive Layers\n\nThe eight classes naturally organize into four operational layers.\n\nTransmission\n\nsignal\n\nfragment\n\nImmediate meaning units.\n\n---\n\nDocumentation\n\nartifact\n\nfield-log\n\nRecords of evidence and process.\n\n---\n\nStructure\n\nscroll\n\ncodex\n\nExtended or stable frameworks.\n\n---\n\nNavigation\n\nloremap\n\nnexus\n\nWays to traverse the archive.\n\n---\n\nImplementation\n\nCarrier Pigeon ingest reads the object_type field and routes the object to the appropriate collection.\n\nExample routing:\n\nscroll → src/content/scrolls/\n\nloremap → src/content/loremaps/\n\nartifact → src/content/artifacts/\n\nfield-log → src/content/field-logs/\n\ncodex → src/content/codex/\n\nfragment → src/content/fragments/\n\nnexus → src/content/nexus/\n\nsignal → src/content/signals/\n\nThis routing allows the archive to grow while maintaining clear structural boundaries.\n\n---\n\nSummary\n\nThe ND Codex classification system supports four forms of knowledge:\n\ntransmission\n\nevidence\n\nstructure\n\nnavigation\n\nTogether these allow the archive to function not merely as a repository, but as a living knowledge system.",
  "content_markdown": "# ND Codex Object Classification\n\nThe ND Codex archive organizes all entries into eight object classes.  \nEach class describes the **role an object plays in the archive**, not the topic it discusses.\n\nObjects may share themes or subject matter, but each object belongs to **exactly one class**.\n\nThis classification keeps the archive readable, navigable, and structurally stable.\n\n---\n\n# The Eight Object Classes\n\n## Signal\n\nShort, high-clarity statements intended for immediate interpretation and use.\n\nSignals act as **compressed transmissions**.  \nThey are designed to communicate meaning quickly and clearly without requiring extended context.\n\nTypical characteristics:\n\n- concise\n- direct\n- immediately interpretable\n- high signal-to-noise ratio\n\nSignals often function as **entry points into larger structures**.\n\n---\n\n## Fragment\n\nSmall units of meaning meant to remain useful alone while remaining expandable later.\n\nFragments preserve ideas before they fully develop into larger structures such as scrolls or codex entries.\n\nTypical characteristics:\n\n- incomplete but self-contained\n- conceptually dense\n- expandable\n- portable\n\nFragments frequently become seeds for future work.\n\n---\n\n## Field Log\n\nDated records describing system condition, constraints, and directional adjustments.\n\nField logs document **what is happening in the system over time**.\n\nTypical characteristics:\n\n- timestamped\n- observational\n- operational\n- situational\n\nField logs provide **context for how the archive evolves**.\n\n---\n\n## Artifact\n\nPhysical or digital outputs that document what was made and how it holds up.\n\nArtifacts are **evidence objects**.\n\nTypical characteristics:\n\n- visual or material focus\n- documentation of process\n- demonstration of construction\n- observable results\n\nArtifacts answer:\n\n- what exists\n- how it was made\n- what condition it holds\n\n---\n\n## Scroll\n\nExtended writing that carries context, sequence, and sustained argument.\n\nScrolls represent **narrative or conceptual movement**.\n\nTypical characteristics:\n\n- structured progression\n- extended reasoning or storytelling\n- thematic continuity\n- longform composition\n\nA scroll should feel like **a path the reader follows**.\n\n---\n\n## Codex\n\nCore references that define stable standards for structure, classification, or publishing.\n\nCodex entries act as **structural anchors for the archive**.\n\nTypical characteristics:\n\n- definitional\n- stable\n- procedural\n- architectural\n\nCodex entries change rarely and provide **shared reference points** for the system.\n\n---\n\n## Loremap\n\nPlace-anchored field definitions mapping terrain, symbolic layers, and recurring signals.\n\nLoremaps organize knowledge spatially rather than narratively.\n\nTypical characteristics:\n\n- geographic anchoring\n- symbolic geography\n- layered interpretation\n- long-term observation\n\nLoremaps help readers understand **how place shapes signal**.\n\n---\n\n## Nexus\n\nCurated reading chains that connect multiple objects into coherent narrative movement.\n\nA nexus functions as a **navigation structure**.\n\nTypical characteristics:\n\n- linking\n- sequencing\n- contextualizing\n- guiding interpretation\n\nNexus entries do not introduce new objects;  \nthey **reveal relationships between existing ones**.\n\n---\n\n# Structural Principle\n\nEvery object belongs to exactly one class.\n\nObject classes describe **role**, not topic.\n\nFor example:\n\n- a collage may be an **artifact**\n- a reflection about that collage may be a **field log**\n- an extended essay about the process may be a **scroll**\n\nEach class contributes a different function within the archive.\n\n---\n\n# Archive Layers\n\nThe eight classes naturally organize into four operational layers.\n\n## Transmission\n\nsignal  \nfragment  \n\nImmediate meaning units.\n\n---\n\n## Documentation\n\nartifact  \nfield-log  \n\nRecords of evidence and process.\n\n---\n\n## Structure\n\nscroll  \ncodex  \n\nExtended or stable frameworks.\n\n---\n\n## Navigation\n\nloremap  \nnexus  \n\nWays to traverse the archive.\n\n---\n\n# Implementation\n\nCarrier Pigeon ingest reads the `object_type` field and routes the object to the appropriate collection.\n\nExample routing:\n\nscroll → src/content/scrolls/  \nloremap → src/content/loremaps/  \nartifact → src/content/artifacts/  \nfield-log → src/content/field-logs/  \ncodex → src/content/codex/  \nfragment → src/content/fragments/  \nnexus → src/content/nexus/  \nsignal → src/content/signals/\n\nThis routing allows the archive to grow while maintaining clear structural boundaries.\n\n---\n\n# Summary\n\nThe ND Codex classification system supports four forms of knowledge:\n\n- transmission\n- evidence\n- structure\n- navigation\n\nTogether these allow the archive to function not merely as a repository, but as a **living knowledge system**.",
  "author": {
    "id": "nathan-davis",
    "name": "Nathan Davis",
    "designation": "Archive Operator",
    "role": "Archive Operator",
    "handle": "@nathandavis",
    "avatar": "/media/people/nathan-davis.jpg",
    "bio": "Designer, builder, and curator of the Codex Archive."
  },
  "contributors": [
    {
      "id": "nathan-davis",
      "name": "Nathan Davis",
      "designation": "Archive Operator",
      "role": "Archive Operator",
      "handle": "@nathandavis",
      "avatar": "/media/people/nathan-davis.jpg",
      "bio": "Designer, builder, and curator of the Codex Archive."
    }
  ],
  "date_published": "2026-03-15T04:51:09.923Z",
  "date_modified": "2026-03-15T04:51:09.923Z",
  "status": "published",
  "visibility": "public",
  "language": "en-US",
  "axes": {
    "scale": null,
    "depth": null,
    "focus": null,
    "function": null
  },
  "themes": [
    "taxonomy",
    "archive",
    "structure",
    "methodology"
  ],
  "constellations": [],
  "tags": [
    "taxonomy",
    "archive",
    "structure",
    "methodology"
  ],
  "keywords": [
    "Codex",
    "taxonomy",
    "archive",
    "structure",
    "methodology"
  ],
  "relations": [],
  "media": [],
  "capture": null
}