Build a small clickable local prototype from these supplied process rules.
Show [states and actions] with source rule IDs and meaningful error/return
paths. Use fictional data. Local controls should actually change the
prototype state, but label approvals, sends and saves as simulations.
No network calls, accounts, tracking, backend or external writes.
Provide actual runnable files and a plain explanation of what works
locally, what is simulated and what a real implementation would require.

---

Map each control to the local state it changes and the supplied rule
that allows it. Keep invalid or unresolved cases explicit. Do not
display a real-service completion receipt where none exists.
Mark any proposed integration as future work, not implemented behaviour.

---

For [case/action], the prototype [wrong state / misleading completion
message]. Rule [ID] says [actual condition], and no external action
exists in this scope. Correct the local transition and simulation label.
Keep the useful layout and other rules unchanged. Repeat that actual
case and do not claim a live service was implemented or a real request saved.
