Decision and Action History
Guide status: Governance contract. Last reviewed 14 August 2026. Implemented receipt, history and audit fields must be verified in the installed version.
Purpose
Liva 7 should keep the chain from evidence to outcome understandable. Decision receipts, action records and audit history allow a merchant to know why work was proposed, who or what authorised it, what actually changed, whether the storefront was verified and what was later observed.
Three connected records
A decision receipt records the recommendation, evidence snapshot or reference, chosen response, reason, scope, authority, decision-maker and time. It establishes intent.
An action record records the requested change, target, applicable policy, execution state, actual result, exceptions and verification. It establishes what did or did not happen.
An outcome review records the measurement definition, window, observed result, evidence standard, guardrails, limitations and follow-up decision. It establishes what was learned without automatically claiming causality.
Action states
Useful states distinguish prepared, waiting for approval, approved, executing, completed, verified, declined, deferred, failed and cancelled. A completed internal operation is not the same as a verified live storefront change. Failure should preserve the last known safe state and a reason that a human can act on.
Record quality
- Use stable identifiers and timestamps.
- Keep the store, market, products, audiences, placements and theme in scope.
- Reference the evidence class, freshness and material limitations.
- Identify whether authority came from a person or an active policy.
- Record platform-controlled steps separately from Liva 7 preparation.
- Append corrections or later states without silently rewriting the original decision.
Use history operationally
Review history during handovers, repeated failures, policy review and outcome analysis. Look for recommendations repeatedly dismissed for the same reason, actions frequently reaching fallback, or policies that no longer match store structure. History should improve judgement, not become a stream of unactionable events.
Privacy and access
Record the minimum customer data required. Restrict sensitive operational and customer context to appropriate roles, apply the retention policy and never include secrets. A support export should remove or minimise customer-level information by default.
You are finished when
- another authorised person can reconstruct the decision and execution;
- approval, action, publication, verification and outcome are distinct;
- exceptions and limitations are preserved; and
- the record is useful without exposing unnecessary data.