This directory uses numbered documentation layers. Start here before reading implementation code or dated progress logs.
From the repository root, run vstatus to inspect the current cross-project
production workflow without changing production data:
| Need | Command |
|---|---|
| Current overview | .\vstatus |
| Periodic refresh | .\vstatus watch |
| Lesson pipeline | .\vstatus lesson "<lesson-name>" |
| Run details | .\vstatus run <run-id> |
| Task attempts | .\vstatus task <task-id> |
| Stage wave | .\vstatus wave <stage> <number> |
| Machine-readable output | .\vstatus json [output-file] |
| Strict health gate | .\vstatus check |
| Command help | .\vstatus help |
The overview covers vBook orchestration, vtext progress, vision/fusion quality, run evidence, pause/stop controls, and scheduler freshness. Read the production workflow status runbook for field interpretation, exit codes, aliases, and advanced options.
For project orientation:
- 00_project/overview.md
- 00_project/glossary.md
- 00_project/status.md
- 00_project/task-board.md
- 00_project/roadmap.md
For development work:
- 00_project/glossary.md
- 00_project/status.md
- 00_project/task-board.md
- 30_pipeline/README.md
- 20_architecture/README.md
- 40_development/README.md
For technical experiments and route comparisons:
- 40_development/experiment-protocol.md
- 60_operations/experiment-workspace.md
- 60_operations/experiment-workflow.md
- 60_operations/experiment-artifacts.md
- 60_operations/experiment-datasets.md
- 70_progress/2026-07-10-note-synthesis-experiment-plan.md
| Layer | Purpose |
|---|---|
| 00_project/ | Project positioning, glossary, scope, roadmap, and status |
| 10_product/ | User scenarios, product workflow, requirements, and acceptance criteria |
| 20_architecture/ | System architecture, module boundaries, data contracts, and decisions |
| 30_pipeline/ | Stage-by-stage media-to-knowledge pipeline documentation |
| 40_development/ | Setup, commands, testing, Git workflow, and agent collaboration |
| 50_modules/ | Package-level documentation for vbook_* modules |
| 60_operations/ | Local runs, smoke tests, troubleshooting, and artifact cleanup |
| 70_progress/ | Status snapshots, backlog, milestones, and dated progress logs |
| 80_superpowers/ | Agent specs, implementation plans, reviews, and handoffs |
| 90_reference/ | Original requirements, external references, and vtext boundary material |
The original documents now live in the numbered layers:
- 10_product/business-plan.md
- 20_architecture/design.md
- 20_architecture/architecture.md
- 20_architecture/data-model.md
- 20_architecture/module-boundaries.md
- 20_architecture/output-contracts.md
- 30_pipeline/overview.md
- 40_development/sync-protocol.md
- 00_project/legacy-roadmap.md
- 90_reference/original-requirements.md
vBook can learn from vtext's project structure and workflow ideas, but it must remain an independent project with independent modules, interfaces, and evolution.