Repository navigation
Rebind pre-P0 machine package to v0.3 before founder adoption #27
Description
Status
PRE_P0_HOLD / IDENTITY_REBIND_REQUIRED
CURRENT_GATE:
P0-DISC-001
CURRENT_CONTROL_BASIS:
v0.3-proposed
P0:
NOT_EXECUTED
F0:
NOT_CLOSED
Finding
The current proposed v0.3 implementation-control path and the older machine-package identity are not yet one coherent chain.
Observed identity aids:
CURRENT_V0_3_MANUAL_DIGEST_PREFIX:
1643b9d9
LEGACY_MACHINE_PACKAGE_MANUAL_DIGEST_PREFIX:
5a6be223
The machine manifest and ADOPTION-002 path remain bound to the older v0.2 identity. They must not be issued alongside a v0.3 adoption instrument as though both describe one source subject.
Digest prefixes are not complete SHA-256 values. Closure requires exact source bytes and full digests in one byte-preserving controlled workspace.
Required bounded work
- Retrieve the exact v0.3 manual and companion-profile bytes without normalization.
- Record the exact role and filename of every current package component.
- Rebuild or amend the machine-package manifest against the exact v0.3 bytes.
- Produce one successor or consolidated adoption identity for the coherent v0.3 package.
- Recompute the complete SHA-256 set and verify every package relationship.
- Acquire and record the pinned dependency identities, including
jsonschema,referencing, andrfc8785. - Execute Draft 2020-12 validation, all 156 fixtures, RFC 8785 finalization, and the end-to-end self-test.
- Preserve v0.2 as historical lineage rather than silently overwriting it.
- Bind the founder shell, candidate roots, authorized output root, evidence home, recovery destination, custody method, and authority record.
- Emit
PRE_P0_READYonly if all applicable checks pass.
Closure conditions
Close this hold only when all of the following are attributable to exact source identities:
- one coherent v0.3 manual, companion-profile, machine-manifest, checksum, and adoption chain exists;
- the complete SHA-256 set verifies;
- the required schema and fixture suite passes;
- RFC 8785 behavior is finalized and passes;
- the end-to-end self-test passes;
- the local execution and custody bindings are recorded;
- the founder-ready adoption packet no longer contains overlapping v0.2 and v0.3 authority paths.
GitHub relationship
The GitHub preparation state is recorded in draft PR #26:
docs/F0_F4_CONTROL_PACKAGE_SOURCE_CUSTODY.md
docs/F0_F4_GITHUB_COMPARISON_PREPARATION.json
docs/PRE_P0_GITHUB_HANDOFF.md
docs/PRE_P0_GITHUB_HANDOFF.json
The eight preparation PRs remain draft and unmerged. Their successful workflow results are bounded evidence for exact draft subjects, not F0–F4 closure evidence.
Boundary
This issue does not upload or normalize the v0.3 package bytes, issue adoption, authorize or execute P0, close F0, merge any preparation pull request, mutate registry pins, change releases or tags, configure repository settings, or establish independent reproduction.
It records the final known pre-P0 identity hold so it cannot be silently bypassed.
Activity
Riverbraid commentedon Aug 10, 2026
2026-08-10 pre-implementation applicability note
Read-only recheck against the current founder-supplied project source bundle indicates that this issue remains useful as the visible GitHub pre-P0 hold, but the specific repair state in the original issue body is no longer the latest local navigation state.
The current local navigation/repair records (not uploaded here as executable custody) record:
Important custody boundary: the exact
c1cabf...carrier bytes are not contained in the current AI project-source bundle, so this note does not establish or upload executable custody and does not independently reproduce those local qualification results.The original issue body's v0.2/v0.3 identity-rebind and 156-fixture checklist should therefore be treated as historical pre-repair navigation, not as the current technical repair list. Do not close the issue merely on that basis: current closure still requires exact-carrier binding, source-bound native Windows qualification, the superseding entry-anchor/adoption sequence required by the controlling records, and separate P0 authority before P0 execution.
GitHub preparation drift recheck: the eight draft PR subjects recorded by PR #26 remain open, draft, unmerged, and on their recorded exact heads:
Riverbraid-Core#7—699567de01e83494a8f4a00b503b322ff61b410cRiverbraid-Evaluation-Kit#13—868341e2a26ae1ac912be170a2930034b06623eeRiverbraid-Golds#6—57fcbdbe9677debd6795ee3b423d99dccbc9b7f0Riverbraid-Documentation#26—2a227ecea06abeb1d64c7ac5b2adc1db8589743cRiverbraid/.github#5—40916bf7425821ed29e8cf405500387eaffe5129Riverbraid-Refusal-Gold#7—a05c341af05fe9b5663c5dc8d6e85084e0118cdcRiverbraid-Harness-Gold#6—e054407becc9d995b023042a24eaf0c7cae5e0b7Riverbraid-Gold-V2#3—9124578dbc7ec1285accc7098df6453fbbab51ecThis comment is an append-only applicability clarification only. It does not merge, adopt, upload the control package, mutate registry pins, issue P0 authority, or advance F0-F4.