This is the stable entry point for delivery status. Mutable work records live
as independent files under docs/progress/ so concurrent branches
do not edit one shared checklist.
- Read active or blocked slice files under
docs/progress/. - Read
avm-implementation-spec.mdandavm-consolidation-plan.mdfor implementation rules and sequencing. - Create one file named
YYYY-MM-DD-<descriptive-slug>.mdfor the new slice. Do not allocate a sequentialF###identifier and do not maintain a shared index.
Each slice file records:
Status:in-progress,blocked, orcompleteStartedandUpdateddates- the working branch
- outcome, checklist, validation, and blockers or dependencies
Update only the slice file owned by the current branch. Keep completed files in place as the audit trail. If work is deliberately handed to another branch, record the takeover in that same file before the new branch edits it.
Get-ChildItem ./docs/progress -Filter '*.md' |
Select-String -Pattern '^\*\*Status\*\*: (in-progress|blocked)$'The checklist used before this convention was adopted is preserved in
legacy-checklist-through-2026-08-10.md.
Older closed workstreams remain in
progress-archive.md.