Infinity Ops — Field Guidelives at /guide · updates with every releaseInfinity Ops — Field Guidelives at /guide · updates with every releaseEverything lives behind one address: /hub. Bookmark it on your phone. It routes you to the Crew Board, Events Dashboard, Kitchen & Warehouse boards, the Culinary Schedule — and this guide.
Every run moves through these. A killed run is cancelled but never erased — if you see one struck through, it's history, not a mistake. The same words and colors appear on your phone, the wall TVs, and the office dashboard: when you tap Arrived, the warehouse TV flips at the same moment.
Don't call around — flag it. On your run (crew) or the events dashboard (events/culinary): pick FOOD / ALCOHOL / RENTAL / other, add a note and your name. The right people get texted, it lands on the wall boards, and dispatch can send a run with the item. You'll see it resolved in the queue.
Every page has a "Something wrong?" button. Tap it, say what you expected vs. what happened, send. It goes straight to the help desk with a snapshot of the page — and the Brain reviews every report nightly. If you left your number, you may get a status text when it's fixed. Please use it — a 10-second report beats a rumor that "the app is broken."
Hub → Report an Issue: pick the venue or building, say what's wrong, done. It goes to Kevin for approval, then onto the fix list with an estimated date. No sirens, no texts — it travels silently and you get email updates. Check the "already in play" list first so we don't double-file.
Every single page — Dispatch, Planning, Property Brain, Sales Brain, Org Chart, all of it — now carries the SAME dropdown in its header to every other door in the company. You don't need to remember which app hosts what anymore; open the dropdown from wherever you already are. Still: the Hub (/hub, bookmark it) is the front door and the dropdown's own top link · Field Guide (this page) · Report an Issue for anything broken at a venue · the 🐞 "Something wrong?" button on any page when the APP itself misbehaves (that one goes to the fix-it queue, not maintenance).
/me is your personal base — your own out-of-office requests (submit and see your history right there, no more asking someone else to enter it for you), plus whatever else your tier unlocks. /dash is your own modules-and-kudos dashboard. Both are open to every signed-in person; what you see on each scales to your access level automatically.
Today's runs, live: truck, crew, depart-by time, status chips. Standing/recurring runs sit in their own labeled section below the event runs. If a row pulses, it just changed.
The depart text carries your link, or go Hub → Crew Board → My Day. Your stacked assignments for the day: tap Departed → Arrived → Done as you go, see tasks, flag a missing item right from the run.
From the Hub tap Warehouse Schedule (or bookmark /warehouse/current) — no login, it opens straight to Whole Week: the full crew and every run going out, same as the culinary schedule. Want just your own shifts and runs? Tap My Day and enter the last 4 of your cell (same last-4 as everywhere else; if two people share the last 4, just tap your name).
Weekly pack-out sheets drive what goes on the truck. Building the schedule itself? The written how-to lives with the ops docs (ask a manager for Trung's schedule guide).
Go to /inventory-count on your phone, log in the same name-and-PIN way as everywhere else, tap your location. Enter a count for each item, or hit Can't find it if it's genuinely not there — never guess a zero. Every value saves the moment you stop typing; you can lock your phone and pick back up later with everything still there.
Honest state right now: the "Par" line reads live from the actual Master Inventory Sheet (or the Warehouse Sheet, for the monthly Warehouse count) — that connection went live 2026-08-10. Counts you enter are NOT reaching the sheet yet, though: Dispatch can read the sheet but write access hasn't been granted (confirmed Viewer-only as of this writing). Your counts are saved safely in Dispatch either way and will start mirroring to the sheet automatically the moment write access is granted, no re-entry needed. All 8 locations are built: Bell Tower, Bridge Building, Cherokee Dock, Saddle Woods, Saint Elle, The Cordelle, Estelle, Catering Kitchen, plus the monthly Warehouse count.
/schedule/current is always the current approved week; /schedule/upcoming is always the next posted week — send that one while you build next week and it never changes, even through edits and re-posts. Bookmark once and stop chasing new links.
Today's food runs with hot-food and late-night flags, plus standing runs in their own section. Same status chips as everywhere else.
Flag it from the events dashboard (events PIN + your name — every flag has a name on it). It texts the right people and enters the central Missing queue where dispatch can send a run.
Three tabs: Today · This Week · Missing. Each event card shows crew size, depart times, and a clipboard indicator — 📋✓ means the day-of rollup has been opened by the team; 📋⌛ means not yet.
Report (anyone, with their name) → Claim (a dispatcher/manager takes it) → Resolve or Send-Run (a real run is created to deliver the item) → history. Reporting works with the events PIN; claiming/resolving/sending needs your own PIN — those actions carry your name.
Your book, live: every upcoming event you're on, a readiness ring (8 checks: team, final count, times, floorplan, packlist, BEO, timeline), and real links to every doc. If a number looks wrong there, it's wrong on the HubSpot deal — fix the source and the page follows. When something breaks, use its 🐞 button — don't text it in.
/inventory-assignments — a read-only view of all 8 built count locations (the 7 venues + Catering Kitchen, plus Maggie's monthly Warehouse count), who's assigned, and this week's/month's progress (counted / can't-find / total, last activity). Built for Tae, who runs weekly inventory across the venues — but Tae's own account doesn't exist in this system yet (a real, unresolved gap, not an oversight), so for now this page is open to any admin/kitchen-manager-tier login, same gate as the other manager-only screens. Maggie's identity has the same gap; her warehouse row is seeded the same NULL-staff_id way as Tae's.
The Infinity Brain reads Dispatch through a read-only door (it can never write). Morning emails, stat cards, and briefings are built from the same data you see here — if the boards are right, the Brain is right.
Run npm run smoke — health, login, today's board in one pass against prod. (The bare node scripts/smoke.js command by itself now refuses to run at all — it fails loudly and tells you to pass --target=prod explicitly, on purpose, so a smoke test can never silently point at the wrong environment. npm run smoke already does that for you.) Then click through what changed. Small ships, verified live.
This page ships in the same codebase as the features it describes. No staff-facing change merges without updating its section here plus one line in WHAT'S NEW. Builders: that's part of the definition of done. Managers: when you approve a feature, ask "did the guide move too?" If you're reading something that doesn't match the app, that's a bug — hit the 🐞 button.
WHAT'S NEW rotates monthly (standing convention, since 2026-08-09): the top box always shows the CURRENT month only (plus a few days' grace into a new one) — it answers "what changed lately," never "what changed once." On first touch of a new month, whatever's on top moves into the "Earlier updates" archive below it, dated, collapsed, never deleted.
Guide born July 3, 2026 · written by Fable 5 as a parting gift · maintained by every build after