Work¶

This section holds shaped work produced by the BFDev process.

Use work/ for material tied to one specific initiative, delivery slice, or shaped problem that may change status over time. Each work item gets its own slug folder so the challenge, specification, stories, release plan, and supporting notes stay together.

work/ is intentionally not a generic dumping ground for drafts. A page belongs here when it is part of a bounded piece of delivery and would feel incomplete or misleading if it were separated from the rest of that work item's context.

Use reference/ instead when the content is meant to stay true across multiple initiatives. Use process/ instead when the content explains how work should be done rather than what a given work item contains.

Lifecycle Buckets¶

Bucket	Purpose
`active/`	Current initiatives, projects, and approved work in flight
`backlog/`	Shaped work not yet assigned to an active delivery slice
`archived/`	Superseded or completed work retained for reference

Folder Contract¶

One folder per work slug
The canonical landing page for each work item is index.md
Common work documents are challenge.md, spec.md, stories.md, and optional release-plan.md
Not every work slug needs every document on day one; add the standard pages when the work is ready for them
Supporting dated material belongs under notes/ or evidence/ inside the work item folder
Long-lived cross-project design belongs in reference/system-design/, not here
Process guidance belongs in process/, not here