# SEVN Table (Saltbush & Lime)

> SEVN Table is a SEVNworks product concept that turns an event enquiry into a costed menu, dietary review, versioned proposal and run sheet. It is shown for Saltbush & Lime, a FICTIONAL modern Thai-Australian kitchen, bar and catering business in St Clair, NSW. Every business, client, event, dish, price and dietary tag is fictional sample data. Money is integer cents AUD; totals include 10% GST. Servings and costing come from a deterministic engine, never from an AI model. Dietary tags are marked verified or unverified; allergies and unverified tags stay "awaiting review" until a person decides. Human approval rule: agents can read and calculate, but any change is a proposal that a person approves in the app. Deposits, emails and reservation holds are simulated.

## Site and app

- [Saltbush & Lime concept website](./): the public site (menu, reservations, functions and event brief, venue, about, visit). Fictional business.
- [Sample menu](menu/): 18 dishes with dietary tags and their verification status.
- [Functions & catering](functions/): packages, spaces and capacities, and the guided event brief (free text can be extracted into a brief).
- [SEVN Table workspace](app/): the staff app. Event inbox → brief → menu → costing → dietary review → proposal versions → run sheet → simulated confirmation.
- [Agents screen](app/#/agents): how to connect, the in-page tools (WebMCP and `window.sevnAgent`) and recent agent activity in this browser.

## MCP server

- Endpoint: `/mcp/table` (Streamable HTTP, stateless JSON-RPC over POST). Claude Code: `claude mcp add --transport http sevn-table https://<host>/mcp/table`.
- Read tools: `get_menu` (catalogue IDs, cents, tags with verified/unverified status), `list_events`, `get_event`, `check_capacity`, `calculate_proposal` (servings, costing in cents, budget fit, simulated deposit), `review_dietary` (unverified stays "awaiting review"), `draft_run_sheet`, `extract_event_brief` (free text → brief fields via the same OpenAI extraction as the functions page; the text is not stored).
- Proposal tools (never change anything; they return an `approvalUrl`): `propose_event_brief`, `propose_menu` (catalogue IDs only), `propose_proposal_approval`.
- Approval: a person opens the `approvalUrl` (`app/#/agent-proposal/…`), sees the proposed values against the current ones, and chooses Approve & apply or Discard. Applied changes are recalculated, versioned and logged "via agent".
- Typical order: `list_events` → `get_event` → `check_capacity` → `get_menu` → `calculate_proposal` → `review_dietary` → `propose_menu` → `propose_proposal_approval` → `draft_run_sheet`. New free-text enquiry: `extract_event_brief` → `propose_event_brief`.
- Read tools see the sample baseline; a visitor's own browser workspace may have moved on. In the app, the in-page tools act on that browser's live workspace, and every change asks the person to Allow or Deny first.

## Case study

- [SEVN Table case study](../sevnworks/products/sevn-table/): what the product does and how it was built.
- [Suite MCP directory](../.well-known/mcp.json): all six SEVN MCP servers.