Where AI governance meets operational reality.

EVIDENCE DISCIPLINE

A claim must remain inside the evidence.

Keep the source record, its stated basis, the verification performed and the resulting finding distinct. A conclusion can extend only as far as the examined record supports.

Verification is an activity that must be described. It is not a label that strengthens a record by itself.

Explore the record properties →

RECORD PROPERTIES

Preserve what a reader needs to inspect.

A record’s presence is not enough to establish its sufficiency. Preserve these five properties so another reader can examine the basis for reliance.

01 / SOURCE

Where did it come from?

Identify the record’s origin and relationship to the system or claim. Preserve the context needed to trace it.

02 / BASIS

What does the record say?

State what the record reports as observed, tested, reproduced or reviewed, and the grounds it gives. This is distinct from verification of that account.

03 / VERIFICATION

What was examined?

Describe verification against defined criteria: who or what performed it, what was done and the result. Keep unperformed checks explicit.

04 / LIMITS

Where does support stop?

State what the record does not establish beyond its scope, observation conditions or reliability limits.

05 / ABSENCE

What remains missing?

Identify expected records or signals that are missing, conflicting or unavailable. State how that affects the question rather than assuming an answer.

ANALYTICAL STATES

Do not collapse fact, interpretation and conclusion.

A reported observation, reproduced behaviour, corroborated source, inference and unsupported proposition require distinct treatment. State which kind of support is present and how it was established.

What the source reports

Attribute the claim to its source. A report of a test is not the same as independently reproducing that test.

What examination establishes

Describe corroboration, reproduction or other verification actually performed, with its criteria and limits.

What analysis infers

Make the reasoning and assumptions visible. Keep unsupported propositions unresolved rather than presenting them as findings.

NEGATIVE EVIDENCE

What did not happen belongs in the record.

Missing logs, failed reproductions, refused access, absent controls and unresolved contradictions may affect the examination. Their significance must be established within scope.

Notably Absent

Record relevant non-events and missing evidence alongside positive observations. Distinguish an observed non-event from an event that was not observable because the necessary records or access were unavailable.

No record of an event is not, by itself, proof that the event did not occur. A failed reproduction does not establish that the reported behaviour is impossible.

CONCLUSION BOUNDARY

Scope travels with the finding.

System version, operating period, environment, criteria, exclusions and limitations constrain the conclusion. Reuse in another setting requires a renewed basis.

Preserve the original finding and link later reviews to it. New evidence should not silently rewrite what an earlier record supported.