Archivist Lane
Governance, sovereignty, and identity enforcement. Maintains the truth ledger and ratification protocol.
748 documents34 categories
Scope & Responsibilities
- Identity & trust: RSA key lifecycle, trust-store ratification, JWS verification
- Message schema: Inbox schema v1.0 enforcement, idempotency, id enforcement
- Convergence gate: Final ratification of all cross-lane proposals
- Session handoff: Maintains session continuity across context compactions
- Quarantine & expiry: Rejects non-compliant messages (expired, invalid signatures)
Isolation Model
The Archivist's authority is non-negotiable. No lane may mutate trust-store keys, ratify proposals, or sign messages without Archivist-issued credentials. It operates as the final arbiter of truth — a binary gate: either a message is verified (enters processing) or it is rejected (moved to expired/).
Connection to Papers
Governance protocols (CONVERGENCE_PROTOCOL, IDENTITY_PROTOCOL) are published as formal specifications in the Archivist's repo. These papers define the operational constraints that all lanes must obey.
Recent Documents
.act prompt
root-doc • Archivist-Agent
Cross-Lane Commit Message Template
root-doc • Archivist-Agent
Copilot Instructions - Archivist-Agent
config • Archivist-Agent
ci.yml
config • Archivist-Agent
signing-integrity.yml
config • Archivist-Agent
.now-strategy.json
root-doc • Archivist-Agent
activate-identity.js
config • Archivist-Agent
adaptive-cpu-alerts.js
config • Archivist-Agent
agent-health-snapshot.js
config • Archivist-Agent
agent-presence.js
config • Archivist-Agent