Slipmark Cloud
By Reply Intelligence Group
founder-ship-it/Slipmark · Proof record #66

The gate refused.

RefusedLedger intact · 96 entries0 verified · 4 refusedRe-verified against GitHubRecorded 25 Oct 2026, 15:23 UTC
Where it came fromsigned by GitHub
Ledger entryLedger intact · 96 entries
Entry
#66 of 96
Entry hash
29312c4a161dfd59f17dff5a7ddb0108498f03e189088b40391342baab5c6cec
Previous hash
c476e3d470dc617da93bd5ccf6b101637b935ff4238e2442f3ea447b01f565e9

Each entry's hash covers this run's verdicts and the previous entry's hash. The whole chain is recomputed every time this page is built: changing any past record would break it here.

Organisation rules Not met

Rules set by the repository owner, checked against the files this change touched.

RuleResultFiles it coveredMissing a passing verdict
Gate code and its spec need a reviewer passNot metdocs/attestation.md, src/attest/context.tsdocs/attestation.md, src/attest/context.ts
Payments code needs a security reviewMetnone changed

Gate results

What CI found when it re-hashed each attested file at commit 56968b7. Slipmark Cloud then read GitHub's own copy of the commit, re-hashed every attested file itself and got the same answer.

ResultFileAgentVerdictDetail
Spec changed after verdictsrc/attest/attestation.tsreviewerpassattested 7556949190a7…
now e2b69530aac4…
Spec changed after verdictdocs/attestation.mdreviewerpassattested 3752b18b9857…
now a19d857b5d93…
Spec changed after verdictdocs/attestation.mdreviewerpassattested 3752b18b9857…
now a19d857b5d93…
No verdictsrc/attest/attestation.ts——no passing, current attestation covers src/attest/attestation.ts

Verdicts as the agents recorded them

The attestation files in the repository at this commit.

reviewer · pass.slipmark/attestations/reviewer--docs_attestation.md.json
Read
docs/attestation.md 3752b18b9857076c2c1aa90a4ef815e94aa53ebd8642bc0706a48b55ce414a63
Note
Docs match code: policy-from order and fallback note, policy.source/ref/sha256, require in policy, subfolder and link rules, new exit-2 cases, signatures.issuer, HEAD message.
Attested
25 Oct 2026, 14:32 UTC
reviewer · pass.slipmark/attestations/reviewer--src_attest_attestation.ts.json
Read
src/attest/attestation.ts 7556949190a721b8dc2ce0249664dde2302e88b5d7128b7ae5d56a3f2c48451b
Note
Policy read from base: resolution order, exact refs/remotes base via show-ref, ls-tree with every parent checked (linked .slipmark is exit 2), subfolder policy with root guard, CRLF, no-base matches v0.4; attack repos r1-r8 behave as documented.
Attested
25 Oct 2026, 14:32 UTC
reviewer · pass.slipmark/attestations/reviewer--src_attest_signing.ts.json
Read
src/attest/signing.ts aeefb8706f106dc0ddfcea6b6f3bba1dff9a49c4c572ab8a0b9113803578ae42
Note
Signed verdicts section matches signing.ts: DSSE over canonical JSON minus signature, payload check, issuer default and signatures.issuer, * identity match, invalid always refuses, unreachable Sigstore exits 2 only when required.
Attested
25 Oct 2026, 14:32 UTC

What this proves: these verdicts were recorded by founder-ship-it/Slipmark's own workflow at this commit, and the files above either matched or did not. It does not prove a verdict was right, only what it was about.

#66 refused · founder-ship-it/Slipmark · Slipmark Cloud