Labour Temple · Internal Documentation

Labour Temple operations docs

How the site runs, what to do when it doesn't, and everything we agreed was delivered. Start with the Site Operating Model for the zoom-out, then the four tracks below.

Start with the operating model →
System Status Checking…
Membership Checkout
Loading…
Room Bookings
Loading…
01 — Operate

Run the four purchase tracks

Each track has its own page: architecture at the top, incident playbooks collapsed beneath.

Track 1Membership CheckoutSelf-serve signup for six plans. Stripe + OfficeRnD + welcome email.Track 2Meeting Room BookingsSeven rooms, single- or multi-day. Double-gated availability + auto-refund.Track 3One-Off PurchasesDay passes. Stripe + OfficeRnD kiosk-compatible pass + receipt.Track 4Inquiries & Lead CaptureEvery form submission that isn't a purchase. Two Zaps, five downstream surfaces.

Cross-track

The rituals and references that span every track.

Cross-trackPlaybooks IndexEvery incident scenario across Tracks 1–4 on one page.Cross-trackData Sync & ReconciliationWhere writes fail silently — monthly reconciliation ritual.Cross-trackTesting & MonitoringWhat was tested, what's watched, and what alerts reach you.
02 — Reference

Look up how the site is put together

The zoom-out, the admin reference tables, the live punch list, and the forward-looking backlog.

ReferenceSite Operating ModelEntry points, CMS collections, integrations, customer lifecycle.Admin ReferenceOfferings ComparisonEvery plan and space, side-by-side. CMS/Stripe/Worker audit.ReferenceWebsite Punch ListLive Asana board — content, design, configuration backlog.ReferenceRoadmapKnown gaps, deferred scope, not-yet-documented processes.
03 — Handoff

What was delivered and how we support it

Signed off at the handoff meeting. Response targets and access requirements for the warranty window.

HandoffAcceptance ChecklistSigned at the handoff meeting — delivered, warranty, new scope.HandoffSupport SLASeverity, response targets, access requirements.