The archive is the memory: the store of what was decided, what was done, and what comes next. Where the executive is the live state, the archive is the durable record behind it, kept as a real checkout so the work persists across every session. It is one of the four parts of Ordova.
The archive is the part of the system that remembers: session handoffs, project plans, daily notes, captured reading, and drafts in progress.
It is the counterpart to the live configuration. The executive holds what the agent runs under now; the archive holds what has accumulated over time, so a new session can pick up where the last one stopped without starting from nothing.
It is kept as a real checkout, not a scratch folder, so the record is versioned and travels with the rest of the working identity.
Each kind of note has a home: handoffs, projects, daily notes, ideas, captured articles, content drafts, and the memory store.
Session handoffs record what was completed and what to resume. Projects hold the longer arcs, separated into the early and the matured. Daily notes keep the chronological thread, and captured articles keep the reading worth keeping. A documentation tree describes the system to itself.
The memory store sits among them, written every session by the harness, so what is worth remembering across sessions is held in one named place rather than scattered.
Anything dropped into a synced folder from a phone reaches the inbox at the next session; one command writes it up, ready for you to place.
A thought, a link, or a document lands in a drop zone. On the next session a hook moves it into the inbox, and a single command classifies it and writes it up. The capture takes a second; the groundwork is one command. Where it belongs in the record stays your decision.
The inbox is deliberately transient: a staging area, not a home. Once an item is promoted to its proper place, the staging copy is cleared.
The navigation over the archive is a view of the notes beneath it, never a second source of truth.
A front page maps the whole, and each folder carries its own index. These are derived views: they summarise the notes, so when the substance changes the note changes first and the map is regenerated from it.
This is the same discipline the rest of Ordova holds: a neglected record has gaps but stays true, while a neglected summary drifts silently and reads confidently. We keep the truth in the record and treat the map as downstream of it.
The archive is a private store: personal professional capital, kept private by deliberate decision.
The methodology that shapes the record is documented in the open, and this page is part of that. The contents of the record are not. They are the accumulated working context of one operator, which is exactly the capital the charter sets out to keep on our own side.
So the structure is public and the substance is private, and the line between them is drawn on purpose rather than by neglect.
This page is a derived view: a plain-voice adaptation of the archive's own README, not the record itself. Keeping the two in step as the source is revised is the job of the source anchor.