event.clinic · suite overview
Each figure below is parsed from that product’s own build ledger by the same code that renders its own status page, so the two cannot disagree. Nothing here is typed in by hand.
The events platform the other products read from — and the only one
publishing a no-login surface, /directory/v1.
Three products read event.clinic’s database directly, one consumes its public directory,
and the layout and seat-map engine lives in its repository and is shared rather than copied.
One caution worth stating plainly: much of that coupling is currently accidental —
ALTER DEFAULT PRIVILEGES grants every new app table to Mise unless
someone remembers to REVOKE. A declared hub should mean a published contract,
not more implicit sharing.
Event procurement
128 complete · 128 total
Carries a bucket no sibling has — verified, not deployed: a suite exits zero but the migrations are local only, so nobody can reach it.
Temporary workforce
54 complete · 54 total
Not yet coupled. Mise’s X4 exists to receive its crew (agency kind, agency_worker_ref) and is blocked on Q-007.
Venue & property portal
43 complete · 1 not started · 44 total
The venue side of event.clinic — an estate schema on the SAME database, with foreign keys straight into app.venue. Its ledger is the only one in the suite generated from source rather than written: rows come from the navigation, and a surface with no route is reported unreachable rather than complete.
Artist management
32 complete · 1 in progress · 33 total
Own auth, own database. The sell side of the live deal. Ecosystem bridge is S31 — pending, and it says to re-measure siblings first.
Open the ShowLedger24 status page →Wedding planning · live at velawel.com
92 complete · 6 in progress · 1 nothing to build · 99 total
The only product already serving real users. Mise’s X5 turns its guest list into seat-level requirements and refuses to guess which sitting a requirement belongs to. No transport yet — Q-007.
Open the VELA status page →AV production & rental
30 complete · 3 in progress · 33 total
Lives in the av schema of event.clinic’s database, read-only on app. Couplings are T22 and T30, both not started.
Catering management
58 complete · 3 in progress · 8 not started · 69 total
Reads event.clinic directly as mise_rw — identified by the database role it connects as, impersonating no tenant.
Transition planner · nruceo.event.clinic
79 complete · 61 on production, no suite · 2 in progress · 142 total
Runs against event.clinic through a mirror with its own token. Scheduled jobs run from ~/nruceo-live, not from the repo — editing the repo alone changes nothing.
Recorded in Mise’s own ledger as slices X1–X6 — the one place the couplings are currently written down. Two of the six have no transport: the logic is built and tested, but nothing carries the payload between products.
| Slice | Coupling | Status | The ledger’s note |
|---|---|---|---|
| X1 | Mise → event.clinic | live | Reader, snapshot model, sync check and exception lifecycle all built and tested. The engaged event returns rows; an unengaged one returns none. |
| X2 | Mise → Estate | partial | GET /api/venues/:id joins venue, spaces, Estate’s diary and Mise’s kitchen. Reads Estate defensively and returns estateReadable: false rather than an empty array. |
| X3 | Mise → Procurevent | partial | Bid requests, requirements, responses and the submission gate all built. No transport — Q-005. |
| X5 | Mise → VELA | partial | The inbound receiver stores verbatim then processes. It refuses to guess which sitting a requirement belongs to. No transport — Q-007. |
| X4 | Mise → Verbunk | not started | The agency crew kind and agency_worker_ref exist to receive it. Q-007. |
| X6 | Mise → Rigfold | not started | Same database, so the cheapest of the six. |
11 of 11 answering. Every hostname is read from a wrangler routes
block, never guessed, and probed once when this page was built — so these are a
snapshot, not a monitor. A site that breaks after 2026-09-05 11:45 UTC still reads green here until
the next build.
| Host | Answered | Worker | What it is |
|---|---|---|---|
| event.clinic | 200 | event-clinic-web | Marketing site |
| app.event.clinic | 200 | eventclinic-web-production | The portal |
| api.event.clinic | 200 | eventclinic-api-production | API. Probed at /directory/v1, the only no-login route |
| velawel.com | 200 | vela-app | VELA, live |
| my.velawel.com | 200 | vela-app | VELA couple portal |
| velavel.com → https://velawel.com/ | 200 | velavel-redirect | Redirects to velawel.com |
| procurevent.com | 200 | procurevent-redirect | Marketing / redirect |
| app.procurevent.com | 200 | procuvent-app | Procurevent app |
| admin.procurevent.com | 200 | procuvent-app | Admin |
| api.procurevent.com | 200 | procuvent-api | API. Probed at /v1/health, since the root 404s by design |
| estate-dev.marikpeter.workers.dev | 200 | estate-dev | Estate, dev only |
Not probed: odu (last modified 2026-07-13) · showfold-group (last modified 2026-07-12) · verbunk (last modified 2026-07-18, predates the current Verbunk build) · procuvent-site (site Worker, route not in config) · procuvent (route not in config) · estate-api-dev (dev API, no public route). These Workers exist in the account
but declare no public route in their config, and a guessed hostname would report a real 404
about an address that was never theirs.
None — every product above is generated from its own ledger. This section listed Estate and Procurevent as having no ledger, and did not mention NRÜ at all. All three had one. A dashboard that states an absence has to re-check it, or it becomes the most confidently wrong thing on the page.