Skip to content

docs: one vertical slice through DoD, owner gates and protected merge (NO_BUMP) #145

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
pcvantol merged 2 commits into from
Sep 18, 2026
Merged

docs: one vertical slice through DoD, owner gates and protected merge (NO_BUMP) #145

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
9be334e
docs: require complete vertical slices and scoped autonomous delivery…
pcvantol Sep 18, 2026
8bd2edb
Merge current main into vertical-slice documentation branch
pcvantol Sep 18, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
17 changes: 12 additions & 5 deletions BOOTSTRAP.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -8,11 +8,18 @@ For the owner's two concurrent Codex architect sessions, read
[LANE_2](docs/roadmap/lanes/LANE_2.md), and both linked live coordination issues.
The [allocation index](docs/roadmap/dual-lane-development-v1.json) covers the
existing 34 families without changing their owning dependency graphs or the
historical count. Select independent ready subsets; do not issue a duplicate
prompt or mutate another lane's repository/runtime. The next suitable scope
moves to a qualified Forge Mission route as soon as it can, not after the full
portfolio. This is operator planning/navigation, not a new runtime scheduler,
authorization, maintenance operation or change to Mission-3 acceptance.
historical count. Every assignment must follow
[vertical-slice delivery](docs/roadmap/VERTICAL_SLICE_DELIVERY_V1.md): one kickoff
covers implementation, required tests/refactoring, review fixes, supported owner
authorization, PR, protected main merge and declared artifact/installed delivery.
The owner has delegated those ordinary lifecycle steps within the selected
released scope; do not ask for routine reapproval or issue separate test/DoD/
merge prompts. Real permissions, independent assurance and material effect
boundaries remain mandatory. This is not a fabricated runtime grant.
Select independent complete outcomes; do not issue duplicates or mutate another
lane's repository/runtime. Move supported scope to qualified Forge Missions as
soon as possible, not after the whole portfolio. Reading this planning does not
start a scheduler, reset, release or Mission, or change Mission-3 acceptance.

## Roadmap overview and autonomy-first focus

Expand Down
Loading
Loading