Scrivener
Operations On-Demand Contract Complete

Scrivener

Documentation Maintenance Specialist

Audits documentation for staleness and quality

""Documentation is not administrative overhead. It is operational infrastructure that agents depend on.""
01 · Scope

What is this agent's job?

Audits documentation for staleness and quality

Identity

Scrivener maintains documentation quality across the Value-First monorepo -- detecting stale references, fixing broken links, keeping planning docs synchronized, and ensuring Sanity CMS schema integrity. Documentation is infrastructure. When a skill file references a deprecated command or an INDEX file has wrong agent counts, every agent that loads it operates with false confidence.

Quality Bar

Documentation staleness report identifies specific files with last-modified dates, broken references, and outdated information.

  • ☐ Stale documentation detected (30+ day files with active dependencies)
  • ☐ Broken cross-references identified
  • ☐ Planning doc sync verified (README, INDEX, ROADMAP consistent)
  • ☐ Sanity CMS schema integrity verified
  • ☐ No forbidden language

Invocation Triggers

"Check documentation health" or "Find stale docs" → spawn scrivener
/weekly-review includes documentation health → spawn scrivener
Sanity schema integrity check needed → spawn scrivener

Scope Boundary

Scrivener maintains documentation and Sanity schema. Scrivener does not curate memory files (Archivist does) or maintain code (Squire does).

What Works / What Doesn't

What Works

  • Agent definition with clear scope for documentation maintenance and Sanity operations

What Doesn't Work

  • No AGENT.md implementation exists yet
  • No automated staleness detection
  • No integration with Sanity schema validation
Feedback Loop Reference freshness: when agents load docs with outdated information, Scrivener failed to catch staleness. Archivist handles the parallel for memory files.
02 · Access

What can this agent touch?

Handoff

Archivist (memory curation is parallel to doc maintenance)

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)
"Scrivener is needed but not built. The March 15 self-upgrade session proved the point -- INDEX.md had wrong agent counts, ROADMAP.md was 10 bricks behind, DEFERRED.md had 5 resolved items still listed as open. That was a manual fix. Scrivener would catch these continuously."
← Back to AI Team