Add inactive risk-gates evaluator - #210
Conversation
Deploying ystack with
|
| Latest commit: |
007eb84
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://e2f4164f.fabrica-6yx.pages.dev |
| Branch Preview URL: | https://codex-control-risk-gates-v1.fabrica-6yx.pages.dev |
Codex reviewer (cross-vendor, read-only)Reviewed-head: 007eb84 BugsNo findings. The complete classifier, malformed-input precedence, forced-high and unsupported-tier handling, claim/request/reference binding, timestamp ordering, duty-result regeneration, and canonical output validation were reviewed. Classification-only cases execute the exact shipped risk-gates.jq. Representative routine, high, bootstrap, reject, duty-violation, forged-duty, dependency, strict-jq, and TOCTOU cases retain the complete wrapper path. Pure cases retain canonical verdict, sorted and unique reasons, normalized minimum tier, and no-authority assertions. Process-group launch waits for confirmed group ownership. Timeout and signal paths use bounded TERM, KILL, and wait cleanup. The forced-timeout regression proves that a TERM-resistant nested process does not survive. The TOCTOU marker pauses inside the exact risk-program execution window, and the final live-file identity check rejects mutation on Linux and macOS. An independent exact-candidate targeted run passed all 48 risk-gates checks. SecurityNo findings. Caller-authored accept claims remain inconclusive with unqualified provenance. No input can synthesize satisfied, authority, qualification, activation, permission, or an external effect. Malformed, stale, ambiguous, unbound, rejected, downgraded, unsupported, and duty-violating inputs fail closed. Policy, decision, evaluator, duty-separation, validator, and selected-core closure identities are bound and checked again after execution. Inputs reject symlinks. jq must be an absolute regular jq 1.6 executable. Private mirrored dependencies execute, and race mutations are detected. The change adds no credential, real target, networked adapter, candidate execution, publish, deploy, release, install, or live activation path. ComplianceNo findings. The exact diff contains only README.md, RESTORE.md, ci/required-files.txt, the five risk-gates product files, and the targeted risk-gates test. It is one inactive, repo-only Control foundation Roadmap concern. No construction-mode forbidden path or prefix is touched. Restore-manifest changes are append-only and include every new restore-critical file. README and RESTORE describe the inactive observation-only boundary and focused proof. The branch is a linear descendant of the exact base. Required app-15368 CI run 33508343002 and check 99857694481 succeeded on this exact head/base. No exceptional implementation, authority expansion, workflow or permission change, constitution change, frozen PR #183 change, or excluded parent-plan change was found. |
|
Construction merge receipt
Postflight verified squash-only ancestry, exact tree equality, and the main ref. |
Roadmap item 2: Control foundation.
Exact candidate
Scope: eight paths
Proof on the exact head
Linux root fix
Behavior
This change does not use a real target or credential, execute candidate code, access a networked adapter, install or activate a profile, publish, release, deploy, or perform an external write.