SwitchboardSBSwitchboardhistorical receipt · self-issued
archive · July 2026

A historical build receipt.

This receipt covers the July 2026 website build at commit 5b33cd7. It does not cover the current website revision. Its build, typecheck and fixture-suite claims were graded by buildReceiptIssuedV2 against transcripts saved in the repo. The original record and its limits are preserved below.

Receipt of Governed Work
switchboard-website · issued 03 Jul 2026, 18:20 UTC
No.rcv2-a4c19e02d7f38b56Historical · July 2026 · self-issued
Mode when issued
Performed by
claude-code · claude-fable-5
Acceptance
Score reporting
Status

Current, with limits:

  • Research-mode receipt — not a basis for live execution decisions.
  • Self-issued — treat every disposition as the builder grading itself until the independent lane re-assesses.
Verdict
cautioned

Partially verified — one claim couldn’t be backed by evidence.

  • 1 claim(s) unsubstantiated
What was asked

Rebuild apps/web as the one-page Lit Artifact landing with notes, diligence, and receipt routes — a static proof of concept where every displayed artifact recomputes through the real @switchboard/core builders.

Scope held: 4/4 scope checks passed.

In the agent’s own words

“This site is the artifact: the production build, strict typecheck, and fixture suites pass with zero API routes and zero environment variables, and every receipt shown recomputes through the exported @switchboard/core builders. Rendering beyond Chromium is unexercised, and this receipt is self-issued — the independent lane has not re-assessed it.”

Reported outcome: completed. This paragraph is the agent’s claim — the verdict above is what the record supports.

The claims, checked — seven of them

This site is the artifact: the production build, strict typecheck, and fixture suites pass with zero API routes and zero environment variables, and every receipt shown recomputes through the exported @switchboard/core builders. Rendering beyond Chromium is unexercised, and this receipt is self-issued — the independent lane has not re-assessed it.

Backed by a recorded check — “pnpm --filter @switchboard/web build — production build completes; zero api rout…”

The production build completes with zero API routes and all pages prerendered.

Backed by a recorded check — “pnpm --filter @switchboard/web build — production build completes; zero api rout…”

The fixture suites pass against the real core schemas.

Backed by a recorded check — “pnpm --filter @switchboard/web test — fixture suites green against the real core…”

The strict typecheck exits 0 with no errors.

Backed by a recorded check — “pnpm --filter @switchboard/web exec tsc --noemit — strict typecheck exits 0 with…”

Every displayed artifact parses through the exported @switchboard/core zod schemas.

Matches evidence on file — “captured vitest transcript: the landing and diligence fixture suites (52 tests) …”

Rendering holds in Safari and Firefox.

Nothing in the recorded evidence backs this claim.

Froze this receipt at issuance with pinned identity so server and client render identically.

Matches evidence on file — “captured next build transcript lists every route as prerendered static content w…”
What was checked — four recorded checks
passpnpm --filter @switchboard/web build — production build completes; zero API routes, all pages prerendered
passpnpm --filter @switchboard/web test — fixture suites green against the real core schemas
passpnpm --filter @switchboard/web exec tsc --noEmit — strict typecheck exits 0 with no errors
passTest "fixture-validation suites (vitest)" — passed
Evidence on file
saved during the run
3
rebuilt afterwards
0
derived
0
evidence index
on file

Evidence saved while the work ran counts for more than evidence assembled afterwards.

Still open — four items
cautionSelf-issued: the builder and the issuer are the same lane; the independent evaluation lane has not re-assessed this work.
cautionScreenshot QA ran in Chromium only; Safari and Firefox are unexercised.
unresolvedRe-issue after the landing-integration commit lands so the covered tree and the deployed tree coincide.
degrades_confidenceRe-issue after the landing-integration commit lands so the covered tree and the deployed tree coincide.

This piece of work could be signed off at issuance — the open items are noted, not blocking.

Next planned step: Independent evaluation + re-issue against the shipped commit

Since issuance — two events, nothing erased
limit applied03 Jul 2026, 18:22 UTC

Issued in research mode — reliance is bounded to research use.

Limit: Research-mode receipt — not a basis for live execution decisions.

limit applied03 Jul 2026, 18:23 UTC

The builder issued its own receipt; the independent evaluation lane has not run.

Limit: Self-issued — treat every disposition as the builder grading itself until the independent lane re-assesses.

Same record, two renderings — exact field names, lineage identifiers, and hashes are in the machine view.

Self-issued. That’s the point of the independent lane — read the essay →

Of the structural guarantees on /exit, this receipt is missing one — independent evaluation. runEvaluation ships in the same package as the builder and runs in the same process, invoked by the operator who ran the work.

proof artifacts: .switchboard/proof/dispatch-web-lit-001 · issued 3 July 2026 from the working tree at commit 5b33cd7 · a new revision needs its own receipt