Skip to content

docs(llm-context): explore + design for a unified chat-history fed to the LLM (Tasks 2/3)

Administrator requested to merge beta into main

Exploration-only deliverable (no code changes). Documents how MESSAGE / RECENT MESSAGES / ON-SCREEN STATE could merge into ONE bot<->user history where the LLM sees everything the user sees — rendered lists/cards WITH real button payloads (labeled system-sent), messages the bridge deletes (kept for the LLM but tagged hidden), and confirmation acks. Plus a flows-explainer variable (buttons pick things; phone needed for payment; changing pax re-searches; offers expire after 15 min) synced to the real code values.

  • DESIGN.md — the proposal, the exact context to pass, and open questions.
  • sample-1-flight-booking.json — full flight journey as the unified history.
  • sample-2-command-qa-refine-expiry.json — command / mid-list QA / pax re-search / expiry.
  • flows-explainer.md — the explainer text + where it plugs in.

Merge request reports