Skip to content

docs: specify Genesis/Managed bootstrap execution and promotion (NO_BUMP) #273

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 1 commit into from
Sep 17, 2026
+168 −0
Merged

docs: specify Genesis/Managed bootstrap execution and promotion (NO_BUMP) #273

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
12 changes: 12 additions & 0 deletions BOOTSTRAP.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2,6 +2,18 @@

**Status:** Canonical standalone repository onboarding

## Project bootstrap — Genesis, Managed and promotion

The [project bootstrap execution design](docs/engineering/PROJECT_BOOTSTRAP_EXECUTION_V1.md),
[scoped owning roadmap](docs/development/PROJECT_BOOTSTRAP_V1_ROADMAP.md) and
[documentary DAG](docs/development/PROJECT_BOOTSTRAP_V1_DAG.json) specify the
future manifest-driven creation/adoption and Genesis-to-Managed promotion.
Reuse B8R identity/attachment and existing Genesis/Managed primitives; the added
PB-E operation/qualification nodes remain PLANNED. This is NO_BUMP design work,
not an active provisioning request, runtime change or Mission-3 prerequisite.
Forge owns product/manifest semantics; EP owns actual repository effects and
readback; Workspace owns the human experience. Peer communication stays HTTP.

## Current pickup checkpoint — consolidation and parking, 10 September 2026

Read the [owning consolidation roadmap](docs/development/CONSOLIDATION_PARKING_2026_09_10.md)
Expand Down
20 changes: 20 additions & 0 deletions docs/development/PROJECT_BOOTSTRAP_V1_DAG.json
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,20 @@
{
"schema_version":"1.0",
"increment":"PROJECT_BOOTSTRAP_AND_ARTIFACT_MANIFEST_V1",
"owner":"engineering-platform",
"authority":"DOCUMENTARY_DERIVED",
"executable":false,
"version_decision":"NO_BUMP",
"parent_lanes":["B8R","GENESIS_MANAGED_EXECUTION","P-TRANSPORT","L0"],
"architecture":"docs/engineering/PROJECT_BOOTSTRAP_EXECUTION_V1.md",
"current_mission_3_dependency":false,
"nodes":[
{"id":"PB-E0","status":"PLANNED","depends_on":[],"deliverable":"Typed operation, authority, B8R identity and receipt contracts"},
{"id":"PB-E1","status":"PLANNED","depends_on":["PB-E0"],"deliverable":"Inventory, existing lease/ledger admission and HTTP readback"},
{"id":"PB-E2","status":"PLANNED","depends_on":["PB-E1"],"deliverable":"Local Genesis bootstrap and attachment evidence"},
{"id":"PB-E3","status":"PLANNED","depends_on":["PB-E1"],"deliverable":"Managed birth/adoption and host governance readback"},
{"id":"PB-E4","status":"PLANNED","depends_on":["PB-E2","PB-E3"],"deliverable":"History-preserving explicit Managed promotion"},
{"id":"PB-E5","status":"PLANNED","depends_on":["PB-E1"],"deliverable":"Operation-scoped reporting, telemetry and safe recovery"},
{"id":"PB-EQ","status":"PLANNED","depends_on":["PB-E2","PB-E3","PB-E4","PB-E5"],"external_evidence":["forge:PB-F0"],"deliverable":"Installed Genesis, Managed, promotion and negative-boundary qualification"}
]
}
20 changes: 20 additions & 0 deletions docs/development/PROJECT_BOOTSTRAP_V1_ROADMAP.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,20 @@
# Project bootstrap V1 — EP owning roadmap

**Owner:** Engineering Platform. **All added implementation/qualification nodes: PLANNED. NO_BUMP.**
This scoped delivery roadmap extends the [canonical EP roadmap](ENGINEERING_PLATFORM_ROADMAP.md) at the existing B8R attachment, Genesis/Managed execution, P-TRANSPORT and L0 contract/proof seams. It is not a replacement execution engine or a claim those foundations are absent. Forge L1/L1-R is the consumer lane; Workspace onboarding is a later client, not an EP prerequisite.

Read the [EP execution design](../engineering/PROJECT_BOOTSTRAP_EXECUTION_V1.md) and [documentary DAG](PROJECT_BOOTSTRAP_V1_DAG.json). Cross-product semantic contract and PB-01..PB-40 catalogue: `pcvantol/forge:docs/architecture/PROJECT_BOOTSTRAP_AND_ARTIFACT_MANIFEST_V1.md` and `PROJECT_BOOTSTRAP_QUALIFICATION_V1.md`.

| Node | Depends on | Deliverable and closure |
| --- | --- | --- |
| PB-E0 | none | Versioned typed operation/receipt/capability contract, B8R-compatible identity reservations and authority mapping |
| PB-E1 | PB-E0 | Bounded inventory, authorization, lease/ledger and actual HTTP admission/readback over owning services; no new side channel |
| PB-E2 | PB-E1 | Genesis absent/unborn/existing local bootstrap with trusted validation, local commit and committed attachment evidence |
| PB-E3 | PB-E1 | Managed absent-resource birth plus existing-repo adoption, protected delivery, governance/CI readback |
| PB-E4 | PB-E2, PB-E3 | Quiesced, publication-authorized Genesis-to-Managed promotion preserving IDs and Git history |
| PB-E5 | PB-E1 | Scoped reporting/export/telemetry, cancellation and restart-safe effect reconciliation, privacy and no implicit Mission |
| PB-EQ | PB-E2, PB-E3, PB-E4, PB-E5 | Installed execution qualification across both modes/promotion and all applicable PB cases; real remote-provider proof distinct from fixtures |

PB-E0/PB-F0 align published immutable contract fixtures. PB-E1 consumes the qualified P-TRANSPORT/authority subset, not the whole future installer/Agent-fleet programme. PB-EQ may use Forge-produced contract fixtures without requiring final Forge PB-FQ. Forge PB-F3 consumes PB-E1, PB-F4/PB-F5 consume mode results, and PB-FQ consumes PB-EQ. There is no cross-product cycle and no dependency on Workspace UI.

Genesis and Managed implementation can proceed independently after E1. Promotion joins them. Qualification of the new operation must not alter the current Mission-3 acceptance or install new runtimes during a running test. Ordinary feature delivery and active #271/#272 changes are outside this documentation increment.
16 changes: 16 additions & 0 deletions docs/engineering/GENESIS_MODE.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -29,3 +29,19 @@ a bounded corrected terminal report while preserving the original local report.
Managed transactions remain the default. Their repository synchronization,
GitHub pull-request, validation, merge, finalization and cleanup lifecycle is
unchanged.

## Complete project bootstrap and promotion — planned composition

The [project bootstrap execution design](PROJECT_BOOTSTRAP_EXECUTION_V1.md),
[owning roadmap](../development/PROJECT_BOOTSTRAP_V1_ROADMAP.md) and
[documentary DAG](../development/PROJECT_BOOTSTRAP_V1_DAG.json) specify the
future manifest-driven Genesis/Managed bootstrap and explicit promotion.
They reuse the local-only primitives above, but add planned artifact,
identity/adoption, authority, recovery and qualification contracts. They do
not expand current placement support or silently change the legacy declaration.

Genesis is local engineering, not automatic publication permission. Promotion
requires a separately approved remote/history/settings effect set and actual
Managed-governance readback, with unchanged project identity and ancestry.
New-project readiness never creates or approves a Mission. All added PB-E nodes
remain PLANNED; this documentation changes no runtime, grant or installation.
Loading
Loading