Expand description
Workflow contracts for tasks, events, reviews, and recommended actions. Workflow events and outcomes for reviewable resort operations.
§Operator framing
Use this page to understand how a source fact turns into a staff-visible task, review reason, draft message, or recommended next action. It matters to operators because workflow values preserve why something is being suggested, what evidence supports it, and which human review gate still controls the live care, labor, payment, or customer-communication step.
The next step is to follow the type that matches the queue you are explaining: events identify why work started, task/message modules describe staff-facing drafts, review values explain why automation stopped, and outcomes record the evidence trail. The Rust API details below are the generated implementation surface for implementers; this framing is the business reading guide.
Workflows connect provider/read-model facts to staff-visible tasks, customer-message drafts, policy context, and recommended next actions. They preserve evidence and review reasons so AI agents can reduce manual triage while keeping live care, labor, payment, and customer communications inside explicit approval boundaries.
Modules§
- external
- External workflow-provider vocabulary retained before promotion into domain tasks or messages.
- message
- Provider message fields used before normalization into customer-message workflows.
- status_
update - Provider status-update fields used to reconcile external task or message progress.
- task
- Provider task fields used to create staff work without losing source evidence.
Structs§
- Event
- Workflow event that records what changed, who/what it concerns, and what evidence/risk came with it.
- EventId
- Stable identifier for a workflow event emitted by an agent, adapter, or staff-facing process.
- Policy
Context - Policy context attached to a workflow so reviewers can see allowed actions and required gates.
- Result
- Workflow result carrying status, summary, recommended action, and verification notes for staff review.
- Review
Reason - Review explanation recorded when automation must stop at a manager, medical, or customer-message gate.
- Risk
Flag - Risk marker surfaced when a workflow may affect pet safety, labor cost, payment, or customer trust.
- Summary
- Verification
Note - Evidence note proving what source fact, review, or staff action verified a workflow outcome.
Enums§
- Allowed
Action - Action an automation policy permits for a workflow outcome.
- Event
Type - Event category emitted by triage, policy, review, external sync, or source ingestion.
- Recommended
Action - Recommended next action for staff, managers, or automation after evaluating a workflow.
- Review
Reason Error - Risk
Flag Error - Status
- Normalized lifecycle states used to reconcile source-system data with domain workflows.
- Subject
- Subject of a workflow event or recommendation.
- Summary
Error - Verification
Note Error