Venue property and facility management · build status
The system a venue runs on, extending event.clinic's spine with an `estate` schema. Unlike its siblings, the ledger below is GENERATED from the navigation source rather than written — a hand-kept list of what is done reports 100% forever.
E1 – E4 · 4 slices
4 complete
E5 – E9 · 5 slices
5 complete
E10 · 1 slice
1 complete
E11 – E16 · 6 slices
6 complete
E17 – E20 · 4 slices
4 complete
E21 – E23 · 3 slices
3 complete
E24 – E30 · 7 slices
7 complete
E31 – E35 · 5 slices
4 complete · 1 not started
E36 · 1 slice
1 complete
E37 – E38 · 2 slices
2 complete
E39 · 1 slice
1 complete
E40 · 1 slice
1 complete
E41 · 1 slice
1 complete
| Slice | Name | Status | The ledger’s note |
|---|---|---|---|
| Group Global — Portfolio | |||
| E1 | Venues | built | / |
| E2 | Compliance | built | /portfolio/compliance |
| E3 | Utilisation | built | /portfolio/utilisation |
| E4 | Board pack | built | /portfolio/board |
| Group Global — People and access | |||
| E5 | Tasks | built | /tasks |
| E6 | People | built | /people |
| E7 | Roles and permissions | built | /roles |
| E8 | Activity | built | /activity |
| E9 | Invitations | built | /invitations |
| Group Venue — Overview | |||
| E10 | Command view | built | /overview |
| Group Venue — The building | |||
| E11 | Venue profile | built | /venue |
| E12 | Buildings and spaces | built | /structure |
| E13 | Asset register | built | /assets |
| E14 | Planned maintenance | built | /ppm |
| E15 | Cleaning | built | /cleaning |
| E16 | Work orders | built | /work |
| Group Venue — Compliance and safety | |||
| E17 | Statutory register | built | /compliance |
| E18 | Risk register | built | /risk |
| E19 | Incidents | built | /incidents |
| E20 | Contractors and permits | built | /contractors |
| Group Venue — Crowd and security | |||
| E21 | Capacity and crowd | built | /capacity |
| E22 | Lost property | built | /lost-property |
| E23 | Security operations | built | /security |
| Group Venue — Commercial | |||
| E24 | Function diary | built | /diary |
| E25 | Enquiries and rates | built | /pipeline |
| E26 | Event orders | built | /orders |
| E27 | Purchases | built | /procurement |
| E28 | Public listing | built | /listing |
| E29 | Events here | built | /events |
| E30 | Catering | built | /catering |
| Group Venue — Media and documents | |||
| E31 | Photos and plans | built | /media |
| E32 | Drawing register | built | /drawings |
| E33 | Layouts and zone maps | built | /layouts |
| E34 | Brand kit | built | /brand |
| E35 | Seat assignment — who sits in each seat | planned | Declared on planned; no surface, no route, and nothing rendered. |
| Group Venue — Settings | |||
| E36 | Settings and vocabulary | built | /admin |
| Group Event — This event | |||
| E37 | Event workspace | built | /event |
| E38 | Venue brief | built | /event/brief |
| Group Event — Operations | |||
| E39 | Operations log | built | /event/operations |
| Group Event — Safety | |||
| E40 | Crowd and permits | built | /event/safety |
| Group Event — Commercial | |||
| E41 | Booking and orders | built | /event/commercial |
scripts/
that exits 0 against the code as committed; a slice whose script has not
exited 0 in a single run is not complete here, whatever else was built.
Exit 2 means BLOCKED — something could not run, so the tree was NOT measured. That is not a pass, and it outranks FAILED: no answer is more dangerous to act on than a bad answer. Three checks are local-only (they create roles and write fixtures) and are reported as SKIPPED against dev, never as passes.
./scripts/verify-all.sh local
# both servers from one shell — the launch.json entry `estate-local` cd ~/Documents/property-management/api && npx wrangler dev --port 8811 & # API # the portal. 5188 is not arbitrary — it is the API's ALLOWED_ORIGIN cd ~/Documents/property-management/app && npm run dev -- --port 5188 --strictPort # load the schema and the demo venue locally cd ~/Documents/property-management && ./db/apply.sh --with-demo # prove the tree before believing any status above cd ~/Documents/property-management && ./scripts/verify-all.sh local # regenerate this page's ledger from the navigation source cd ~/Documents/property-management && python3 scripts/build-ledger.py
Estate uses real paths, not hash routing, so every link below survives a reload and can be pasted to someone else. The venue workspace is keyed by `?site=` and the event workspace by `?event_id=` — a link without one lands on the picker rather than guessing, which is deliberate: an operator with three venues used to see only the first.