{ "spec": "coderifts.assurance-capture.v1", "date": "2026-09-23", "measured_by": "@coderifts/conformance@0.8.11", "pinned_version": "0.8.11", "ceiling": "A passing adversarial vector proves ONE NAMED SHAPE fails at the recorded version, never that the class is closed. RECORDED is not LIVE. MODELLED is not COVERED.", "_how": "Two runs of the same suite. `recorded` (default) verifies vendored pinned artifacts; `live` produces new proof on available infra and reports NOT_RUN without it, never falling back. The two axes are coverage and evidence_tier, and the suite refuses to conflate them.", "summary": { "recorded": { "profiles": 7, "covered": 7, "partial": 0, "not_covered": 0, "live": 2, "recorded": 5, "modelled": 0, "not_run": 0, "overall_evidence": "RECORDED", "full_live": false, "coverage_line": "7/7" }, "live": { "profiles": 7, "covered": 2, "partial": 0, "not_covered": 5, "live": 2, "recorded": 0, "modelled": 0, "not_run": 5, "overall_evidence": "LIVE", "full_live": false, "coverage_line": "2/7" } }, "profiles": [ { "id": "DECISION_LOGIC", "title": "Verdict invariants", "recorded_coverage": "COVERED", "recorded_evidence_tier": "LIVE", "live_coverage": "COVERED", "live_evidence_tier": "LIVE", "already_live": true, "goes_live_when": null, "why_not_live": null, "does_not_prove": [], "vectors_present": 15 }, { "id": "RECEIPT_CRYPTO", "title": "Signature and binding", "recorded_coverage": "COVERED", "recorded_evidence_tier": "RECORDED", "live_coverage": "NOT_COVERED", "live_evidence_tier": "NOT_RUN", "already_live": false, "goes_live_when": [ "live kernel / production key / key-discovery not available in this process" ], "why_not_live": "LIVE evidence was requested and this suite does not mint receipts. Without a live kernel, a current production key and a fresh key-discovery endpoint, RECEIPT_CRYPTO is NOT_RUN. It does not fall back to the recorded vectors — that would conflate the two axes.", "does_not_prove": [ "that the live kernel mints this today", "that the production signing key is current", "that the key-discovery endpoint is fresh", "that the grant is currently executable" ], "vectors_present": 16 }, { "id": "GUARDED_TOOL_TABLE", "title": "The tools handed to the guard", "recorded_coverage": "COVERED", "recorded_evidence_tier": "LIVE", "live_coverage": "COVERED", "live_evidence_tier": "LIVE", "already_live": true, "goes_live_when": null, "why_not_live": null, "does_not_prove": [], "vectors_present": 6 }, { "id": "CREDENTIAL_BOUNDARY", "title": "The raw host cannot write", "recorded_coverage": "COVERED", "recorded_evidence_tier": "RECORDED", "live_coverage": "NOT_COVERED", "live_evidence_tier": "NOT_RUN", "already_live": false, "goes_live_when": [ "live infra (Postgres / executor / host credential) not available in this process" ], "why_not_live": "LIVE evidence was requested for CREDENTIAL_BOUNDARY and this suite does not mint a prove transcript. Without the running host and database that produced the recorded bundle, the profile is NOT_RUN. It does not fall back to the recorded transcript — that would conflate the two axes.", "does_not_prove": [ "that another secret credential is equally refused", "that another target (a different database, a git ref, a raw shell) is inescapable", "that the current configuration still matches this recorded catalog", "that a live kernel would refuse the same host INSERT today — this is one recorded run" ], "vectors_present": 4 }, { "id": "ATOMIC_COMMIT", "title": "Nonce + CAS + attestation as one transaction", "recorded_coverage": "COVERED", "recorded_evidence_tier": "RECORDED", "live_coverage": "NOT_COVERED", "live_evidence_tier": "NOT_RUN", "already_live": false, "goes_live_when": [ "live infra (Postgres / executor / host credential) not available in this process" ], "why_not_live": "LIVE evidence was requested for ATOMIC_COMMIT and this suite does not mint a prove transcript. Without the running host and database that produced the recorded bundle, the profile is NOT_RUN. It does not fall back to the recorded transcript — that would conflate the two axes.", "does_not_prove": [ "that a different executor, schema or deployment still holds the same invariants", "that a live kernel would refuse the same stale token today", "that POINT 8 merge happened — THIS profile's artifact (fixtures/recorded/prove-transcript, run prove-fb5c23bd) records it MODELLED. END_TO_END grades a different capture, in which POINT 8 is PROVEN; neither statement is about the other's evidence" ], "vectors_present": 6 }, { "id": "PROVIDER_ENFORCED", "title": "Merge or deploy refused at the provider", "recorded_coverage": "COVERED", "recorded_evidence_tier": "RECORDED", "live_coverage": "NOT_COVERED", "live_evidence_tier": "NOT_RUN", "already_live": false, "goes_live_when": [ "live GitHub / correlated e2e infra not available in this process" ], "why_not_live": "LIVE evidence was requested for PROVIDER_ENFORCED and this suite does not mint GitHub observations. Without gh credentials and a live provider, the profile is NOT_RUN. It does not fall back to the recorded dumps — that would conflate the two axes.", "does_not_prove": [ "that the ruleset is currently active — freshness is HISTORICAL (was active at observed_at, not proven active today)", "that another unmeasured credential holder (bypass_actors / admin) is equally gated", "that the configuration today still matches this captured ruleset", "captured by a local gh token, not a GitHub OIDC-attested runner", "that GitHub signed these payloads — they are API dumps, not GitHub-signed objects", "that the positive pole (PR#5) was merged — it remains mergeStateStatus BEHIND; SUCCESS on the required check is the positive evidence", "that PR#5's merge-API 405 is a gate-refusal — its reason is \"expected\" (branch BEHIND), not \"failing\"; it is the gate-specificity control beside PR#4's \"failing\" 405", "that the GitHub Actions check \"contract-gate (Action)\" (app 15368) is the ruleset context — the required context is \"CodeRifts / contract-gate\" (app 2860592)", "that a gate-SUCCESS + up-to-date merge was observed — it was not. The 405 pair is a merge-API refusal body (HISTORICAL, local gh), not that a merge proceeded", "that any merge has LANDED under enforcement — MEASURED 2026-09-05: zero commits reached main since the ruleset was created (2026-09-02T08:34Z). The 405 is a refused attempt, not a successful merge", "that the \"expected to be REFUSED\" canary PRs (#12, #13) are evidence — both MERGED on 2026-08-27, six days BEFORE the ruleset existed; they measure the un-enforced repository and must not be cited here", "that a [skip coderifts]-style marker was ever tried — MEASURED 2026-09-05: GitHub code/commit/issue search for \"skip\" on coderifts/demo returns 0 across titles, bodies and commit messages" ], "vectors_present": 7 }, { "id": "END_TO_END", "title": "Authorization through to a governed target state", "recorded_coverage": "COVERED", "recorded_evidence_tier": "RECORDED", "live_coverage": "NOT_COVERED", "live_evidence_tier": "NOT_RUN", "already_live": false, "goes_live_when": [ "live GitHub / correlated e2e infra not available in this process" ], "why_not_live": "LIVE evidence was requested for END_TO_END and this suite does not mint GitHub observations. Without gh credentials and a live provider, the profile is NOT_RUN. It does not fall back to the recorded dumps — that would conflate the two axes.", "does_not_prove": [ "that the target-state transition was re-derived here — conformance holds no repository, so the authorized commit's parents are the ones the PRODUCER recorded, checked only against the base it also recorded. NO SIGNATURE BINDS THAT BLOCK. What can be anchored is: the observation is checked field-by-field against the root-bound readback bytes, and the authorized commit and payload digest against the signed correlation — so an edited block is caught wherever an anchor exists. `base` and `parents` have no anchor, and an artifact that is internally consistent about them is believed (RECORDED, not re-measured)", "that the executor reported its own run honestly — the evidence root binds these tokens to ONE run and closes third-party splicing, and it says nothing about an executor misreporting a run it really performed. The root is signed by that same executor", "that the executor's attestation was witnessed by anyone — it is the executor's own signature over its own transition, re-checked here against the executor registry. Trusted-executor integrity, not an external witness", "that any provider was involved at all — this capture is a LOCAL bare-Git target (target_kind git_bare_ref, provider_witness NOT_APPLICABLE). The target-readback is the executor's own machine read by a process that could not write it; there is no third party here to have done, or failed to do, anything", "that the OBSERVED TARGET STATE is what any other copy of the contract holds — the correlation binds the commit in the target this run mutated, and nothing was re-read anywhere else", "THE MISREAD THIS PROFILE REFUSES: \"7/7\" does not mean CodeRifts merged a pull request. It means the git.ref.update chain — authorize, ledger consume, executor attestation, read-after-write — is correlated end to end on ONE grant, in one run, on one machine", "that CodeRifts merged anything — no pull request was merged under this grant. That is PATH B, a different claim requiring CodeRifts to be the merge actor, and this profile is not evidence for it", "that this run happened today — the capture is pinned and replayed; freshness is HISTORICAL" ], "vectors_present": 2 } ], "does_not_prove": [ "That a profile whose condition is listed will ever meet it. `gaps[]` is what the suite says is missing in THIS process, not a commitment.", "That RECORDED evidence is weaker proof of the named shape — it is proof of a pinned capture, replayed. It is not proof that the live kernel does it today, which is exactly why the two tiers are never merged.", "Anything about a profile the suite did not report. A missing profile is absent from this file, not passed." ] }