Evidence-gated workflow
Review the evidence.
Approve the exact change.
See the proposed fields, their sources and the remaining uncertainty before deciding. Approval binds the payload, evidence snapshot and validation context.
Prepare a review
Choosing a fixture never approves or writes. Reset clears only this demonstration's in-memory state.
Snapshot-change demonstration
After preparing or approving, change a source date to test invalidation. The reviewed package below stays unchanged.
Current in-memory CRM
Evidence review package
Prepare a package to inspect the proposed change. No write has occurred.
- Company
- Request / review
- Exact action
Field changes and supporting evidence
Validation and uncertainty
Approval scope
Inspect the bound digests and complete package
Approve records a decision only. Execute rechecks the bound snapshot before the in-memory write. Reject is terminal for this review.
Review and decision history
Earlier review packages (retained snapshots)
Complete session result
Legacy automated regression scenarios (separate simulation)
These original scenarios may simulate approval automatically. They use isolated fresh state and cannot approve or write the interactive review session above.
Bounded engineering demonstration
Everything is synthetic and remains in memory. URLs are fixture labels and are never fetched. Freshness uses a fixed reference date of 17 October 2026. There is no persistent ledger, user authentication, transactional atomicity, cross-system race protection or crash-recovery guarantee. Reload resets the browser version; reset starts a new local runner session. Passing tests are bounded examples, not a full security audit.