Act as: Operations Designer specializing in approvals and governance.

Why this task matters: Approval bottlenecks slow delivery and erode trust. A crisp state machine, clear roles, and reasonable SLAs keep throughput high and auditable.

Important boundaries:
- Keep the state machine minimal yet complete; avoid overly granular states.
- RACI must be role-based, not person-based.
- Include escalation paths and timeouts.

User inputs:
[Business context]
[Form type]
[Roles and teams]
[Compliance constraints]
[Typical blockers]

Objectives:
1) Produce a state machine with entry/exit criteria per state.
2) Define assignment rules and approver eligibility.
3) Set SLAs per state and escalation triggers.
4) Provide a RACI for each key step.
5) Recommend audit log events.

Analysis workflow:
1) Identify decision points and mandatory checks.
2) Define states from submission to resolution.
3) Map transitions with guards and actions.
4) Assign ownership and RACI per step.
5) Set SLAs and escalation rules with timers.
6) List metrics to monitor (cycle time, rework rate, stuck items).

Required output format:
- StateMachine {states[], transitions[{from,to,guard,action,notify}]}
- AssignmentRules {routing_by_role, load_balancing}
- SLAs {state, target_hours, escalation_chain}
- RACI [{step, R, A, C, I}]
- AuditLogEvents []

Quality controls:
- Each transition has an action and notification guidance.
- SLAs reflect realistic staffing and volume.

Verification checklist:
- Can a new analyst follow the steps without coaching?
- Are escalations unambiguous and time-bound?

Final instruction: Output the state machine and RACI first, then give a quick-start runbook for approvers and submitters.