Skip to content

Bind charged integrity adapters to shared image access - #93

Draft
afflom wants to merge 1 commit into
v01/integrity-proofsfrom
v01/integrity-owned-access
Draft

afflom wants to merge 1 commit into
v01/integrity-proofsfrom
v01/integrity-owned-access

Conversation

@afflom

@afflom afflom commented Nov 5, 2026 •

Copy link
Copy Markdown
Member

Integrity adapters previously used their own byte/span access and lost failed-operation work in plain Result errors. This binds OwnedHash and ArchiveBinding to the exact shared RuntimeImage source (cf840ba, SHA-256 7a3dbde8…ef77f) and adds charged result APIs. Existing APIs remain result projections. Successful charged work equals Transition.work and is charged once; typed errors retain the actual prefix cost. Borrowed descriptors do not pin backing: the real producer span ticket stays owned through consumption and release acknowledgment.

The same OwnedLifecycleLaws module is replaced with 33 native declarations/27 main roots against actual RuntimeImage reads, archive-prefix admission and charged success/error equations. Fresh kernel compilation, exact axiom audits and leanchecker pass. Twenty independent fixtures, 60 partitions, ten owned reconstructions and 21 source-owned controls pass, including equal/early/late digest costs and valid-root cleanup. Both one-byte accounting defects reject; exact restoration replays. All 32 repository tooling tests, projection equality, source-authority audit, formatting and diff checks pass.

A complete current 19-module SDK run exposed missing UInt64 foundations. All 97 adapter/control declarations were traced and only 39 exact axiom fields corrected to existing Quot.sound/propext; no body, signature, error, codec, runtime behavior or compiler policy changed. The corrected run passes all source-policy audits with all 16 Core production roots and limits preserved, then fails certificate A C2225d74…R14.__rel_16 for current Core.Heap.releaseStep with LLV7013 kernel deep recursion. This is distinct from the historical RuntimeSequence.step failure. Official lowering maps the current row to Core.Heap.indexEmpty, an existing three-branch helper. The actual two-source isolation stops earlier at Heap.allocate certificate B, fun25 (LLV7015, Rust.Corr.mCons); it does not independently replay the later releaseStep failure. Both exact outcomes, source/roots/limits identities and measured layout comparison are recorded under validation/integrity/image-access/heap-investigation. No justified source factoring was identified or implemented. Paired original/fixed receipts and exact source/model delta are under validation/integrity/image-access/sdk-policy.

Stacked on #87. Exact shared Core RuntimeImage is added as a dependency; no other Core or product implementation is changed. The separate 8339ef8 integration artifact preserves the exact Product uc_exe_01 open Registry row beside all prior Integrity rows. Its public Product tool inputs matched the requested hashes; actual model-write and read-only projection checks passed with 31 IDs. Only the matching Registry, four genuinely changed generated outputs and scoped generation receipts were published. This does not qualify the broader combined runtime. Original SDK/project locks and limits remain unchanged. The published legacy source serialization requires official notation rendering for language1.2; no direct full-source/pinned-SDK acceptance is claimed. Owned production export, Wasm, general Heap/physical-resource refinement, authenticated engine trace and full archive acceptance remain separate. No merge, release tag or issue completion is requested.

Merge the preceding chain head into v01/integrity-owned-access and carry this
lane's unintegrated changes forward in SDK 1.2 form.
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