Part II · Context, Memory, and Artifacts
Files, Artifacts, Metadata, and Semantic Standing
Explains how files, artifacts, metadata, records, and projections carry different forms of semantic standing. Their typed relationships create durable continuity and a reconstructable knowledge graph across ordinary files.
WHAT A FILE REMEMBERS
1. Files are the durable body of the system
File-native intelligence means more than exporting model responses to Markdown. Files are the artifacts the person is making, the custody layer for exact sources, the stable addresses of bounded work, and the durable ground from which semantic situations are reconstructed.
They preserve identity, language, structure, decisions, lineage, plans, relationships, and evidence independently of one model process or provider. Mature file operations make the knowledge searchable, comparable, editable, versionable, archivable, and recoverable.
The model is temporary. The file environment preserves what the collaboration has built.
2. Four classes of durable ground
Diagram 1 · §2
Text equivalent
Canonical content → Canonical companion memory; Canonical content → Durable operation evidence; Canonical companion memory → Derived projections; Durable operation evidence → Derived projections.
Canonical content contains exact sources, artifacts, and accepted definitions of reusable practice. Companion memory describes stable purpose, structure, standing, and relationship. Operation evidence records consequential movements and effects. Derived projections make the field navigable for a particular use.
The distinctions establish authority. A convenient map does not replace the document it summarizes. A working context does not become permanent memory. A receipt proves what occurred without becoming the artifact itself.
3. Core file classes
Chapter 08 classifies memory by function; this table shows durable forms through which those functions can be realized. The mapping is not one-to-one. A companion record can preserve identity, standing, relationship, and lineage, while a decision may require an artifact, companion ground, and operation evidence together.
| File class | Standing | Intelligence function |
|---|---|---|
| Thinking Markdown | Primary exploratory work | Lets thought develop before formal structure is required |
| Canonical document Markdown | Primary artifact | Holds the language or deliverable the person is creating |
| Document Home / companion YAML | Canonical companion memory | Preserves identity, purpose, accepted spine, standing, lineage, relations, state |
| Document Map Markdown | Rebuildable projection | Presents movement structure and contribution in readable form |
| Project or Session Home | Canonical navigational bearing | Holds project purpose, plan, outputs, documents, and relationships |
| Workflow YAML and stage Markdown | Reusable method ground | Defines role, stages, guidance, quality, and completion behavior |
| Expertise resource | Accepted reusable knowledge | Carries reviewed principles, roles, methods, exemplars, and conventions |
| Materialized context Markdown | Rewritable capsule source | Holds stable notes and freshly selected reasoning ground |
| Decision and relationship record | Durable semantic state | Preserves rationale, authority, dependency, challenge, and supersession |
| Assignment and return record | Durable delegated-work state | Preserves commission, grant, product, limitations, and proposed delta |
| Operation and lifecycle receipt | Durable evidence | Preserves source state, authorization, exact effect, result, and failure |
| Registry and Flow Atlas output | Derived infrastructure | Resolves identity, validation, impact, inspection, and visualization |
4. The artifact remains primary
The document is the work the person is making. Metadata exists to help intelligence understand, navigate, and operate on that work. It does not replace the artifact or force machine state into public prose.
AIOS reads exact language, creates or extends artifacts, applies bounded revisions, restructures movements, composes across files, compares claims with sources, tests integrity, and produces maps and syntheses. Operational fields remain in companion records and receipts where they can support reconstruction without contaminating the artifact's human form.
5. The Document Home and Document Spine
The Document Home is the canonical companion memory adjacent to one managed document. It preserves stable identity while the artifact's title, path, language, state, and relationships change.
It carries the document ID, current path and revision, accepted purpose, movement hierarchy and anchors, accepted movement traces, landing, annotations, source lineage, relationships, completion synthesis, pending work, and operation ground.
Within it, the Document Spine gives the compact Why → How → What account of the artifact: why it exists, how its load-bearing movements develop, and what it establishes or leaves open. The spine supports context, navigation, and resumption. Visible prose retains the form required by its audience and purpose.
6. Identity, title, path, revision, and anchor remain distinct
Identity answers which durable object this is. Title answers what the person currently calls it. Path answers where it lives. Revision identifies the exact artifact state read by a judgment or operation. An anchor identifies the stable movement or section under reference.
A rename preserves identity. A move preserves lineage. An exact edit binds to the revision it inspected. A title match never authorizes mutation of stale content. These distinctions let file operations remain precise while the human-facing organization evolves.
7. The Document Map projects contribution
The Document Map is a readable projection compiled from the artifact and its accepted companion ground. It presents document purpose, ordered movements, hierarchy, contribution of each movement, document landing, selected annotations, relationship bearings, and anchors for exact descent.
Unlike a table of contents, the map explains how the artifact moves. It is discarded and rebuilt when stale because its authority comes from the canonical document and Document Home.
8. The Project or Session Home preserves navigational bearing
At project grain, the Home concentrates Purpose, Plan, Outputs, Documents, and Relationships. It is a launch point into the durable field rather than a chronological log.
From the Home, the system descends to companion records, movement maps, exact passages, decisions, sources, assignments, and returns. The person recovers project direction without loading every artifact or reconstructing conversation history.
9. Metadata performs four jobs
Identity resolves stable objects across changes in title, path, revision, and interface.
Semantic standing distinguishes source, interpretation, assumption, proposal, accepted ground, contest, staleness, and supersession.
Relationship and lineage show how artifacts, claims, decisions, sources, workflows, and operations bear on one another.
Operational reconstruction recovers what was authorized, in flight, applied, returned, failed, or awaiting attention.
The existence of a field never decides semantic truth. Metadata makes meaning addressable; judgment and authority determine standing.
10. Structured fields and natural language cooperate
Stable IDs, exact references, revisions, hashes, statuses with mechanical effects, operation types, ownership, lifecycle state, validation, and controlled relationship terms belong in structure.
Purpose, rationale, contribution, interpretation, uncertainty, exception, relationship meaning, quality conditions, and substantive directives belong in natural language.
This division lets mechanisms resolve exact obligations without asking a schema to carry the complete meaning of the work.
11. Records exist at consequential seams
Durable records preserve completed thinking movements, delegated commissions and returns, workflow runs, stage context, source sets, editorial plans, applied changes, cross-file operations, decisions, annotations, completion syntheses, promotion, and acceptance.
Recording every streaming fragment would generate operational noise. A receipt is warranted when future reconstruction depends on authority, identity, source state, standing, exact effect, product, failure, or continuation.
This threshold prevents receipt excess: evidence is preserved where continuity depends on it rather than emitted for every internal event.
12. Bounded file operations
Models declare semantic products and proposed consequences. The host applies exact effects through operations such as read, search, compare, create, insert, replace, append, move, branch, link, annotate, change status, register, supersede, archive, and explicitly authorized deletion.
Each consequential effect identifies its originating command or grant, canonical target, relevant source and destination revision, maximum mutation scope, parsing and validation result, success or failure state, resulting revision, and receipt.
This is bounded semantic sovereignty in operation: the model judges within an explicit jurisdiction, while deterministic mechanisms retain custody of exact file effects.
13. Standing governs file authority
| Input | Standing | Normal consequence |
|---|---|---|
| “Add this to the plan.” | Direct instruction | Authorizes a bounded plan change when the target is clear |
| “This may belong in the plan.” | Observed possibility | Creates a candidate, not an edit |
| Repeated theme | Forming pattern | Records evidence for review rather than installing a principle |
| Delegated research return | Evidence-shaped return | Enters as evidence or proposal, not an automatic decision |
| Approved reusable method | Promoted expertise | Becomes selectable guidance within scope |
| Stale map | Derived projection | Rebuilds from canonical ground; never overwrites it |
Semantic implication does not silently become mutation authority. Proposal, take-up, authorization, operation, and acceptance remain visible transitions.
14. Relationships form a file-native knowledge graph
Diagram 2 · §14
Explicit records and exact handles allow the graph to emerge from the files themselves. Search, source descent, indexes, and the Flow Atlas make those relations navigable. A database or vector store can assist retrieval without becoming canonical semantic authority.
15. Restart is an architectural test
From durable files, the system reconstructs document identity and revision, accepted purpose and structure, project bearing, pending and returned work, workflow state, decisions, relations, annotations, source standing, suggestions and take-up, lineage, maps, and indexes.
State that exists only in a running process is not durable file-native intelligence. Restart exposes whether the architecture has actually landed what continuity requires.
16. Provider independence follows from custody
Prompts, artifacts, memory, and records remain outside one model provider. A provider can change without taking the knowledge corpus with it. Context-window size no longer defines project memory. Evidence can be re-evaluated by different models against stable ground. Long-horizon work can survive upgrades and routing changes.
The boundary
Portability still requires provider adapters, capability testing, and behavioral regression evidence. Local custody prevents semantic lock-in; it does not make every model universally interchangeable.
17. Derived views remain removable
The Registry, Flow Atlas, maps, search facets, and working contexts make the system legible. Their safety depends on reconstructability.
The canonicality test is simple: if a projection disappears, can exact owner files and accepted records recreate it? A projection that cannot be rebuilt has become an undeclared source of truth.
This is the test against projection authority: a useful view may guide inspection, but it cannot acquire standing above the ground from which it was built.
18. Failure conditions and evaluation
Metadata monoculture
A metadata monoculture asks one schema to represent every meaning and workflow. Structure expands until it substitutes fields for the natural-language judgment the work requires.
Parallel companions
Parallel companions split authority over one artifact. Conflicting records can then claim the same purpose, spine, standing, or current state.
Projection authority
Projection authority lets a map, index, search result, or Atlas view outrank its sources. A rebuildable aid silently becomes the place where truth actually lives.
Title identity
Title identity treats a human-facing label as the durable object identifier. Rename or reuse then breaks lineage and can direct an operation toward the wrong revision.
Passive file watching
Passive file watching initiates semantic work merely because bytes changed. Observation becomes unadmitted action without a person command, prior grant, or bounded commission.
Hidden state
Hidden state keeps necessary continuity inside a running process or private store. Restart then reveals that the file environment cannot reconstruct the intelligence it supposedly owns.
Receipt excess
Receipt excess records more internal activity than later reconstruction can use. Evidence becomes operational noise and makes consequential seams harder to inspect.
Evaluation tests stable identity across move and rename, stale-edit prevention, canonical-versus-derived distinction, proposal/authorization/effect separation, lineage recovery, local isolation of malformed records, deterministic rebuilding, multi-model use, restart, and human legibility.