Archivist
Operations On-Demand Fully Operational

Archivist

Memory Curation Specialist

Memory file curation and staleness detection

""Memory that is not curated is not memory. It is noise with a timestamp.""
01 · Scope

What is this agent's job?

Memory file curation and staleness detection

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.

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

/weekly-review includes memory health → spawn archivist
"Clean up memory" or "Memory is getting stale" → spawn archivist
MEMORY.md exceeds 300 lines → spawn archivist for curation
Context loading fails due to memory file size → spawn archivist immediately

Scope Boundary

Archivist curates memory files. Scrivener maintains documentation. Archivist does not maintain code docs or skill files.

What Works / What Doesn't

What Works

  • Staleness detection based on date references in memory entries
  • Archive-not-delete approach preserves historical context

What Doesn't Work

  • No automated scheduling for memory curation
  • No relevance scoring beyond date-based staleness
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.
02 · Access

What can this agent touch?

Handoff

Scrivener (documentation maintenance is parallel to memory curation)

04 · Production Record

What has this agent produced?

Recent Runs

Run history coming soon — instrumentation in flight.

Active Engagements

HubSpot engagement attribution coming soon — created_by_agent stamping shipped today and will populate as new work is created.

Published Artifacts

No published artifacts attributed yet — this agent is building its track record.

Leadership Commentary

V (COO)
"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."
← Back to AI Team