Maya Architecture Docs Overview · Architecture · Capabilities · Request path

Maya — rule of thumb

Straight-forward, so context does not wander. Maya only does one job: help the traveler book a flight, a hotel, or both.

Flight · hotel · both ≤3 options each time Maya → MCP → OMS Positive path to book first
How to verify Maya does this (Asto). Open the CAP checklist — each of your 7 bullets maps to CAP-01…CAP-07. Each CAP has Must / Must not / verify probes. ChatGPT can review that page against your bullet list. Glossary: CAP = Capability · SDD = Software Design Document · ADR = Architecture Decision Record. (AI + training honour the same records.)
CAP catalogue (start here)Asto bullets → CAP-01…07 SDD hubFreeze after CAP OK ADR hubMCP→OMS decisions ArchitectureMaya → MCP → OMS

10 rules (memorize these)

#Rule
1Job = book flight, hotel, or both. Nothing else is the product.
2Intent first → fill slots → show summary → wait for Search.
3No Search click = user is editing the summary. Update slots. Do not search yet.
4Suspect intent change (e.g. hotel path then “cari pesawat ke Jogja”) = re-confirm intent, then follow the new intent. Do not dig in on the old one.
5After Search: show ≤3 options for flights and for hotels. User can ask for another batch if not happy.
6No Book click = refine from chat → search again. Never invent options.
7After Book: check all intents met → confirmation page (flow design).
8Geo is exact: “Kuta Bali” ≠ “Kuta Lombok”. Prefer the place the user named.
9Inventory is live OMS via MCP. MCP stores behaviour/session — not fares or rooms.
10MVP focus: positive path until booking works. Weird edge cases later. Do not confuse “AI dumb” with “flow broken”.

The loop (one picture)

flowchart TD
  A[1. Intent
flight / hotel / both] --> B[2. Summary]
  B --> C{Search?}
  C -->|no — edit chat| B
  C -->|intent changed| D[Re-confirm]
  D --> A
  C -->|yes| E[3. ≤3 options
OMS via MCP]
  E --> F{Book?}
  F -->|no — more options| E
  F -->|yes| G[4. Intents met?]
  G --> H[5. Confirmation]

Technical path (short)

Traveler → maya-api → Anamaya MCP → OMS

In session Intent, summary, picks, prefs.
Live from OMS Flights, hotels, photos, prices, bookings.
NRCP How Maya speaks / reads informal ID — not a hotel database.
CONFIRM Book / pay / cancel need explicit Ya.
Full loop table7 steps as SDD candidate MVP rules3 options · geo · intent flex · photos ArchitectureMCP vs OMS detail One chat turnSequence diagram