This file is the canonical entrypoint for repository documentation.
These documents describe the current MVP behavior and should be treated as the source of truth:
- ../README.md: runtime entrypoints, repo map, and current MVP scope
- current-truth.md: canonical product boundary, runtime, docs, and historical artifact notes
- repo-hygiene.md: canonical source, fixture, artifact, and release-evidence policy
- swarm-operator-contract.md: canonical
autovoice swarmoperating model, run taxonomy, GitNexus inputs, MemKraft writes, and lane completion rules - user-guide-voice-profiles.md: source-artist and target-user workflow, training lifecycle, conversion, and karaoke usage
- frontend-persistence-boundaries.md: what lives in browser
localStorageversus what is owned by backend storage - api/README.md: REST and WebSocket API entrypoint
- deployment.md: current compose, hosted preflight, release-candidate, and completion-matrix deployment contract
- production-readiness-closeout-2026-04-28.md: latest production verification results, support boundary, and remaining release blockers
- quality-ux-post-release.md: quality and operator-UX milestone for improving local/private readiness evidence; not a public/commercial launch declaration
- public-commercial-launch-gate.md:
AV-3rfd.18launch blockers and evidence required before public/commercial readiness can be claimed - troubleshooting.md: operational debugging and recovery notes
These are useful for implementation context, but they are not the authoritative current-product spec:
- continuous-learning-architecture.md: earlier architecture design track
- seed-vc-architecture.md: pipeline-specific reference
- hq-svc-patterns.md: HQ-SVC implementation notes
- sota-voice-training.md: research synthesis
- smoothsinger-concepts.md: conceptual notes
- security-review.md: security review context
- deployment-guide.md: deployment-oriented instructions
- deployment-verification.md: reference notes for deployment verification details
Date-stamped readiness, coverage, and failure-analysis reports under docs/ are historical artifacts. They document past investigation snapshots, not the current MVP truth. Use them for archaeology only after reading the canonical docs above.
Root-level historical planning, prompt, and completion-report docs (formerly ORCHESTRATOR*.md, PHASE*, *_SUMMARY*, PROMPT.md, etc.) now live in archive/.
Historical examples include: