feat(rsi): add controlled proof demonstration protocol - #26
Merged
Merged
Conversation
added 6 commits
September 30, 2026 15:52
Member
Author
|
Adversarial review completed against the final PR head (
Verification: 183 test files passed in |
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.
Summary
Adds the staged issue #20 proof workflow: a development-only engineering pair, a final frozen three-campaign plan, resumable paired development and confirmation execution, and read-only JSON/Markdown analysis. The engineering gate requires a durable generation-zero self-hosted selection, an accepted generation-one child run from that selected commit, and terminal generation-one fixed-control candidate decisions. Confirmation identities are not scheduled during engineering.
The final plan binds the benchmark manifest, effective configs, task schedule, runtime and image identities, broker allocations, seeds, analysis source, engineering evidence, endpoint metadata, and operator cap. Before execution, the launcher reloads task identities and recomputes the full calls/tokens/spend/runtime plan from the frozen configs and broker limits; it rejects a stored plan that understates the recomputed budget. OpenRouter routing is pinned to DeepInfra fp8, with returned model/provider metadata checked before usage can qualify.
No live demonstration or paid inference has occurred. An authenticated OpenRouter key was used only for read-only endpoint metadata. The three brokered requests in the mock guest smoke used a mock upstream and do not represent production provider usage. No operator cap has been supplied.
Verification
npm run typecheck— passed on the final tree.git diff --check— passed on the final tree.npm test— exit 0; all 183 test files passed. TAP recorded 35 skipped integration cases: 9 PostgreSQL-gated and 26 S3-gated. The final added fixed-control CLI-path assertion was then verified by the focused integration test below.npx tsx src/rsi/benchmark/__tests__/openshell-integration.test.ts— passed on the final tree; verifies one selected fixed-control CLI launch, guest/verifier separation, and teardown ordering.npx tsx src/rsi/__tests__/proof-demonstration.test.ts— 3 passed, 0 skipped, including a qualifying synthetic record and fail-closed tampering cases.npx tsx src/rsi/__tests__/proof-demonstration-launcher.test.ts— 3 passed, 0 skipped, including generation-one fixed-control decision enforcement and restart/receipt checks.npx tsx src/rsi/__tests__/proof-demonstration-plan.test.ts— passed, including recomputed budget mismatch rejection.npx tsx --test src/rsi/__tests__/postgres-queue.test.ts src/rsi/__tests__/proof-campaign.test.ts— 40 passed, 0 failed, 0 skipped.ea12df5ee67abb3d610dd26a68988c5dff8af25f: RSI image digestsha256:0e2b6135d2e9011e27a1043feb1d9faf387043e0893f50d41efc2ccd53bc26b5; image marker matched that commit. The commits after it contain test-only changes.$0.001272mock accounting, 0 arbitrary-egress sentinel hits, and no raw key in guest result. Gateway alias trap removed and sandbox list was empty after the run.Security impact
The OpenRouter key remains in the supervisor broker and is not sent to the guest. Candidate execution and independent verification remain isolated. Confirmation fixtures and verifier inputs are excluded from guest snapshots/images. Frozen plans and analysis outputs are restricted to external or ignored supervisor-only paths. Campaign execution requires the exact frozen cap and fails closed on incomplete or uncertain evidence.
Test plan
No production inference should be sent without a concrete operator-approved cap. The report must remain inconclusive or not-demonstrated unless all frozen paired cells, receipts, artifacts, ledgers, lineage, and statistical gates verify. The mock smoke and service-backed integration checks exercise plumbing only; they do not establish the multi-generation demonstration.