NORTHSET

Proof-of-Pass Receipt

Receipt ID M-176

ISSUE / WORKThrow helpful error when `number` option is invalid · PR #186

CONTRIBUTOR SELF-RUN — NOT MAINTAINER VERIFICATION

RUN

01 / TECHNICAL RESULT

Technical result

1/1

declared commands passed

Recorded on the named code in the named execution environment. The evidence annex carries the exact scope.

Upstream
OPENmutable external state
Attempts
2 totalcurrent M-176 · #2
Cost record
PARTIALunpriced

02 / RECORDED WORK SEQUENCE

Northset Proofline

Every task-bound attempt is shown in recorded order. Anatomy geometry follows each non-null elapsed duration’s share; labels retain exact recorded time.

  1. ATTEMPT 1M-175FAILED INFRA TERMINALinfrastructure
  2. ATTEMPT 2M-176READY

ATTEMPT 2 / EXECUTION ANATOMY

01Discoverynot captured
02Qualification2m52s68.3%
03Authoring1m06s26.4%
04Verification13.3s5.3%

03 / ECONOMIC NARRATIVE

Economic identity

Observed sponsorship, authorization, scope, transfer, and outcome. No estimates or inferred value.

  1. 01 / MANDATE

    Sponsored and authorized

    The recorded mandate names both its sponsor and initiative, with authorization tied to a named approver and approval time.

    SPONSORNorthset OSS Fund · OSS mission experimentation

    AUTHORIZEDinternal-user:aeziz ·

  2. 02 / WORK

    Demand became scoped work

    An external issue invitation became a stable task and a recorded code-and-test scope, without treating scope as a measure of value.

    TASKTASK-OSS-AFF06F41E4AFA0E0 · defect fix · attempt 2

    INVITATIONIssue #22 · label

    SCOPE2 files · 16 changed lines · 1 production files · 1 test files · 1 declared check

  3. 03 / EXTERNAL OUTCOME

    Transfer and upstream state

    The recorded maintainer transfer and its contingency are separate from upstream state, which remains a mutable external observation.

    MAINTAINER TRANSFERnone · not merge contingent

    UPSTREAMOPEN · mutable external observation

04 / COST COMPLETENESS

Known, unknown, and unpriced

Known: maintainer payment was none. A known zero external transfer is not a zero total cost.

Missing or unpriced components

  • model inference
  • actual host compute
  • human review
  • shared tooling
TOTAL COSTUNPRICED

No complete total is recorded; see the missing or unpriced component record above.

Evidence annexEconomic · technical · provenance · limitations
01

Economic evidence

Lineage, usage, caps, outcome, and cost provenance

Attempt lineage

  • M-175attempt 1 · FAILED INFRA TERMINAL · infrastructure
  • M-176attempt 2 · READY

Recorded usage

requested reviewer model
gpt-5.6-sol
actual reviewer model
not captured
requested author model
gpt-5.6-sol
actual author model
not captured
networked setup phase
7.9s
install-only duration
not captured
declared commands
1.4s
unclassified executor time
4s
CPU time
not captured
peak RSS
not captured

Configured resource envelope

CPU cap
2
memory cap
4096 MB
PID cap
512
command wall cap
1800s
output cap / stream
2000000 bytes

Configured limits are an envelope, not observed consumption.

Cost lines

  • maintainer paymentobserved quantity unpriced · 0 external transfer · amount unavailable

Cost status: partial. Values without source-backed quantities and rates remain null.

Outcome facts

technical checks passed
true
PR opened
true
CI
pending
merged
false
accepted as submitted
not established
external cycle time
not captured
released
not observed
deployed
not observed
business result
not observed
02

Technical evidence

Code, environment, exact commands, patch, and outputs

Project

gr2m/github-project

Work

Throw helpful error when `number` option is invalid · PR #186

Verification execution

runtime: northset-oss executor v1
human operator: aeziz

Code

base
64182013ac77df26d96dce3ba49a008015a9a600
recorded patch commit
dad4d74f7c11eb20d8783d43caa4b29b850bd320
declared metadata; not execution-bound
patch diff SHA-256
sha256:c94ba3d9a8d05706f251446af82c90bf1ec3c46b18a16a7fe88c70797b460b05
bound to executed patch bytes

Environment

image reference
node@sha256:40ad9f3064e67d6860b4bc3fe1880b2953934fd6320ada990e45fe0efa6badd7
repository digest
node@sha256:40ad9f3064e67d6860b4bc3fe1880b2953934fd6320ada990e45fe0efa6badd7
immutable image ID
sha256:6ed6ff875e9714bb845b850b08f3ad231ccbb5848812647bcf11acdd4bd1d2f8
platform
linux/arm64
network
phaseA:bridge,phaseB:none

Declared checks

Execution summary
1/1 declared command returned exit 0 in the recorded environment

  1. ./node_modules/.bin/ava test/constructor.test.js

    exit 0 · 1.4s

run wall (derived from recorded timestamps) 13.3s

PASS — 1/1 declared command

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.

Public scope interpretation

The receipt proves the focused constructor regression only; maintainer review, CI, and merge remain independent decisions.

Committed patch.diff
diff --git a/index.js b/index.js
index c5c3d87489384a63218a5b6ba6fa52f301bf9bf5..4399473395ceb23d048e26f704b610f186f391c9 100644
--- a/index.js
+++ b/index.js
@@ -37,6 +37,10 @@ export default class GitHubProject {
   constructor(options) {
     const { owner, number, fields = {} } = options;
 
+    if (Number.isNaN(number)) {
+      throw new TypeError("The number option must be a valid number");
+    }
+
     // set octokit either from `options.octokit` or `options.token`
     const octokit =
       "token" in options
diff --git a/test/constructor.test.js b/test/constructor.test.js
index 6378b53c7d2b796ca018d131eef379644a219991..f34028279931a7defc3356fa4332ec1b48a4a74e 100644
--- a/test/constructor.test.js
+++ b/test/constructor.test.js
@@ -50,3 +50,15 @@ test("constructor with token", (t) => {
 
   t.true(project.octokit instanceof Octokit);
 });
+
+test("rejects NaN as the number option", (t) => {
+  t.throws(
+    () =>
+      new GitHubProject({
+        owner: "owner",
+        number: NaN,
+        octokit: new Octokit(),
+      }),
+    { message: "The number option must be a valid number" },
+  );
+});
Redacted stdout
=== cmd 1: ./node_modules/.bin/ava test/constructor.test.js ===

  ✔ constructor
  ✔ constructor with custom fields
  ✔ constructor with token
  ✔ rejects NaN as the number option
  ─

  4 tests passed
Redacted stderr
=== cmd 1: ./node_modules/.bin/ava test/constructor.test.js ===
03

Provenance & limitations

Bundle identity, attestation, verification, and claims boundary

Record details

payment
none · not merge-contingent
redactions
none recorded
Bundle contents digest
sha256:4336cf789521039384d0a61c7ad4b6a3b8c644aa503a3d564a40ae5eace87f5a
Signed asset SHA-256
sha256:f208b5838773e12407f556a788daa48194216ead0217f4dcef0cb8b76c6a1380
Signed provenance recorded
verified 2026-07-16T22:49:26.547Z

NOT INCLUDED

  • Does not prove code quality
  • Does not prove security
  • Contributor self-run record of Northset's own contribution; not the maintainer's verification.
  • The receipt proves the focused constructor regression only; maintainer review, CI, and merge remain independent decisions.

Signed bundle

Download signed bundle

Verify this receipt

gh attestation verify run-record-M-176-4336cf789521.tar.gz --repo northset-oss/verification-pilot --signer-workflow northset-oss/verification-pilot/.github/workflows/attest-bundle.yml

Attestation 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
Northset contributed this fix and ran its declared checks. Contributor self-run. Not maintainer verification.

Evidence of what ran — not a verdict that the code is good.

SELF-FUNDED FIELD-TESTING.

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

This page reports scoped proof-of-pass receipt evidence. 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.

Read the full Claims Boundary policy.