Skip to main content
Early pricing is live. Start free for up to 3 AI systems — no card, no time limit.Early pricing is live. Free for up to 3 AI systems.
All docs
Explanation

How evidence is approved

The three evidence states, who moves a claim between them, and what a state does and does not prove.

5 minFor: Finance reviewer, Workspace owner

Three states

A GL-backed value claim is in exactly one of three states. The state names are the product's; the labels are what the Value claims page shows.

Validate GL evidenceFinal attestationAuthor submitsSubmit for validationself_reportedAwaiting independent validationvalidator_confirmedAwaiting final attestationaudit_signed_offFinal-attestedby a Validator who did not author itby an Administrator, Governance lead or Attestor
three states, three different people; a state is an internal review status, not external assurance · source evidence-states.mmd
StateLabelEntered by
self_reportedAwaiting independent validationThe author, with Submit for validation: an AI system, a retained GL credit and a causal explanation.
validator_confirmedAwaiting final attestationA Validator who is not the author, with Validate GL evidence.
audit_signed_offFinal-attestedAn Administrator, Governance lead or Attestor, with Final attestation.

A claim's substantiated amount is the gross GL-backed benefit less a stated attribution reserve. The reserve is shown as its own line, never hidden in the figure.

Separation of duties

  • The author cannot validate. The validate control does not appear on a claim the signed-in person authored.
  • A Validator cannot final-sign. The roles that can are listed in the table above and nowhere else.
  • A Contributor can author and never approve. An Auditor can read every state and change none.
  • Every transition is one entry in the audit chain, with the actor, so the sequence of three people is reconstructible.

The role sets are in Who can do what, and a backend test keeps them identical to the server's.

Confidence on the Scorecard

When enabled for your organization

The Scorecard screens are switched on by Oabo for a deployment, and are off in production as of release 0.3.0.

On the Scorecard a benefit does not have a state of its own. An administrator links it to a value claim or a guided-proof claim in the same organization, and its confidence is worked out from the link each time it is read:

Linked toConfidence
A value claim that is Final-attestedVerified
A value claim that is Awaiting final attestation, or a guided-proof claim with a source on recordMeasured
Nothing, a self-reported claim, or staff-reported hours cited beside the benefitEstimated

A benefit takes its best link; a use case takes its lowest benefit; the report sentence names the lowest across the month. Linking never changes an amount, and unlinking is audited like linking.

What a state does not mean

  • Final-attested is an internal review status. It is not external assurance, and no Oabo state claims to be.
  • No state proves causality. The causal explanation is a stated argument that a validator and an attestor accepted; it is recorded as such.
  • A validated claim is not a verified system. A system's verified badge is earned by measured spend, not by a claim.
  • Staff-reported hours are a statement, not a measurement. Citing them keeps a benefit Estimated, by design.

Previous

Cost coverage

Last documented 2026-11-18 against master fb17e1c5. Live release 0.3.1.