Terminal-2
Ticket-trading intelligence + primary-market ticketing platform. FastAPI on Render + Supabase Postgres + edge functions + cron-driven ingest from TEvo, SeatGeek, TickPick, Vivid, SeatData, TicketsData, GoTickets, AXS, Broadway.com, ESPN, NWS. Jointly maintained by a small set of specialized bot lanes coordinating through public.bot_chat.
Doc version: v1.4.0 · baseline 2026-05-28 (A1); v1.1.0 2026-06-09 (C1) — Start here adds the code knowledge-graph onboarding pointer (→ PROJECT_BIBLE.md §8); v1.2.0 2026-06-09 (C1) — pointer now links the committed, viewable chart (.understand-anything/knowledge-graph-chart.html); v1.3.0 2026-06-10 (A1) — Architecture + Repo layout + Build/run refreshed against the tree: full nine-client list, broadway_extension/ + trip_planner/ added, dead .env.example step replaced; v1.4.0 2026-06-10 (A1) — bible sweep folded into the entry point: Start here surfaces the AQ-mapper #1 fact + lane status, Conventions gains cross-source-ID / lane-goals / edge-fn-auth pointers. The section-level version + bot-ref convention is defined below under Doc-writing rules.
Start here (reading order) (v1.3 · A1 · 2026-06-10)
A cold-started bot should read these four, in order. The first is loaded for you automatically every session; the rest you read once at session start.
CLAUDE.md — (auto-loaded every session) immutable security + operator lockdown rules. The safety baseline; it directs you to read the bible next.PROJECT_BIBLE.md — the per-session playbook: hard rules, SQL macros, §3 column-name landmines, workflow recipes, 11-item self-check. Read this first of the things you choose to open — and read its §0 before any cross-source SQL: source event IDs NEVER line up; everything resolves through the aq_event_map hub. It's the #1 fact cold sessions miss.BOT_HIERARCHY.md — who you are, who can push where, per-lane write scope, Render service ownership. At a glance: A1 · B1 · C1 · D0 are ACTIVE (D0 is the priority lane); D1–D4 and E1 are PAUSED until D0 ships.D0_BIBLE.md — cross-source ID architecture + the full cold-start manual for building the D0 terminal frontend (PART 1).
Then check KANBAN.md for what's actionable right now (don't claim a row marked [IN PROGRESS by <lane>]).
New to the code? There's an interactive code knowledge graph to orient fast (architectural layers, file/function relationships, guided tour). To view it, open .understand-anything/knowledge-graph-chart.html in a browser (no toolchain). Regenerate with /understand / explore via /understand-dashboard — full recipe in PROJECT_BIBLE.md §8 ("I want to understand the codebase fast").
Canonical docs — CLOSED registry
This table is the complete, closed set of canonical docs. To add a fact, edit the doc that owns it. Never create a new root doc. Never state a fact in two places — link to its owner instead. Sprawl regrew once before because nothing gated new-doc creation; now a CI gate enforces this table (see Doc-writing rules below).
| Doc | Owns (single source of truth) |
|---|
README.md | Entry point · reading order · this registry · doc-writing rules |
CLAUDE.md | Immutable security + operator lockdown rules · doc-discipline rule (auto-loaded every session) |
PROJECT_BIBLE.md | Per-session playbook: rule summary · SQL macros · §3 column landmines · workflow recipes · self-check |
D0_BIBLE.md | Cross-source ID architecture (§3) · full D0 terminal build manual (PART 1) |
RESOURCES_BIBLE.md | Inventory of tables / views / functions / crons / edge functions · event taxonomy & RULES |
BOT_HIERARCHY.md | Bot roster · push authority · Render service scope · per-bot lane scope |
MIGRATION_CONVENTIONS.md | Migration filename + header rules · level/lane taxonomy · landmark-migration log (§14) |
CRON_HIERARCHY.md | Cron scheduling policy + job ownership |
SYNC_PROTOCOL.md | Repo ↔ deploy ↔ DB sync mechanics |
CHANGELOG.md | Auto-generated release notes (release-please) — DO NOT hand-edit |
KANBAN.md | Open work · drift watchlist · known data-architecture gaps (append-only) |
