ESD Quest

ESD Quest is the unified status surface for the ESD platform — and the sister of tmc.quest. Two three-letter .quest domains, same posture: the production state is the marketing surface. Today the page renders a live status dashboard pulling deploy version, commit counts, line counts, OS / PHP / DB versions, and activity rollups from TMC and ESDBooking; tomorrow the domain is slated to host esdbooking.us (or its successor) outright, with the status layer rolling underneath.

What the dashboard surfaces

• Per-system header — current version, deploy time, commit + LOC counts, OS / PHP / MariaDB / Apache versions for both TMC and ESDBooking.
• Live activity rollups — users online, active campaigns, total leads in TMC, JN contacts in ESDBooking, refreshed on each page load.
• Status badges — Online / Degraded / Offline at the system level, so the operator and the public see the same truth at the same time.
• Operator deep-links — footer rail to ESD Booking, Docs, Checklists, TMC Admin, E3.

Why two .quest domains?

tmc.quest anchors the messaging side of the ESD platform; esd.quest anchors the booking and operations side. Same pattern of leaving a deliberately public status board where most stacks would put a marketing splash. The domains are cheap and the posture is expensive — owning both lets the platform speak for itself from two sides.

Why ship a placeholder as a portfolio entry?

Because the placeholder is doing real work. It anchors the domain, it surfaces the live state of the systems pointing at it, and it sits in the rotation of "show me what's deployed right now" the operator already trusts. The eventual full host is a content swap, not a rebuild.