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.
These files are the current source of truth for the rebuild:
rebuild/current-plan.md- active execution order and next work
rebuild/current-state.md- what is built, what is open, what is blocked
rebuild/current-runtime-map.md- Foundation, runtime, model, agent, and memory boundaries
rebuild/intelligence-pipeline.md- extraction, memory, synthesis, action routing, hubs, and agents
rebuild/agent-architecture.md- Harlan, Crewbert, assistants, delegation, and agent boundaries
system-strategy.md- durable system doctrine
source-registry.md- source contract operator index
rebuild/doc-cleanup-plan.md- how docs become truth or evidence
rebuild/owners-closeout.md- Owners package closeout detail and remaining boundaries
business-strategy.md— durable business strategystrategy/— supporting strategy packet docssource-notes/— source-specific operator notes and validation evidencespecs/— design contracts until promoted into active implementationspecs/bcrew-ui-design-contract.md— active BCrew UI style contract for login, launcher, Foundation, and hub surfaces
handoffs/— session checkpoints, source validations, and reconstructed transcriptsaudits/— historical and current audit artifactsrebuild/plan-history/— retired rebuild plans and decision snapshots kept for traceability, not current doctrineresearch/— research notes and older doctrine debatessuperpowers/— older design work and implementation plansdecks/— presentation assets
Evidence files can be useful, but they are not current doctrine unless the active truth set links to or promotes them.
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.