The Verification Foundry
An operable model of Dino: discover an API, sign in without the agent ever holding the secret, a human approval, autonomous testing under budgets, and a sealed result anyone can check.
An operable model of Dino: discover an API, sign in without the agent ever holding the secret, a human approval, autonomous testing under budgets, and a sealed result anyone can check.
Exhibit 02 · Dino
Changes one byte after sealing.
Authorisation: probing the running API.
done
Reads the schema from live introspection and inventories all 37 operations.
done
An OAuth2 client secret is needed. The agent sends the person a link; they enter it into custody themselves. The agent never sees it.
done
The agent proposes where and how the scan runs. Only the person can authorise it; Dino refuses that decision from the agent.
running · seven agents in sequence
Each agent probes one failure class of the running API under a share of the time budget.
Findings are grouped by operation. Anything that looks like a credential is redacted before evidence is stored.
One constructor builds the result as canonical bytes. Its SHA-256 is the digest that gets signed.
The digest is recomputed from the bytes and matches. The result is verified offline.
The digest is a real SHA-256 of the sealed result: tamper with one byte and it no longer matches.
An assay bench. The API under test is the specimen on the left, its operations laid out as tiles under a survey gantry. The front edge belongs to people: a sealed slot where a secret goes into custody, an approval stamp, a budget gauge and a check lamp. The agent's cart rides a rail along the back. It follows the work everywhere, but it cannot reach the front.
Once a person authorises the run, the specimen rides the line past seven test stations, one for each failure class Dino tests. It passes through a redaction shutter, and a press stamps the result into a sealed record.
The record the press stamps is a canonical serialisation of the synthetic result: sorted keys, no whitespace. The digest in the readout is its actual SHA-256, computed in your browser, so the tamper check is a real check.