craft

To maintain a durable project ledger, you initialize a project-local YAML file that persists contexts, blockers, decisions, and gaps with stable IDs and evidence. This authoritative ledger governs nested workstreams and routes memory across planning and review.

Tracking nested workstream governance requires a recursive ledger that links contexts, enablers, and recomposition state. Applied per repository, it enforces per-row IDs and required fields to manage state and route evidence across teams over time.

You can generate a human-readable view from a YAML ledger by linking it to a Markdown file. This provides human and machine surfaces, creating generated index lookups alongside the authoritative YAML state for fast status checks.

You initialize project state tracking by running a start_project command to create the project ledger. You then inspect the state to view current blockers, decisions, gaps, and next moves using the lifecycle governance workflows.

Project ledger governance works without external dependencies by operating entirely project-local. It relies on an internal schema enforcing per-row IDs and references within the YAML authoritative ledger to maintain recursive state.

Recomposition in lifecycle governance is the process of restructuring existing project state, gaps, and decisions over time. The ledger supports dedicated workflows to recompose nested workstreams, ensuring continuous state alignment during planning and review.