Your agents write. Your humans sign. Proof remembers.

Sheet 1 of 1 · General arrangement
DWG No.
PRF-10
Scale
One component
Date
Continuous
Drawn by
Proof (automated)
Checked by
Named reviewer, always
Zone A — FIG. 0 · Assurance system, general arrangement One drawing. It is animated because your org is.
COMMITS → SAME BAR — HUMAN OR AGENT → SHIP · PRODUCTION EVERY FINDING SIGNED BY NAME ENGINEERS SIGN THE PROMISES FINDING → AGENT-READY FIX PROMPT EVERY FIX → A PERMANENT PIN FIG. 1 — YOUR AGENTS CODE AUTHORS HUMAN + AI N SEATS FIG. 2 — THE GATE 52 CHECKS EXIT ≠ 0 UNTIL PROMISES HOLD FIG. 3 — THE CORPUS REQUIREMENTS · PINS · PROOFS · HAZARDS 123 APPROVED — AND COUNTING REPRODUCER MIN. FIG. 4 — YOUR HUMANS SIGNATURES REVIEW · APPROVE · SIGN SIGNED: ____________ DATE: ______
Commit — human or agent, same path Finding — returned as a fix prompt Corpus layer — a permanent pin

← Drag to pan the drawing →

Zone B — Detail views · enlarged, as noted

Four details from the general arrangement.

Detail A — The gate, 4:1

Fifty-two checks stand between every commit and production: formal proof obligations, requirement coverage, mutation adequacy, hazard traces. The gate exits non-zero until the promises hold — no judgment calls, no “looks fine to me.”

It grades human code and agent code by the same bar. That is the point: when authorship gets cheap, the gate is what stays expensive to fool.

  • 52 checks per audit run
  • Exit ≠ 0 until promises hold
  • Same bar — human or agent

Detail B — The corpus, 4:1

On jsonparser, the corpus holds 123 approved requirements. Every miss is root-caused, its siblings swept — one panic class was traced to eight sites and closed at all eight — and the class goes extinct.

Every fix becomes a permanent pin. The corpus never forgets a lesson, never rotates off the team, never needs re-onboarding. Quarter by quarter, another component joins it.

  • 123 approved requirements
  • Panic class swept @ 8 sites
  • Every fix → permanent pin

Detail C — The loop, 4:1

A finding is not a ticket — it is a reproducer plus an agent-ready fix prompt. Hand it to your engineers, paste it to your agents, or let our fix sprints take it. Three inlets, one gate: whoever writes the fix, the same 52 checks grade it.

The loop closes when the reproducer passes and the pin is set — not when someone says it is done.

  • Findings carry agent-ready prompts
  • Your engineers · your agents · our fix sprints
  • The gate grades all three the same

Detail D — The record, 4:1

This drawing includes our errors. One escaped defect stands on the public register: a Set() miss that slipped through with 100% MC/DC coverage at the point of escape. The postmortem is published next to the seven findings we did catch.

An assurance vendor that hides its misses is selling you the same optimism you already have. Ours are on the register, root-caused, pinned.

  • 7 findings on the public register
  • 1 escape — Set() miss, postmortem public
  • 100% MC/DC at the escape — coverage is not correctness
Zone C — Specifications · materials & methods

What the gate is made of.

Formal verification
Kind2 + Z3 model checking — mathematical proof where testing cannot reach
Requirement language
FRETish — NASA's structured requirement notation; every promise machine-checkable
Coverage discipline
MC/DC — the avionics standard, applied across 11 languages
Safety analysis
Hazard analysis — what must never happen, traced to the code that prevents it
Accountability
Named signatures — every finding and every approval signed by a person, by name
Field conditions — why this component exists
46%
of developers distrust AI-generated code — Stack Overflow survey
33%
trust it — the gap between the two is where escapes live
90%
of teams now ship AI-written code — DORA
30%
trust what it writes — DORA. Proof exists for the other 60 points
Zone D — Issue for scoping
Issue request for scoping FORM PRF-10/A
Commercial
Fixed fee
Scope
One component
Duration
≈ 4 weeks
Then
Continuous

We audit one component of your system, end to end. You get the corpus, the findings, and the gate — and the drawing above becomes a drawing of your org. Start with an email; that is all step one needs.

CHECKED BY: NAMED REVIEWER, ALWAYS
■ RECEIVED — LOGGED FOR SCOPING

A named person replies within one working day. No sequence, no drip — one email, from an engineer.