Humphrey — Wiki Entry Point
Purpose: Live intelligence dashboard and operational command centre for Pride of Our Footscray. Combines 8 years of venue data (POS, ticketing, accounting, rostering) with AI insights, alerts, and automation to support daily decisions by the venue’s operators.
Loaded by: _humphrey-project-setup/INSTRUCTIONS.md (Cowork) and pride-intelligence/CLAUDE.md (Claude Code).
Always load at session start
- Humphrey Intelligence App — The product itself: what it is, who uses it, what it’s for
- Tech Stack — Next.js 16, React 19, Supabase, Prisma 7, Railway, Tailwind v4
- Humphrey Design System — Three-layer design: shadcn/ui + tokens + Motion; “theatrical dark”
- Data Integration Architecture — How Square, TryBooking, Xero, Deputy data flows into Humphrey
- Cowork-Claude Code Workflow — Product development methodology Shae uses for PRDs
Load when work touches…
Data sources / integrations
- Square POS — Largest data source (orders, payments, catalog)
- TryBooking — Ticketing + 8-year customer data asset
- Xero — Accounting truth once corrections complete
- Deputy — Rostering, time tracking, payroll export
- Amaka — Square → Xero middleware; data quality dependency
- PinTuna — Loyalty; platform under review
- Settlement Sync — Daily invoice automation
- Daily Sales Sync — Square-to-Xero daily flow
Integration research
- Melbourne Venue Tech Stack Research — Broader tool landscape evaluation
- Deputy Xero Integration Research — Rostering integration specifics
- Automation Opportunities — Workflow automation roadmap
- Tech Stack Optimisation — Recommended additions (inventory, loyalty, email, BI)
Design / UI
- Humphrey UI Overhaul Research — Tool landscape and premium dashboard patterns
- Brand Governance and AI Policy — External creative human-led; internal AI-assisted
Operational data Humphrey surfaces
- Saturday Revenue Collapse — The #1 problem Humphrey helps diagnose
- Saturday Trading Pattern — Data-driven analysis
- Programming Model — Event types Humphrey categorises
- Trading Pattern — Weekday/weekend constraints informing dashboard views
- Financial Snapshot — Current state of the metrics Humphrey must reflect
Regulatory / security
- Shared Account Security — 2FA-to-phone bottleneck; informs Humphrey auth decisions
- Brand Governance and AI Policy — What Humphrey is and isn’t allowed to do with content
Active decisions
- Xero Corrections Approved — Xero data is being corrected; Humphrey should mark Xero-sourced metrics as “correcting” until complete
Source documents
- Financial Snapshot — Revenue, costs, survival threshold as at 25 Mar 2026
- Forensic Audit Run3 — FY23–FY25 bookkeeping audit and corrections
- Loan Accounts Diagnostic — Loan structure and interest expense accounting
- Square Xero Settlement Analysis — Settlement flows and reconciliation issues
- Saturday Analysis — Saturday trading pattern dataset
- Social Media Analytics Data — Instagram and Facebook performance metrics
- TryBooking Contacts Audit — 8-year customer data quality
- TryBooking Revenue 2023 — Category revenue data
- Technology - Intelligence Dashboard Planning — Original dashboard spec and data requirements
- Technology - Systems Inventory — Complete systems listing and integration gaps
- Technology - Automation and Integration Opportunities — Integration roadmap
Analysis relevant to this project
(None yet filed specifically for Humphrey — most analysis lives in pride-intelligence/_specs/ and pride-intelligence/_qa/.)
Cross-project context
- website — Shared tech stack (Next.js 16, Tailwind v4). Shared design tokens possible.
- finance — Humphrey surfaces financial metrics; Finance project corrects the underlying data. Coordinate on Xero data-quality assumptions.
- ops — Humphrey’s operational alerts (incident flags, fatigue warnings, banned persons lookups) only work if Ops has the underlying processes documented.
Key operational facts Humphrey must respect
- Xero data untrusted until Xero Corrections Approved completes — label metrics as “approximate”
- 2FA on shared accounts funnels to CEO phone only — Humphrey cannot rely on SMS MFA as sole auth
- Banned persons list not distributed to security — feature gap Humphrey could fill
- CEO email inbox has 25,000+ unread — any “email-triage” feature must integrate with Mat’s existing 3-phase plan (see Email Management Strategy)
Recent updates
- 2026-04-24 — Sub-index created (WIKI-META-1)