Production Records
Reconstruct what happened during a production Run.
A Production Record keeps the Workload, lifecycle, supplier attempts, effective policy, recorded cost, and evidence gaps together in one exportable operational record.
Keep operating context and later events in the same history.
The record preserves what Acta observed while stating where supplier behavior or business success remains unverified.
Workload and Run identity
Stable Workload identity, unique Run identity, configuration fingerprints, and idempotency.
Preserves the operating context for the Run.
Run lifecycle
Pending, running, waiting, completed, failed, cancelled, and expired states.
Operational completion does not prove that the business accepted the result.
Model and provider history
Requested model, resolved model, supplier attempts, failures, and failover.
Preserves dispatch history without claiming supplier-internal facts.
Effective policy
Access, routing, and privacy policy snapshots associated with the Run.
A policy snapshot does not prove every supplier behavior.
Cost coverage
Acta-recorded cost and explicit states for external or incomplete coverage.
Customer-endpoint infrastructure may remain externally billed or unknown.
Content-free export
Identity, lifecycle, supplier attempts, policy snapshots, cost coverage, and a digest.
Prompt and response content are excluded from the export.
Give accountable owners the same operating history.
Each team can review the fields it owns without losing the common Workload and Run identity.
- CIO and CTO
- Route, supplier attempts, lifecycle, and configuration history
- CFO
- Recorded model cost, attribution, and coverage gaps
- CISO
- Policy snapshots, suppliers, privacy mode, and unknowns
- Workflow owner
- Run status and unresolved evidence needed for a business decision
Build the operating record before the next production change.
Start with one live Workload and preserve what ran, under which controls, at what recorded cost, and with which evidence gaps.