northset.ai

Proof-of-Pass Receipts

Proof-of-pass receipts for open-source work record exactly which declared commands returned exit 0, on named code and in a named environment. Each receipt is scoped evidence, not a verdict on code quality or maintainer approval.

Open a public requestEmail a private request

FEATURED RECEIPT

One real receipt, readable top to bottom.

  1. Declared commandsExact command evidence unfolds on the canonical receipt.
  2. Recorded environmentImage, digest, and network policy remain named.
  3. Separate outcomeLater upstream decisions stay detached from run evidence.

External status

Pull-request state and GitHub review-decision fields are mutable upstream observations, recorded at each publication envelope's observed time. They are unattested metadata and are separate from the signed run bundle.

Own-repository rehearsal archive (3)

Rehearsals exercise the receipt system. They are not external validation.

FOR MAINTAINERS

Request a private run

Maintain an open-source project? Send Northset a PR already in your queue. We run its repository-declared checks in an isolated container and return the run record privately. We do not modify the PR. Nothing is published without your approval. Free during the pilot.

The issue form is public. Do not include secrets or private repository details there; use email instead.

Already onboarded? Add northset-verify to a PR to request a run on that PR.

CLAIMS BOUNDARY

What a receipt does and does not say

A complete proof-of-pass receipt reports the exact declared commands, their recorded exit status, and the recorded execution environment from immutable evidence. Migrated legacy records that lack structured command evidence are marked incomplete and do not claim PASS.

It does not prove code quality, security, full CI coverage, production readiness, or maintainer approval. An attestation confirms bundle provenance; it does not broaden the receipt's claim.

Live upstream outcomes are detached because a later maintainer decision is a different fact from the recorded run. Read the full Claims Boundary policy.