The documentation set is intentionally small. Current behavior belongs in the nearest authoritative document; completed plans and obsolete audits remain available through Git history rather than in the working tree.
| Document | Purpose |
|---|---|
| Project README | Product overview and quick start |
| Architecture | Process, state, storage, and contract ownership |
| Development | Setup, standards routing, and verification |
| Contributing | Change, planning, documentation, and commit expectations |
| Releasing | Current release flow, required evidence, and known gaps |
| Security | Reporting and current trust-boundary guidance |
| Native bindings | Binding status, generation, and packaging |
Audits describe the named repository and standards commits. They are evidence and remediation inputs, not current operating instructions.
- Artifact acquisition — Q1 shared HTTP acquisition is active; AQ-HTTP is not ready
- Runtime installations and model adapters — runtime implementation remains gated by acquisition evidence
- 2026-09-03 current-standards remediation program
- Local intent API and transport-independent domain language — complete within the recorded local scope; native resolution, acquisition, durable declarations and existing IPC/RPC projections accepted; nodes/fleets/new networking deferred until after the next release
An implementation invocation must name the exact focused plan.md and an
explicit start, continue, or verify operation. Plans remain temporary
execution authority; durable accepted decisions move to the appropriate guide
or ADR when the program finishes.
- Frontend
- Electron desktop shell
- Rust workspace
- Core Rust crate
- Torch sidecar
- Developer scripts
- Generated bindings
- Plugin manifests
When guidance conflicts with executable configuration or code, treat that as documentation drift and fix the document and owning behavior together.