backbone-events 0.5.1

Events core + the sale/booth/crm/sms/desk overlay — registrations under one authoritative seat counter, the sale seam (order-minted registrations, forward-only paid heal, SO-cancel mirror cascade), booth bookings with the DB exclusivity wall, closed-vocabulary lead rules through a host sink port, the dual-channel (mail/sms) self-arming scheduler, and the exact-match desk verb (Odoo event port, core + overlay)
1
2
3
4
5
6
7
8
9
10
11
12
13

# events Workflows

Declarative specs of the module's multi-step sagas. The hand-authored Rust is the executable
truth; these YAML files document the intended orchestration and are the readable companion to the
golden cases in `docs/business-flows/`.

| Workflow | Saga | Implemented in | Proven by |
|----------|------|----------------|-----------|
| `example.workflow.yaml` | (replace with your saga) | `src/application/service/…` | `tests/…` |

Single-entity status transitions belong in `schema/hooks/*.hook.yaml` as state machines, not here.
Use a workflow only for a **multi-step** saga (e.g. "create A then B atomically", "A → B → C").
Delete `example.workflow.yaml` if this module has no sagas.