Concepts & glossary · Stampede Docs

AI-derived field: A computed value attached to a Customer or Venue node — ChurnRisk, LifetimeValue, LoyaltyScore — with a confidence score and a derivation chain naming every source signal that produced it.
Booking: A reservation or walk-in attached to a Customer and a Venue. The Booking node is the central hub for orders, threads, upgrades and reviews that follow a guest visit.
Customer: The root identity node. One record per guest, per organisation. Every interaction across the platform stitches to a single Customer through deterministic identity resolution.
Derivation chain: The explicit list of source signals an AI-derived field reads to produce its value. Surfaced on every AI response so the assistant cites its sources.
Edge: A named relationship between two nodes in the graph — `:BOOKED`, `:VISITED`, `:CONTRIBUTED_TO`, `:TAGGED_WITH`. Edges carry their own properties (visit_count, amount, sent_at).
Estate: All venues owned by a single organisation. Loyalty balances, segments and analytics span the full estate by default; org-scoping enforces tenancy at the query layer.
Foundation: The Guest Profile pillar. Customer, Organization, Venue and the AI-derived fields attached to them. The data lake both product surfaces read from.
Graph AI Engine: The identity spine of the platform. Three nodes — Customer, Organization, Venue — that every other entity references. The bus through which all events flow.
Guest Profile: One unified, identity-resolved record per guest. The single source of truth for what the platform knows about a person. Synonymous with the Foundation pillar.
Identity resolution: The deterministic process of folding signals from phone, email and Wi-Fi MAC onto one Customer node. Rules are explicit; every join is a recorded edge with provenance.
Guest Operations: The team-facing surface. The diary, the inbox, the reviews queue, the floor plan editor. Writes to the Guest Profile.
Organization: The top-level tenant. Every entity is scoped to an Organization; every query carries an org_id filter. Estates of venues hang under one Organization.
Pennies: The canonical unit for monetary fields. Every `pennies`-typed field stores integer pennies; divide by 100 for display.
PayOS: The commerce layer. Orders, POS tickets, line items, menu items, billing and add-ons. Every penny tracked.
Marketing Automation: The platform surface that closes the loop on guest comms. Segments built on the live Guest Profile, AI-drafted email and SMS in the venue’s tone of voice, workflows that fire off live state.
PII: Personally-identifying information. Every PII field on the Customer node is tagged at the schema level so erasure and retention policies are mechanically enforceable.
Schema entity: A named node type in the graph — Customer, Booking, Order, Review. 44 in total across 8 layers. Each entity has its own page at /docs/reference/schema/[entity].
Segment: A saved slice of the customer base, queryable in natural language. Dynamic segments re-evaluate on every read; static segments freeze a snapshot.
Splash: The captive portal a guest sees on connecting to venue Wi-Fi. Branded as the venue, not Stampede. A sign-up surface and a marketing surface.
Tag: Two distinct things share this word in the docs: (1) the schema entity Tag, a human-applied label on a Customer like VIP or Coeliac; (2) the docs taxonomy tags like `#bookings`, `#operations`, `#derived` that organise pages by topic, pillar and scope.
Venue: A physical location operated by an Organization. Every activity node links back to a Venue via `:AT_VENUE`.
Wallet card: A digital loyalty or gift card in Apple Wallet and Google Wallet. The guest-facing surface over the LoyaltyEnrollment or GiftCard node.
Workflow: A directed graph of conditions, delays and sends. Runs on the live profile, not a frozen export. Drives birthday flows, post-visit, win-back, anniversary.