first safe pilot
Weekly menu brief or guest FAQ draft from approved facts.
Keep the first workflow at draft or review-support level before any real-world use.
aequai ~ / industries / handbook 08
$ aequai handbook --priority 08 --full-content
Hospitality / Restaurant AI Adoption Handbook
Menu briefs, guest FAQs, supplier notes, shift briefings, and staff SOP drafts with owner review.
priority 08readiness mapfictional/synthetic samples onlyhuman approval required
// boundary: This handbook is local review copy for readiness, training, workflow design, and evidence mapping. It is not sector authority, professional advice, public approval, regulated conclusion, production authority, autonomous operation, token/chain/network action, carbon-asset action, or customer proof.
$ aequai quick-map --pilot --path --no-go
Safe first step.
service path
AI Literacy Training -> Department AI Pilot Design
Use diagnostics, training, pilot design, governance, or simulation according to the workflow risk.
training path
Owner/manager, kitchen/ops, front desk/support, and staff training paths.
Training is personalized to role, workflow, tool stack, risk profile, data boundary, and approval responsibility.
Source: hospitality-restaurant-ai-adoption-handbook-v0.1.md. Source title: Hospitality / Restaurant AI Adoption Handbook v0.1.
$ aequai handbook-source --sections all
Full handbook content.
The sections below expose the actual handbook material: business context, workflows, first safe workflows, map, boundaries, simulation example, checklist, fictional/synthetic sample teaser, recommended AequAI path, 30/60/90 roadmap, and public-safe no-go wording.
[01]Business Contextsource-backed handbook section+ open- close
Restaurants, cafes, hotels, guesthouses, catering businesses, and tourism teams handle menus, guest questions, supplier notes, staff SOPs, schedules, and service updates. AI can draft routine materials when owners keep review.
Every training path is personalized to the person, team, role, workflow, tool stack, risk profile, business context, workflow maturity, data boundaries, and approval responsibilities.
[02]Typical Workflowssource-backed handbook section+ open- close
Menus, supplier briefs, guest FAQs, staff SOPs, shift briefings, local guide drafts, catering prep notes, and customer-update drafts.
[03]First 5 Safe Workflowssource-backed handbook section+ open- close
- +Weekly menu brief.
- +Staff SOP draft.
- +Guest FAQ draft.
- +Supplier note checklist.
- +Shift briefing draft.
[04]Function Mapsource-backed handbook section+ open- close
| Function | Opportunity | Training Need | Gate |
|---|---|---|---|
| Owner/manager | Weekly operations brief | Source discipline | Owner review |
| Kitchen/ops | Menu and supplier brief | Approved facts and review | Manager review |
| Front desk/support | Guest FAQ draft | Data boundary | Manager review before use |
| Staff training | SOP drafts | Workflow practice | Owner review |
[05]Boundariessource-backed handbook section+ open- close
Do not use AI for health/allergen statements without review, refund decisions, booking commitments, private guest data, payment records, or auto-publishing.
[06]Simulation Examplesource-backed handbook section+ open- close
Synthetic scenario: a restaurant drafts a weekly menu and supplier checklist from approved notes. Owner reviews before staff or public use.
[07]Diagnostic Checklistsource-backed handbook section+ open- close
- +Which menu/supplier facts are approved?
- +Which guest questions repeat?
- +Which private guest data is excluded?
- +Who reviews public text?
- +Which staff routines need SOPs?
[08]Fictional/Synthetic Sample Report Teasersource-backed handbook section+ open- close
Fictional/synthetic sample: "Restaurant Weekly Menu and SOP Workflow." Shows owner-reviewed draft support and staff practice plan. It is not customer proof.
[09]Recommended AequAI Pathsource-backed handbook section+ open- close
AI Literacy Training -> Department AI Pilot Design for staff/guest workflow -> AI Governance Starter Kit if multiple staff use AI.
[10]30/60/90-Day Roadmapsource-backed handbook section+ open- close
30 days: menu and FAQ drafts. 60 days: staff SOP practice. 90 days: team playbook.
[11]Public-Safe Wording Notessource-backed handbook section+ open- close
Use approved facts, staff SOP drafts, guest FAQ drafts, and owner review.
$ aequai next --map-business
Use the handbook as a starting map.
Start with one workflow, one review owner, one data boundary, and one evidence log. Expand only after a reviewed pilot shows what to proceed with, shrink, park, or stop.