Skip to content

Latest commit

 

History

History
56 lines (42 loc) · 2.8 KB

README.md

File metadata and controls

56 lines (42 loc) · 2.8 KB

Documentation Authority Map

Status: Active Last updated: 2026-04-25

This repo has a lot of documentation on purpose. Some files are active truth. Most are evidence.

Use this map so old handoffs and audits do not compete with the current system.

For the full markdown inventory, use INDEX.md. It is generated by node scripts/generate-doc-indexes.mjs and classifies every doc as active truth, supporting truth, evidence, or reconciliation work.

Read First

These files are the current source of truth for the rebuild:

  1. rebuild/current-plan.md
    • active execution order and next work
  2. rebuild/current-state.md
    • what is built, what is open, what is blocked
  3. rebuild/current-runtime-map.md
    • Foundation, runtime, model, agent, and memory boundaries
  4. rebuild/intelligence-pipeline.md
    • extraction, memory, synthesis, action routing, hubs, and agents
  5. rebuild/agent-architecture.md
    • Harlan, Crewbert, assistants, delegation, and agent boundaries
  6. system-strategy.md
    • durable system doctrine
  7. source-registry.md
    • source contract operator index
  8. rebuild/doc-cleanup-plan.md
    • how docs become truth or evidence
  9. rebuild/owners-closeout.md
    • Owners package closeout detail and remaining boundaries

Supporting Truth

Evidence

  • handoffs/ — session checkpoints, source validations, and reconstructed transcripts
  • audits/ — historical and current audit artifacts
  • rebuild/plan-history/ — retired rebuild plans and decision snapshots kept for traceability, not current doctrine
  • research/ — research notes and older doctrine debates
  • superpowers/ — older design work and implementation plans
  • decks/ — presentation assets

Evidence files can be useful, but they are not current doctrine unless the active truth set links to or promotes them.

Rule

If a claim appears only in a handoff, old audit, or research note, treat it as evidence. Promote it into active docs or the DB-backed backlog before building from it.