Description
The wave operating model records the README as a deliberate exception: because it is one large file it has exactly one owner per wave, and where several lanes each need a section the README owner is scheduled last with declared dependencies on all of them. That is a real cost paid every wave, and it grows as surfaces are added. The operating model still describes it as 54 KB; it is now 76534 bytes, which is the growth curve stated as a fact. A documentation site already exists under docs/ with its own navigation, so the content has somewhere to go. The point of splitting is not tidiness, it is removing the serialization: sections that live in separate files can be owned by the lanes that produced them. The README that remains should be what a reader needs in the first minute, and a map to the rest.
Acceptance Criteria
- #1 README content is redistributed into docs pages by subject, with no content silently dropped in the move
- #2 The remaining README orients a new reader and links onward, and is small enough that two lanes editing different subjects do not collide
- #3 Every moved section is reachable from the docs site navigation, verified by rendering it rather than by reading the config
- #4 Links that pointed into the README from docs, examples and task history either still resolve or are updated
- #5 The Wave operating model document is updated to retire the single-owner README exception, since the reason for it is gone
Definition of Done
- #1 just check passes locally
- #2 hosted Validate workflow passes on the completing commit
Implementation Plan
Wave 4: implement the commissioned lane after the pushed root harness pre-pass; preserve frozen schemas and ownership; return acceptance evidence and required negative controls; root integrates, reviews, validates locally and at the exact hosted SHA, then reconciles status.
Final Summary
Split the original 76534-byte README into the assigned subject pages and a short orientation/link map. All 51 original section destinations were checked in rendered HTML; the lane accounted for 164 source blocks and root restored all ten adoption blocks. Fourteen navigation pages rendered without issues; 162 local Markdown targets had zero missing files/anchors. Updated the external examples link and retired the README single-owner scheduling exception through the Backlog CLI. Status/pins, security boundaries, review stages and field references follow the clarified destination map; old function pin text was corrected to the unchanged installed digest. Completing checkpoint SHA 5c482ffcf2100714cfe1c3751733d805a501489a; hosted Validate 34263860085 success. Implementation SHA 9c559d105c5cd7761db3c9ca290150d35c936175; hosted Validate 34263352393 success. Local just check passed with 85.4% coverage. Main still has zero real admission cases and one skipped placeholder; these tasks do not claim admission completion.