Where AI governance meets operational reality.

EVIDENCE RECONSTRUCTION

Restore traceability. Preserve the gaps.

Logs, tickets, tests and approvals may exist without forming a coherent record of control operation or decision history. Reconstruction examines whether those existing fragments can be linked to a defined claim.

A reconstructed record must distinguish verified relationships, inference and unresolved gaps.

Explore the reconstruction method →

WHEN IT APPLIES

The record is fragmented, not necessarily absent.

Relevant evidence may be scattered across teams, tools and repositories. The question is whether those fragments can be connected to a particular claim, system state, time and criterion.

For example, an approval may refer to a release without identifying the deployed configuration. A test result may exist without a reliable link to the version it examined. Reconstruction investigates those relationships; it does not presume they can be established.

THE METHOD

Locate. Bind. Check. Record gaps.

Preserve the usable record and the limits of reconstruction at each step.

01 / LOCATE

Identify the fragments.

Locate relevant operational artifacts within authorised repositories. Record their source and collection context.

02 / BIND

Establish the relationship.

Connect each artifact to the system state, owner, time and control claim where the record supports that link.

03 / CHECK

Examine the basis.

Verify basis, integrity and relevance against defined criteria. Keep a proposed relationship distinct from one that has been verified.

04 / RECORD GAPS

Keep uncertainty visible.

Identify stale, contradictory and unavailable material. State what remains inferred, unresolved or outside scope.

OUTPUT BOUNDARY

An inferred link remains an inference.

The final record should identify the source artifacts, relationships established, basis for verification and points where traceability stops. Later explanations must remain distinguishable from records created at the time of the event.

Notably Absent

  • No manufactured event or substitute for a missing original record.
  • No unverified record represented as verified.
  • No absence of a log treated as proof that an event did not occur.
  • No system-wide assurance, certification or compliance finding inferred from reconstructed links alone.

Explore inference and evidence limits →

NEXT STEP

Bring a fragmented evidence chain.

Describe the claim to be examined, the system and period involved, and the repositories where records may be held. Identify your authority to commission the work and any known constraints.

Share a non-confidential description initially. Technical reconstruction begins only under an agreed paid scope, with independence checks, data permissions, handling arrangements and payment in place.