Repository navigation
Conversation
Add a read-only preview capability for stateful shuffled evaluation branches, require immutable derived evaluation-only lineage, and regenerate versioned research artifacts.
Exercise the read-only preview contract across the learner host and relay, proving it leaves the live policy and ledger untouched.
Prevent inherited evaluation budgets from expanding the immutable seven-branch paired-case contract.
Record a run-config-bound, privacy-preserving paired-case prediction commitment before each receiver action.
Execute a source-bound parent and seven immutable child branches with verified lineage and pre-action commitments.
Require explicit child-project teardown and provide a standalone retained-receipt audit before the prospective LV01 paired fixture is allocated. The bounded collector remains software qualification only.
Freeze fresh zero-spend development identities and the seven-branch paired-case packet against the qualified collector source. The allocations are prospective and establish no research result.
Bind parent and paired child topologies to explicit packet-verified subnets, clean up parent projects, and retain a terminal paired-case failure receipt. This addresses the v17 Docker address-pool exhaustion without reusing its allocation.
Register fresh zero-spend parent and paired development identities after the v17 Docker address-pool failure. Bind every parent and child topology to packet-verified explicit subnets without changing the scientific claim boundary.
Allow the prospective paired-development run-id family through the ephemeral qualification signer boundary. The v18 failed fixture remains retained and is not retried.
Register fresh zero-spend parent and paired development identities after the v18 signer-identity failure. Bind the packet to the repaired signer boundary and distinct explicit subnets without changing the scientific claim boundary.
Permit only the frozen seven paired-branch identities through the qualification signer boundary. The failed v19 fixture remains retained and is not retried.
Register fresh zero-spend parent and paired development identities after the v19 paired-branch signer failure. Bind the packet to the corrected branch grammar and distinct explicit subnets without changing the scientific claim boundary.
Pass the immutable copied parent bundle to offline derived-run verification. Preserve the failed v20 fixture; a fresh allocation remains required.
Bind fresh zero-spend identities to the repaired parent-lineage verifier source. Earlier failed attempts remain immutable.
Audit the retained paired fixture against its packet-declared branch order instead of retired branch names.
Add a portable receipt and CI audit for the retained seven-branch local development fixture.
Expose a hash-only qualification seam after the persisted paired prediction checkpoint. Recovery rejects the incomplete prefix without replaying it.
Stop the selected controller after a durable paired prediction commitment and require a replacement controller to reject the incomplete prefix without evidence mutation.
Require a prospective packet, immutable parent input, selected-controller termination, and non-mutating replacement recovery before admitting a fault receipt.
Bind the fresh selected-topology child attempt to frozen source and immutable v21 parent input before any collector execution.
Retain the v1 pre-collection failure and create parent evidence directories before allocating a new single-use root.
Select a packet version explicitly so every failed or superseded allocation remains immutable.
Use a fresh child identity, project, and network allocation after the retained v1 pre-collection failure.
Retain the v2 startup failure and allow the bounded LV01 fault-child identity to receive its ephemeral public keys.
Bind the signer-identity correction to a fresh child, project, and isolated network allocation.
Bind the completed local controller-loss qualification to its immutable raw receipt and portable auditor.
Run the retained v3 commitment-window receipt auditor in the mandatory CI gate.
…s/refuses/reconciles surfaces)
…(drop brew float)
…14b162), superseded by Linux re-freeze
a0-lease.test.ts and a0-launch.test.ts share one on-disk lease (.artifacts/a0-leases/active.json) while vitest runs files in parallel. A sibling create landing inside the no-live-state test flaked run('show') 3/6 batch runs. Skip (per suite philosophy) when a test-owned lease demonstrably holds at assert time; strict otherwise. Verified: 4/4 batch 48/48 green post-fix, solo 15/15, tsc clean.
SHi-ON
force-pushed
the
feat/verifiable-core
branch
from
October 17, 2026 02:57
523c802 to
b96eca7
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Successor to closed #1 on rewritten history (plans/ purged, see comments). R01/R02/R03/R04.1 batch.