WF-201Ready
120-person launch dinner
- Owner
- Event desk
- Stage
- Proposal review
- Next
- Prepare acknowledgement draft
Self-initiated demonstration 04
A workflow that stops before it acts without approval.
Four fictional requests enter one coded browser run. Validation, routing, exceptions, draft preparation, and the approval stop remain visible. Nothing is sent, booked, or connected to an outside account.
The demonstration brief
Keep the route clear and the outside action deliberate.
A dependable workflow needs a preserved source record, explicit rules, visible exceptions, an audit trail, and a named approval point. The automation is not finished when data moves. It is finished when the buyer can understand and control what happens next.
- One fixed fictional fixture set
- Two eligible and two held records
- One browser-only approval control
- Zero external actions
Source4
fixed requests
Ready2
internal routes
Held2
visible exceptions
External0
sends or bookings
Showing route result.
Internal route
Eligible work moves. Exceptions do not vanish.
The result prepares internal ownership and next actions only. It does not write to a CRM or contact anyone.
WF-202Held
Checkout fails on mobile
Contact path is missing.
WF-203Ready
CRM cleanup and handoff
- Owner
- Operations desk
- Stage
- Scope review
- Next
- Create review task
WF-204Held
Follow up after conference
Permission basis is not recorded.
Draft record / WF-201
Prepared for review, not delivery.
Waiting for human review
The draft cannot leave this page without an outside system and separate approval.
Exception queue
Two rows need a decision.
- WF-202Contact path is missing.
Request a valid contact path
- WF-204Permission basis is not recorded.
Record permission decision
All names, addresses, requests, times, stages, and records are fictional fixtures. The approval control changes browser state only. No message, task, CRM record, appointment, or file is created outside this page.
Architecture
Every transition has an owner and a reason.
Receive
A fixed fictional request enters with its source and permission state.
Validate
Required contact, declared permission, and duplicate rules run before routing.
Route
Eligible rows receive a stage, owner, next action, and draft record.
Review
Held rows stay visible. A human may approve a browser-only draft.
Handoff
A paid build would return the workflow map, rules, logs, tests, and operating note.
Production boundary
The buyer owns the accounts, rules, and approval.
A paid implementation starts from a small approved fixture set. External tools, credentials, production records, live messages, and schedules remain outside the work until the owner and acceptance test are written down.
Buyer supplies
The approved source, required fields, permission basis, qualification rules, destinations, account owners, and approver.
Katsa maps
The intake schema, validation rules, stages, failure states, approval points, retry policy, and test set.
Buyer approves
A small fixture set, the route table, every external action, account access, and the exact production done condition.
Katsa returns
The configured workflow, source and destination map, test evidence, exception record, access notes, and operating guide.
Not shown here
A client system, CRM connection, email send, calendar booking, live API, background job, production result, or time-saving claim.
Claim boundary