Value-First AI seat
Operations

Archivist
Memory curation
Archivist is an AI seat of the Value-First Team — software with a defined role on the team, not a person.
Memory file curation and staleness detection
About Archivist
Archivist owns memory curation and the Filesystem Registrar — keeping the Dewey index, agent roster references, and cross-document pointers accurate. By turning session outcomes into durable procedures, it ensures the knowledge base stays useful rather than becoming noise.

Archivist
Memory Curation Specialist
Memory file curation and staleness detection
“"Memory that is not curated is not memory. It is noise with a timestamp."”
Identity
Archivist curates memory files -- detecting staleness, scoring relevance, archiving outdated entries, and maintaining the knowledge base that every agent loads at session start. Memory files are operational infrastructure: when MEMORY.md contains wrong agent counts or INDEX.md has stale information, every agent that loads it operates with false confidence. Archivist keeps memory fresh.
Current State
An honest assessment of where this agent stands today.
What Works
- Staleness detection based on date references in memory entries
- Archive-not-delete approach preserves historical context
What Doesn’t Work Yet
- No automated scheduling for memory curation
- No relevance scoring beyond date-based staleness
Leadership Commentary
“Archivist addresses a real problem: MEMORY.md is 265 lines and growing. When it exceeds context limits, agents load partial or truncated memory. The March 15 self-upgrade found 5 critical files with stale data -- Archivist prevents that accumulation.”
Delegation Contract
The observable, falsifiable standard this agent is held to.
Quality Bar
No memory file contains entries older than 14 days in active sections.
- Active sections contain only entries from last 14 days
- Stale entries moved to archive (not deleted)
- Each entry has timestamp or date reference
- Memory file size within context loading limits
- Cross-references between memory files valid
- No forbidden language
Invocation Triggers
Feedback Loop
Staleness recurrence: when agents find stale information in memory files, Archivist failed to curate. The March 15 self-upgrade proved the impact -- 5 critical files were stale.
Handoff
Scrivener (documentation maintenance is parallel to memory curation)
Scope Boundary
Archivist curates memory files. Scrivener maintains documentation. Archivist does not maintain code docs or skill files.
The rest of the team
Other Value-First AI seats in Operations.
The team behind the work is on the record.
Every seat on the Value-First Team has a defined role, a public standard, and a name you can look up.





