Nicholas Dunzelman

Proof-route regression suite ยท checked May 19, 2026

One pre-leverage gate for the whole route.

One pre-leverage gate checks role source, staleness refusal, renewal repair, draft quality, route index, ledger projection, public URLs, privacy hygiene, and no-outbound state before the proof route can be used.

Decision Ready
Checks 9/9
Average 4.7/5
Next Watch
  1. role_sourceRole marker stays current.The target-role page must still expose the expected AI Deployment Engineer signal. Verifier: curl role page. Score 5/5
  2. stalenessRefusal gate remains executable.The sentinel must reject stale route evidence instead of letting it become leverage. Verifier: validate-staleness-sentinel. Score 5/5
  3. renewalRepair path is available.The renewal drill must turn a stale finding into local repair work. Verifier: validate-renewal-drill. Score 5/5
  4. draft_qualityPost-gate text is scored first.Any future note must pass freshness, recipient fit, new proof, claim safety, repetition, link economy, and date-gate checks. Verifier: validate-follow-up-draft-eval. Score 4/5
  5. route_indexThe reviewer path names this gate.The public route index must expose the regression branch, not a stale next-step claim. Verifier: curl route index. Score 4/5
  6. ledgerReceipt projection matches source truth.The public JSON summary must carry the latest proof-route receipt and URL map. Verifier: curl ledger summary. Score 5/5
  7. public_urlStatus page is live.The autonomy surface must show the current branch and public-check set. Verifier: curl autonomy status. Score 4/5
  8. privacyThe public pack stays clean.The verifier must catch private paths, hidden identifiers, protected-claim drift, and unsafe public-pack changes. Verifier: python3 scripts/verify_public_pack.py. Score 5/5
  9. no_outboundThe date gate stays closed.The route remains local until May 26, 2026, a real reply, or a fresh explicit override. Verifier: rg "2026-05-26|no_outbound". Score 5/5
  1. python3 tools/deployment_receipt.py validate-regression-suite --input examples/proof_route_regression_suite.json
  2. python3 tools/deployment_receipt.py regression-suite --input examples/proof_route_regression_suite.json
  3. python3 scripts/verify_public_pack.py
  4. python3 -m unittest tests/test_proof_ledger.py tests/test_deployment_receipt.py

The regression suite does not send, schedule, address, or authorize external contact. It blocks the route when a marker fails and points the next local repair step at the exact broken surface.

It does not claim target-company affiliation, endorsement, employment, customer deployment, revenue, incorporation, funding, legal status, trademark ownership, or production results.