NORTHSET
Proof-of-Pass Receipt
Receipt ID M-003
ISSUE / WORKNo issue or pull request recorded
REHEARSAL — NOT EXTERNAL VALIDATION
RUN1.2s
01 / TECHNICAL RESULT
Technical result
declared commands passed
2/2 declared commands returned exit 0 in the recorded environment
- Upstream
- PREPAREDmutable external state
- Environment
- node@sha256:2cf067cfed83d5ea958367df9f966191a942351a2df77d6f0193e162b5febfc0network phaseA:bridge,phaseB:none
- Signature
- verified Northset signing workflow provenance
02 / DECLARED CHECKS
Command evidence
Execution summary
2/2 declared commands returned exit 0 in the recorded environment
node bin/validate-mission.mjs missions/M-001/mission.jsonexit 0 · 0.2s
node bin/bundle.mjs verify missions/M-001exit 0 · 0.2s
unclassified executor time (derived residual) 0.7s
run wall (derived from recorded timestamps) 1.2s
Every command listed returned exit 0 in the declared environment. Only the listed commands are in scope. Unlisted test, lint, typecheck, build, coverage, compiler, full-suite, and CI gates are not implied or recorded.
03 / RECORDED IDENTITIES
Compact hashes
- Container image digest
node@sha256:2cf067…5febfc0- Bundle contents digest
sha256:70857a…b13b1c3- Signed asset SHA-256
sha256:90ceab…13f741b
04 / CLAIMS BOUNDARY
NOT INCLUDED
- Does not prove code quality
- Does not prove security
- Self-funded rehearsal on Northset's own repository; not external validation.
05 / Evidence annexTechnical · provenance · full recorded values
01Technical evidence
Code, full environment, patch, and redacted outputs
Technical evidence
Code, full environment, patch, and redacted outputsProject
northset-oss/verification-pilot
Work
No issue or pull request recorded
Verification execution
runtime: northset-oss executor v0
human operator: aeziz
Code
- base
af4fc4d4342dc40128828ebf95e3e49dad3934fa
Environment
- image reference
- node@sha256:2cf067cfed83d5ea958367df9f966191a942351a2df77d6f0193e162b5febfc0
- repository digest
node@sha256:2cf067…5febfc0- network
- phaseA:bridge,phaseB:none
Redacted stdout
=== cmd 1: node bin/validate-mission.mjs missions/M-001/mission.json ===
=== cmd 2: node bin/bundle.mjs verify missions/M-001 ===
OK sha256:6a8bfdeb771e9b1515aa3fcdddda239dba417865fad29bff20f1ac187d372b62
Redacted stderr
=== cmd 1: node bin/validate-mission.mjs missions/M-001/mission.json ===
=== cmd 2: node bin/bundle.mjs verify missions/M-001 ===
02Provenance & record
Full hashes, bundle identity, attestation, and record details
Provenance & record
Full hashes, bundle identity, attestation, and record detailsRecord details
- payment
- none · not merge-contingent
- redactions
- none recorded
- Bundle contents digest
sha256:70857a…b13b1c3- Signed asset SHA-256
sha256:90ceab…13f741b- Signed provenance recorded
- verified
Full cryptographic values
Full recorded values. The compact receipt above shortens these for legibility only.
- Container image digest
node@sha256:2cf067cfed83d5ea958367df9f966191a942351a2df77d6f0193e162b5febfc0- Bundle contents digest
sha256:70857aa3ed190d1bde8e468e6a6d7260aafaf0da83891f016031055feb13b1c3- Signed asset SHA-256
sha256:90ceabf13f47e43b4c8ff3e80128a88dac9881d9420579766da09c88b13f741b
Signed bundle
Verify this receipt
gh attestation verify run-record-M-003.tar.gz --repo northset-oss/verification-pilot --signer-workflow northset-oss/verification-pilot/.github/workflows/attest-bundle.ymlAttestation confirms that Northset's signing workflow produced this exact bundle. The signer does not witness the recorded run, and verification does not turn it into maintainer verification.
QR → receipt page