You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Require authentic initial runtime and production readiness lineage in adjudication bindings #217
Independent read-only review of the #209 implementation in PR #214 found that adjudication_inputs accepts initial invocation envelopes with an absent/unbound production_receipt and an incomplete arbitrary runtime object. The positive test uses a nonexistent readiness path and runtime containing only git_head/helper_sha256, yet the phase passes. Equality against copied metadata does not establish that the real launcher could have accepted these originals.
Require the complete maintained launcher runtime keys, bind helper/runtime identities to original frozen inputs, retain and validate the original production readiness receipt and its necessary lineage, and reject nonexistent, substituted or incomplete readiness/runtime inputs. Preserve original clone identity while validating in the later adjudicator clone; do not rerun old receipts as if they were current environment receipts. Add negative regressions for this exact forged/incomplete provenance shape and document the mechanical limits. File recorded before repair; no new scientific phase launched.
Activity