Writes are enabled
Sourced form fields and reversible transitions execute automatically inside the assigned workflow scope.
Inspectable demonstration
A workflow that writes, pauses, resumes, and proves what happened.
This synthetic, provider-neutral trace demonstrates MODU's execution model without exposing private code, credentials, account data, or live provider responses.
Scenario
Create one zero-cost programme account without losing control at a verification gate.
The workflow uses sourced company data and an opaque vault credential, routes human verification as a bounded gate, resumes the same operation, executes the account action once, and captures confirmation evidence.
Secrets stay opaque
Passwords and one-time codes are consumed in memory and excluded from public traces and durable receipts.
Gates preserve state
The verification lease is bound to the workflow, session, origin, page and operation, then accepted once.
Submission is exact-once
After a durable submit event, recovery may verify or capture completion but cannot emit another submit.
Synthetic trace
Eight durable states from authority to confirmation.
Every step below corresponds to a structured entry in demo-workflow.json.
- 01Authorized
Bind the goal, company identity, allowed origin, duplicate guard, consequences and completion criteria.
authorized - 02Company field written
Fill the sourced business email and record its source without exposing the value in public evidence.
executing - 03Vault credential entered
Consume an opaque credential handle once inside the audited browser action.
executing - 04Verification gate presented
Issue an expiring lease bound to the exact workflow, page, session and operation.
gate_presented - 05Gate satisfied
Verify a one-time signed completion; reject an expired, replayed or mismatched token.
gate_satisfied - 06Same workflow resumed
Revalidate origin, page and action identity before another mutation.
resuming - 07Account action executed once
Bind the requested operation, selected adapter, worker, exit status and observed result.
submitted - 08Confirmation captured
Record the completion marker and receipt, then disable duplicate submission.
completed
What this proves
A reviewable product mechanism—not a screenshot of a chatbot.
The trace makes the control model concrete: writes are permitted within scope, secrets remain separated, external gates do not erase state, and completion is backed by bound evidence rather than an assistant's assertion.
It does not claim a customer deployment, production certification, live provider approval, or independent security assessment.