Repository navigation
Conversation
This branch has not been deployed
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.
Behavioral-integrity hardening against exact frozen base
7f39a846ad05f91560836026e5ef6dfbc74dc731.This PR remains draft. It does not merge, refreeze, authorize a learned fit, or authorize formal Family-1 selection.
Scientific firewall
rigxl_03490IDs, counts, thresholds, or family-conditioned repair branches;J=67/ generation-limit75repair constants;rigxl_03490remains dev/integration-only and can never become untouched formal Family-1 evidence;Geppetto — behavioral closure PASS
Canonical record:
canonical/GEPPETTO_V2_BEHAVIORAL_CLOSURE_20260903.md.Major generic repairs:
roots=1,illegal_parents=0,unsupported=0);log_sigma(h.detach())).Confirmed causal seam: uncertainty NLL was able to optimize shared latent state through
log_sigma(h). Detaching sigma-head input changed the frozen genericfork_5from FAIL-through-2048 to sustained PASS at step 544 while preserving sigma learning.Geppetto run
33703334408:chilecentral, job100487117556: 27/27 PASSwestus3, job100487622297: 27/27 PASSCross-region behavioral replay: PASS.
IRIS — privileged-input source firewall PASS
Historical scope:
canonical/IRIS_LEAK_SCOPE_20260903.md.Repair ledger:
canonical/IRIS_PRIVILEGED_INPUT_FIREWALL_REPAIR_V1_20260903.md.Successor correction:
canonical/IRIS_REPROJECTION_V2_PRIVILEGED_INPUT_CORRECTION_20260903.md.Pre-repair causal run
33704040761confirmed:2.012694835662842;0.18466269969940186;8candidate-valid flips and anchor count64 -> 32.The legacy source suite still passed at that time, so dedicated negative regressions were required.
Generic repairs:
viremoved; analytic projected camera-forward depth is used with projected grid/validity;RGB_CAMERA_FULL_FRAME_LATTICE_V1, deterministic full-frame and camera-only;Frozen negative regressions:
tests/iris/test_iris_v2_privileged_input_firewall_v1.py.Standalone source closure:
33751592814,westcentralus: firewall 4/4 PASS, combined IRIS 24/24 PASS;33751730077,westus3: firewall 4/4 PASS, combined IRIS 24/24 PASS.IRIS_PRIVILEGED_INPUT_FIREWALL_CROSS_REGION_REPLAY = PASSHistorical checkpoints/metrics produced under the superseded privileged-input contract remain QUARANTINED. This is source-contract closure, not learned-fit evidence.
Current architecture-freeze candidate
The Geppetto behavioral gates, Compiler proof gate, and IRIS privileged-input firewall are now mandatory architecture-freeze prerequisites.
Architecture-freeze run
33751730186, job100636583064,northcentralus:38;1c6878b2e1e8cbd30a055849a64c8fe68558924e0a874de2e8fffa2e24ad7575;PASS_SOURCE_ELIGIBLE_FOR_FREEZE;FAMILY_SELECTION_BLOCKED__SOURCE_CHANGED_AFTER_FREEZE.The fingerprint is a candidate, not a seal. Broader subsystem behavioral hardening continues before any global refreeze decision.
Provenance note
The original IRIS 2026-08-31 preregistration is preserved unchanged. Its RGBA learned-path / padded-hull assumptions are not retroactively rewritten; the valid chain is:
original prereg -> causal falsification -> repair ledger -> successor correction -> future explicit architecture seal.Repo/branch naming cleanup is deliberately deferred until the hardening sequence is stable so provenance is not disrupted mid-stream.