Skip to content

Fix RC2 recovery and accounting for bounded Home pilot - #10

Open
justyn-clark wants to merge 4 commits into
mainfrom
fix/rc2-pilot-recovery
Open

justyn-clark wants to merge 4 commits into
mainfrom
fix/rc2-pilot-recovery

Conversation

@justyn-clark

@justyn-clark justyn-clark commented Oct 16, 2026 •

Copy link
Copy Markdown
Owner

Summary

Corrected, unpublished RC2 prepared for a merge decision. Stable release and the uninterrupted Home asset demonstration remain separate held milestones. No merge, tag, release, deployment, Home run or new model spending is performed by this PR update.

  • PR head: bc0b05cc2d9321ae300d15e62fa99e8864e26d93.
  • Prior remote head e210cde9d59d4f4cdc9048a5a7c3bb969e5d510d fast-forwarded through the accepted correction 6a5641432032b4ca3e7fe4d941e4ef14afa989e0; no force push or imported experimental work.
  • Includes interrupted-dispatch checkpointing, monotonic known usage with exact archived reports, bounded verified restoration and immutable continuation/accounting fixes, with fail-before/pass-after regressions and matching docs.
  • The only nine paths after the accepted source are canonical audit/proof continuity, CHANGELOG and public documentation. All runtime, dependencies, examples, tools and workflow bytes are identical to the accepted source.

Acceptance Boundary

The original unchanged static engineering acceptance is accept_for_bounded_home_pilot, no findings, independent of core authorship (same provider; not organizational independence). It names source 6a5641432032b4ca3e7fe4d941e4ef14afa989e0 and runtime 0.5.0-rc.2, binary SHA256 f71e926d0a864b4f36a019e8951a4cb922639fd6ab365af1e8847494ed946d8c. The existing checksum-pinned binary is unchanged and reproduced byte-for-byte by the local offline proof build.

  • Acceptance SHA256: b2df4d527847a96683f7d9a3886b658f00bd9526407e5eb8afa463e7573f3678.
  • Evidence-manifest SHA256: 8a42e33364f90b91ed57e182e5de25f9baeb57e93f848fc8985ad2638b397dc9. Private original packets/logs/receipts remain private.
  • Source-content digest remains e563ec372e78c1cbe026089f9e12ff93523efd8a5ec9f216552473bc14085b72; documentation digest changes only with these clarifications.
  • No receipt is rewritten or reassigned to this new Git SHA or a different build. A binary rebuilt at the PR head has different VCS metadata and requires its own binding/acceptance before live use; the original accepted binary is the bounded pilot candidate. Material runtime changes require newly authorized review.

See merge-readiness record and RC2 notes.

Validation

  • Fresh focused/full Go suite, vet, internal race, scoped-budget race (count 3), default CLI contract, format and gitleaks passed locally.
  • Legacy, creative, scoped-budget, model-assignment and SMALL v1/v2 offline integration proofs passed with no provider/native/Home operations.
  • Source-bound allowlisted docs bundle, semantic prose review, code/docs and SMALL co-change, publication privacy and cache-free SMALL strict gates passed. CLI reference unchanged because no CLI/default/JSON contract changed in the audit/prose descendant.
  • Hosted checks for this exact head: PASS on Linux and macOS for both push and pull-request CI; GitGuardian also passed.
  • Pull-request CI and push CI, both bound to bc0b05cc2d9321ae300d15e62fa99e8864e26d93.

Kept Separate

  • Continuous-spend 0.5.0-rc.3-dev.1, source c2cb18f36465c24e73ab74e96f2cf7d4647c232d, binary bd318c28e469c4b73bd744cf5a4b87efbf8626dfde20612c3df3833a2ee4a2e5: not imported; independent acceptance pending. The proposed one-call 190,000-token review remains PROPOSED_NOT_AUTHORIZED.
  • Home completion-harness repairs (reported 98 checks/11 syntax checks) remain separate offline consumer work, not a fresh independent verdict.
  • All historical rejections/attempts and cumulative ledgers retained: five release calls spent, 230,937 reported tokens, USD unknown; unused conditional second review closed. This preparation spends zero new model calls and no Home asset allowance.
  • Dirty primary checkout, historical build directories, installed runtimes, old contracts and Home files are unchanged. No quality threshold is lowered or baked into the general-purpose runtime.

Remaining Milestones

A human merge decision is next after final exact-head checks. Stable/live approval, uninterrupted real Home demonstration, source-bound deployed documentation readback, immutable packaging and publication remain separate; this PR does not clear those gates.

@justyn-clark justyn-clark changed the title Hold RC2: recover safely and preserve truthful pilot evidence Fix RC2 recovery and accounting for bounded Home pilot Oct 20, 2026
@justyn-clark
justyn-clark marked this pull request as ready for review October 20, 2026 07:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant