01
Requirement
The obligation or question to be addressed.
ASSURANCE
The evidence model connects governance requirements and controls to records of system behavior, their provenance, checks against defined criteria, findings and conclusions that remain within scope.
THE OPERATING DISTINCTION
Risk management generates and governs controls and evidence. An examination asks what the evidence is sufficient to support. A policy, passing test or log entry needs context, integrity and relevance before it can support a conclusion.
THE EVIDENCE CHAIN
The chain is a conceptual model for a defined system, time and assurance question. The operational examination procedure is described separately.
01
The obligation or question to be addressed.
02
The operational condition or safeguard.
03
The records offered for examination.
04
Origin, context, system state and time.
05
Evidence verified against defined criteria.
06
What the examined record supports or leaves unresolved.
07
A conclusion confined to the stated scope and limitations.
THREE WORKING PHASES
Each phase answers a different examination question. The seven-element chain remains the record connecting the requirement to the conclusion.
REQUIREMENT → CONTROL
What exactly is being examined? Specify the claim, system version, operating context, period and criteria before selecting the relevant controls.
EVIDENCE → PROVENANCE → VERIFICATION
Can the records support examination? Establish source and provenance, verify against defined criteria, and record missing or conflicting evidence.
FINDING → BOUNDED ASSURANCE
What can the decision rely on? State the finding, its evidence basis, unresolved questions and the limits that bound any assurance conclusion.
THE EVIDENCE RECORD
An assurance-ready record must preserve its origin, stated basis, verification state, limits and meaningful absence. Reconstruction cannot manufacture a missing record.
01
Where the record came from and how it relates to the system or claim.
02
What the record states was observed, tested, reproduced or reviewed, and on what stated basis.
03
What was checked against defined criteria, by whom or by what process, and with what result.
04
What the record does not establish outside its scope.
05
What expected record, event or signal is missing, conflicting or unavailable.
SUPPORTING LAYERS
Applied research examines real evidence problems; frameworks provide context; bounded examination methods apply the model; training develops practitioner capability.
Empirical questions and evidence limits.
Control, incident, response and Physical AI context.
Scope, criteria, findings and limitations.
Repeatable practitioner use.
Where records are fragmented, evidence reconstruction examines whether existing artifacts can be linked to the relevant system, time and claim. Inferred relationships and gaps remain explicit.
Explore Evidence Reconstruction →ONE ROUTE INTO ASSESSMENT
Evidence Readiness is one assessment route, not a prerequisite for every service. A different question may call for a Bounded Control Assessment, a Bounded Assurance Engagement, research or standards work.
Start with one system, one bounded assurance question and the available records. The assessment examines whether that evidence is ready for a defined examination, where it falls short and what further work is needed.
CURRENT BOUNDARY
The evidence model and workflows are being tested through bounded examination methods. Machine-readable tooling is in development. Independent conformance testing and certification are not yet operating.
WHAT THIS MEANS IN PRACTICE
The current starting point is evidence readiness for a defined system, not generalized certification. Security, governance and assurance teams can use the result to decide what further examination or engineering is warranted.