Synthetic demonstrationNo customer data · no assurance claim · implementation status shown at every stage
Interactive synthetic walkthrough
One tenant. Every role. The complete evidence lifecycle.
This is a transparent product tour, not a production-readiness claim. Each chapter shows the intended user action and its current implementation state.
Record the corridor, parties, residency, retention and approved data classes before any customer evidence is accepted.
Evidence produced
Signed order · DPA · role/data map
Production truth
Approved evaluations now produce append-only orders, exact invoices and payment evidence; counsel approval, DPA acceptance and the signed external instrument remain gates.
Recorded walkthrough · 50 seconds
Send one URL. Show the complete lifecycle.
The recording uses the same synthetic fourteen-stage tour above. On-screen chapters and the caption track identify the actor, action, evidence output and current production implementation state.
A silent, captioned screen recording that progresses from prospect approval and tenant onboarding through Verify, Control, Close, independent review, service review and offboarding using synthetic data only.
Read the complete 14-stage transcript
01
Approve the POC boundary
Commercial + privacy owner — Record the corridor, parties, residency, retention and approved data classes before any customer evidence is accepted.
Partially production-backed: Approved evaluations now produce append-only orders, exact invoices and payment evidence; counsel approval, DPA acceptance and the signed external instrument remain gates.
02
Provision the tenant
Platform administrator — Create the organisation and first programme through a reviewed, idempotent request, then issue the named owner invitation.
Partially production-backed: Tenant requests retain their order authority, production requires a paid invoice, and activation fulfils the order; suspension and rollback UX remain.
03
Enrol the owner
Organisation owner — Accept the personal invitation, complete MFA and bind the fixed identity subject to the tenant membership.
Partially production-backed: Named invitation and membership activation are live; terms acceptance and recovery operations remain.
04
Separate the duties
Organisation owner — Invite preparer, reviewer, field, device, counterparty and external-review roles with programme and site scope.
Production-backed slice: Owner-managed role, scope and lifecycle controls are database-backed with negative tenant tests.
05
Design the programme
Programme administrator — Version the period, sites, counterparties, materials, units, tolerances, evidence criteria and close checklist.
Partially production-backed: The first configuration snapshot is live; richer criteria, drafts and multi-period planning remain.
06
Onboard a source
Data preparer + source owner — Quarantine and scan the exact upload, promote only the clean version, stage rows and approve mappings with a different reviewer.
Partially production-backed: Upload, promotion, staging, maker-checker mapping and immutable canonical row lineage are live; the named two-role object canary remains.
07
Commission the corridor
Device technician + site operator — Register identities, instruments, vehicles, tags and seals; issue credentials and test offline, replay and fallback paths.
Partially production-backed: The tenant-scoped registry, Ed25519 device credential, supplier-approved read-only profile, health, replay sequence and revocation controls are production-backed; a real installer rehearsal and signed update seam remain.
08
Capture both ends
Site operator + counterparty — Record attributed origin evidence and let the receiver commit independently before either side can see the comparison.
Partially production-backed: ProofLink/media, encrypted reconnect, blind ProofPair and signed registered-instrument TP-E2 ingestion are production-backed; official WhatsApp and a named real-device rehearsal remain.
09
Run deterministic controls
Data preparer — Freeze an input snapshot and run mass, duplicate, cut-off, payment and source-completeness checks with row citations.
Production-backed slice: Rule proposal, independent approval, immutable snapshot execution, encrypted dispatch, bounded retry, quarantine and authorised redispatch retain exact hashes and row citations; the named two-role rehearsal remains an acceptance gate.
10
Resolve an exception
Preparer + reviewer + counterparty — Request evidence, append a response and proposal, then require an independent approval, rejection or disclosed limitation.
Partially production-backed: Programme-scoped assignment, evidence request/response, independent disposition review, escalation and disclosure are production-backed; notification delivery and named-role acceptance remain.
11
Lock the period
Preparer then data reviewer — Complete the checklist, reproduce totals, attest separately and lock a snapshot that can only be superseded by a reasoned reopen.
Partially production-backed: Checklist history, independent attestations, deterministic immutable Close and KMS-signed PDF/XLSX/JSON packs are production-backed; the named two-actor rehearsal remains.
12
Review the released evidence
External reviewer — Select authorised samples, ask structured questions and download only the released pack without editing customer records.
Partially production-backed: Named assignment, explicit artifact release, bounded sample frame, request/response, access logging, revocation and expiry are production-backed; named reviewer acceptance remains.
13
Review the service
Customer owner + MassTrail — Review source and device health, incidents, SLOs, usage and corrective actions against the agreed corridor scope.
Synthetic demonstration only: Operational telemetry, support portal, SLO reporting and cost attribution remain.
14
Offboard with evidence
Owner + privacy + security — Revoke people and devices, export authorised records, apply holds and retention, then evidence deletion or restriction.
Synthetic demonstration only: The legal schedule exists; executable export, hold, deletion and certificate workflows remain.
Ready for a named rehearsal?
Move from the synthetic story to an attributable session.
Any organisation can apply. A platform administrator qualifies and schedules the request before named MFA-backed access is approved.