Observed in a source record.
Example: an SAP write event or signed tool request.
PROTOTYPE · DESIGN-PARTNER STAGE
FORKIT ENTERPRISE
RECONSTRUCT THE
CONSEQUENTIAL ACTION.
Observability tells you what one component saw. Action Assurance asks whether the organization can connect human authority, agent/model, identity, tools, business systems, outcome and source evidence into one defensible record.
SIMULATED PROCUREMENT ACTION
One commitment. Eight systems of evidence.
Human→Approval ?→Purchasing agent→Claude→svc-procurement→create_purchase_order→SAP→PO #91821 · €18,400
ASSURANCEPARTIAL
Downstream effect is evidenced. Human authorization is not.
Agent traceDIRECT
IdentitySUPPORTED
Tool requestDIRECT
SAP writeDIRECT
ApprovalMISSING
CONFIDENCE IS A FIRST-CLASS FIELD
Forkit does not flatten uncertainty into “logged.”
Corroborated across sources.
Example: identity plus tool evidence agrees on the same principal and object.
Correlated, not directly proven.
Example: time/resource/business-object correlation without a shared transaction ID.
Sources disagree.
Example: agent trace names one identity while the business-system audit shows another.
Required evidence is absent.
Absence remains visible instead of being silently filled in.
FINANCE / PROCUREMENT
Commitments and approvals
Purchase orders, invoices, refunds, payments, credit and delegated approval chains.
TARGET USE CASECUSTOMER OPERATIONS
Agent-triggered changes
Refunds, account changes, service decisions and downstream CRM/ERP updates.
TARGET USE CASEACCESS / CONTROL
Authority changes
Role changes, privileged tool use and identity/permission evidence around agent actions.
TARGET USE CASE15-BUSINESS-DAY ASSURANCE SPRINT