MARSEN HUMAN-APPROVAL SYNTHETIC DEMO

Status
This is an isolated Node.js demonstration using fictional identifiers and an
in-memory CRM record. It makes no network request and writes to no customer or
production system. It is implementation evidence, not a customer deployment.

Files
- approval-engine.mjs: versioned proposal and synthetic CRM implementation.
- approval-engine.test.mjs: nine automated behavior tests.
- run-demo.mjs: prints representative scenario outcomes as JSON.

Run
node --test approval-engine.test.mjs
node run-demo.mjs

Verified behaviors
- approval executes the exact reviewed version;
- rejection writes nothing;
- an edit supersedes the prior version and needs a new approval;
- an expired proposal cannot execute;
- a changed target record produces a conflict instead of an overwrite;
- replay uses a stable action ID and does not duplicate the write;
- a timeout after a committed write is reconciled before retry.

Limits
The store is in memory and single-process. It does not demonstrate durable
transactions, concurrent reviewers, production authentication, provider
idempotency, distributed locks, notification delivery or a real CRM. A
production implementation must use the destination's supported concurrency and
idempotency controls, durable audit storage, access control and recovery plan.

28 September 2026 extension
Added tests for a different reviewer, an altered returned proposal copy, and an
approval attempted after rejection. All nine checks passed; see
test-results-2026-09-28.txt and test-run-2026-09-28.json for the recorded run.