One claim in context.
Name the system and version, operating environment, relevant period and the claim that needs examination. Identify the records you know exist; send no credentials or sensitive evidence with the first enquiry.
EVIDENCE READINESS PILOT
One system. One bounded assurance question. One defined evidence base.
The Pilot is a controlled starting point for examining whether existing records can support a specific claim about a defined system and operating context.
ODA3 / EVIDENCE SYSTEM↗
ONE BOUNDED QUESTION
01
SYSTEMIdentify the subject
02
RECORDExamine the evidence
03
OUTPUTState finding and limits
No blanket maturity or certification claim.
THE EXAMINATION QUESTION
What does the available record establish?
We define the claim, scope and control context, then examine the records that actually exist. A question can remain unresolved when the evidence is unavailable, stale, contradictory or outside scope.
HOW IT WORKS
Work backward from the conclusion sought.
The examination record follows Question → Scope → Control Context → Evidence → Provenance → Verification → Finding → Limitation.
Define
System, period, claim, criterion and exclusions.
Examine
Records, source, operating state and checks against defined criteria.
Record
Supported finding, material gaps and limits.
THE BOUNDED PILOT
Know what enters the examination and what comes out.
The final scope is agreed in writing before any records are examined. This describes the scoping route, not a promise of a particular finding.
A testable boundary.
ODA3 documents the question, applicable criteria, permitted inputs, exclusions, evidence use and review terms before examination begins.
Records that actually exist.
Source, provenance, integrity, relevance and conflicts are checked against defined criteria. Missing or contradictory evidence remains visible.
A bounded record.
The finding states support, partial support, gap or unknown as warranted by the method; it identifies limitations and what further evidence would change the answer.
Outside this Pilot: certification, a general safety or compliance claim, and conclusions about unexamined systems, versions, environments or periods.
THE OUTPUT
A bounded evidence-readiness finding.
The output records what examined evidence supports, what it does not support, and what additional evidence would be needed for a stronger conclusion. It can inform later evidence engineering or assurance work without assuming either in advance.
NOTABLY ABSENT
The Pilot is not certification.
It is not a blanket maturity score, an assertion that a system is safe or compliant, or a way to resolve missing evidence by assumption. The result does not extend to unexamined versions, periods or environments.
START WITH A QUESTION
Describe the claim, not your entire environment.
A short written note can establish whether a bounded Pilot is appropriate. ODA3 would ask for the system and claim, the operating context, known records and any immediate constraint. Sensitive files and credentials are not requested at this stage.
INITIAL SCOPING NOTE
“For system [name/version], in [environment/period], what do the available records establish about [specific behavior or control]?”
Illustrative wording only. Use the contact route to discuss scope; do not send credentials or sensitive evidence in the first enquiry.
BEGIN
Send a question and the evidence you already have.
A short written note is sufficient to scope whether the Pilot is a fit.