Touchstone

The unit of verification

Controls

A control is a machine-checkable claim compiled from the issuer's own words. It names its subject, cites the exact bytes it came from, and states a predicate an engine can evaluate without judgment. Below is a real one, dissected — as signed in sequence 1.

Anatomy of a control

This control was evaluated in sequence 1 and satisfied. Every field below is reproduced byte-exactly from the signed bundle.

ustb-one-day-yield-present

SATISFIED
Subject
Superstate USTB one-day yield figure is published
One sentence stating what is checked. Written by the compiler, approved by a human.
Cited span
"one_day":0.03519765645878166
The byte-exact span of the issuer document the compiler cited when it proposed this control. Compile-time evidence, not this epoch's observation.
Source
superstate-ustb-yield · issuer-api
Where evidence comes from, and what kind of authority it is. An issuer API proves publication, not truth.
Adapter
ustb-yield
The deterministic code path that retrieves and normalizes evidence for this control.
Predicate
exists · field = one_day
The operator and expected value. This one asserts the field is present in qualifying evidence.
Cadence
business-daily · grace period 1
How often evidence is expected, and how many periods may lapse before absence counts against the asset.
Effective from
2026-08-14
The date the control is in force from. No end date is set.
Compiler confidence
0.85
The compiler's own confidence in the candidate. Candidates below 0.8 are abstained from automatically and never reach a human.
Approval state
approved
Approval changes exactly two fields — approval_state and compilation_sha256. Nothing else about a control can be edited by a human.
Compilation
8724e933…1fba6b5eshow full value 8724e9338d92f60055720f6a1fe3b7307c22a9c4b57e8e52b76c62dc1fba6b5e
The compilation artifact this control was accepted in. The control is read from that artifact; the approval ledger can only point at it, never restate it.
Content hash
1b71225f…21b348a7show full value 1b71225f38aad052fc8ccd7f29e7bde1568a82dfad2e62f7dff983d921b348a7
SHA-256 over the control's canonical bytes. The signed report references the control by this hash; change one byte and the hash changes.
Evaluated
0.035406030377782935 on 2026-08-16
What sequence 1's evaluation observed for this control, and the row date it belongs to.
See all eight controls as evaluated in sequence 1

From proposal to report

  1. Proposed

    A model reads the issuer's published documents and proposes candidate controls. Each cites the exact bytes it was drawn from and carries the compiler's own confidence.

  2. Gated

    Deterministic checks screen every candidate. A candidate below 0.8 confidence is abstained from — recorded in the compilation artifact, never shown to a human as approvable.

  3. Approved or declined

    A human approves or declines each surviving candidate. Approval may change only approval_state and compilation_sha256. Declines are recorded with reasons.

  4. Evaluated

    Each epoch, the engine retrieves fresh evidence and evaluates every approved control. A control the evidence cannot answer is reported unevaluable, not skipped.

  5. Reported

    Results are bound into a report by content hash and control set root, signed with Ed25519, and published to the registry on X Layer testnet.

Declined is recorded too

The approval ledger keeps what a human turned down, next to what was approved. In its own words:

Declined entries are candidates that passed every deterministic gate and a human still did not approve — recorded because a control set that silently omits them cannot be audited for why.

approval ledger, sequence 1

holdings-line-items-present

Declined 2026-08-16

“holdings is a collection, and whether exists means 'present' or 'non-empty' is undefined in the control language. Deciding that here would smuggle in a semantics change as an approval.”

ustb-fund-identifier-stable

Declined 2026-08-16

“The expected_value is a literal fund identifier, but eq compares decimals: the evaluator resolves expected_value['value'] to a Decimal and returns UNEVALUABLE when it cannot. Approval may change only approval_state and compilation_sha256, so this cannot be repaired by approving it.”

The control dissected above belongs to the eight-control set sequence 1 was signed under. The project has since approved a different, five-control set, which applies only to later sequences.