Single Decision Audit

Open Latest Proof JSON Generate Fresh Proof

Every capability must map to a runtime service, finance use case, UI surface, source, and status.

The audited path is Signal → Context → Evidence → Decision → Control → Outcome → Learning → Impact → Replay.

Signal

proven

Invoice signal is resolved into a duplicate-payment investigation.

Source: ● LiveAgentDecisionLedger.signal_type

duplicate_invoice

Enterprise Ontology

proven

Runtime maps invoice context to domain, process, activity, and decision.

Source: ● LiveEnterprise ontology contract + ledger decision type

Domain=P2PProcess=Invoice ProcessingActivity=Duplicate Invoice Validation

Decision Ontology

proven

Decision metadata defines authority, evidence requirement, risk, and allowed outcomes as a structured runtime object.

Source: ◆ ComputedDecision ontology object derived from AgentDecisionLedger

hold_invoiceAP ManagerEvidence=4

Control Ontology

proven

Control and policy guardrails are exposed with owner, risk, control type, evidence requirements, and decision-to-risk edges.

Source: ● LiveStructured control ontology from policy agent result and decision ledger

AP-001DetectiveAP ControllerFinancial loss from duplicate payment

Evidence Fabric

proven

Evidence pack binds invoice, PO, receipt, prior payment, and supplier records to the decision.

Source: ● LiveEvidencePack + decision evidence payload

Invoice INV-778950Purchase Order PO-450009876Receipt GR-2219Prior Payment PAY-778112Supplier History Vendor 5002

Agent Runtime

proven

Agent execution or decision ledger shows the runtime produced a recommendation.

Source: ● LiveAgentExecution / AgentDecisionLedger

duplicate-payment-agent

Judgment Registry

proven

Human-grade rationale, outcome counts, and reason-code patterns preserve enterprise judgment for reuse.

Source: ● LiveJudgment registry summary from ledger rationale and historical-decision metadata

35 similar decisions28 approved/releasedEmergency maintenance supplier with delayed PO or receipt acknowledgement.

Decision Memory Runtime

proven

Prior decisions are returned as scored matches with confidence band and counterfactual context.

Source: ○ IllustrativeDecision memory from replay history, confidence metadata, and deterministic match factors

96% top similarityscored match factorscounterfactual

Outcome Runtime

proven

Outcome connects recommendation to what actually happened.

Source: ● LiveValueEventRecord.supporting_outcome_id / ledger status

HumanDecision.ACCEPTEDOUT-INV-778950-HOLD

Learning Runtime

proven

Learning is based on outcome, override, rationale, and reusable patterns.

Source: ○ IllustrativeAgentExecution.human_decision_reason + decision rationale

Supplier, amount, PO, and prior payment window matched; supervisor release remains available for emergency maintenance exception.

Impact Runtime

proven

Value attribution records risk avoided and calculates human/agent/policy contribution from runtime lineage.

Source: ● LiveValueEventRecord + Enterprise Impact Runtime

e17ba4cf-137a-4b0f-9d6c-f552ca3e36a28a9e3d93-6a17-5dc3-ab59-85a0162c679fagent=576000.0human=336000.0policy=48000.0

Autonomy Runtime

proven

Runtime records which steps were agent-performed, human-approved, or hybrid.

Source: ○ IllustrativeAgentExecution.autonomy_level / human_decision

L1_ASSISTED

Replay

proven

Replay path links signal, context, evidence, control, recommendation, action, and outcome.

Source: ● LiveLedger replay hash + value event replay reference

sha256-replay-inv-778950sha256-replay-inv-778950

Role Aggregation

proven

Impact rolls from the individual decision to analyst, team, process, function, and CFO drill path.

Source: ● LiveValueEventRecord user/team/function fields + Enterprise Impact Runtime

AnalystSupervisorTower LeadFB&T LeaderCFO

Use this page before showing additional capability pages. If this one duplicate invoice cannot traverse ontology, control, evidence, judgment, learning, impact, autonomy, and replay, the next priority is wiring and instrumentation rather than another feature.