PARTNERS

Add selected Workbench capabilities through bounded OEM and partner integrations

Deliverablesdeliverable
deliverable

Evidence Pillar Figures

Canonical figures for the Evidence pillar.

Public sample
Client deliverable
public-sample
System
Evidence Pillar Figures
Environment
Production pilot

# Evidence Pillar Figures

EVD-01

What Evidence Makes Defensible

Evidence preserves provenance, validation state, and retest history so technical findings can support real decisions.

Three-part figure showing observations and test outputs becoming governed evidence and decision-ready artifacts.

INPUTSTechnical source materialObserved behaviorReproduced findingsTraces andconfigurationRetest resultsENGINEEvidencePreserveprovenanceAssign explicitclaim stateLink finding,control, andretestRecord analystreviewRESULTSDefensible decision artifactsTechnicalevidence objectOperationalremediationrecordDecision-readysummaryReusableregression proof
EVD-02

Evidence Lifecycle

Evidence moves from observation through validation, remediation, retest, and controlled reuse without losing claim state.

Governed evidence lifecycle from observation and reproduction through validation, remediation, retest, closure, residual risk, and reuse.

Evidence lifecycle
  1. 1
    Observe
    Capture source behavior, configuration, trace, or artifact.
  2. 2
    Reproduce
    Confirm the behavior under controlled and documented conditions.
  3. 3
    Validate
    Challenge evidence, ordering, alternatives, and consequence.
  4. 4
    Remediate
    Record the selected control, owner, and expected evidence.
  5. 5
    Retest
    Replay the supported path and verify the control outcome.
  6. 6
    Reuse deliberately
    Carry forward only the evidence and claim state appropriate to the new context.
Retest loop returns to Reproduce
What state does the evidence support?
  • Grounded
  • Inferred
  • Rejected
  • Residual
EVD-03

Claim State Boundary

Observed, reproduced, grounded, inferred, rejected, and analyst-reviewed claims must remain visibly distinct.

Diagram showing observations and reproductions, grounded claims, review boundary, explicit inference, rejected claims, and analyst-reviewed publication state.

SUPPORTED CLAIMSupported claimGroundedQualified consequenceProvenance retainedPublication state approved1Observed

A behavior, artifact, configuration, or trace was directly captured.

2Reproduced

The behavior was repeated under controlled conditions.

3Challenge evidence and alternatives

Review tests source sufficiency and plausible alternative explanations.

4Approve publication state

An analyst confirms the claim language, caveats, and release boundary.

5Inferred

Plausible extension that remains explicitly provisional.

6Rejected

Unsupported, contradicted, or not reproducible.

7Unresolved

Evidence is insufficient for a defensible conclusion.

EVD-04

Evidence-to-Decision Stack

Executive conclusions remain trustworthy only when they stay traceable to technical evidence and replayable proof.

Layered artifact stack from observed evidence and structured findings through remediation and retest records to technical and executive reporting.

PROVENANCE CONTROLSSource referencesVersion andgenerated timeReview and approvalstateObserved and reproduced evidenceRuntime tracesConfiguration and policy snapshotsReproduction recordStructured findings and pathsFinding objectPath and relationship objectClaim and validation stateRemediation and retestControl and owner recordRetest resultRegression fixtureDecision-ready reportingTechnical reportExecutive summaryDecision recordCONSUMERSEngineeringSecurityLeadership