Clara's paths — the customer page tab
Every path Clara can act on for one customer, in one table, with its mode edited in place; unwired rows grayed with a reason
29 Oct 2026 · branch feat/clara-paths-tab · captured against propflow-stage · at 8462cb15646+local
Data note. Every name and balance below comes from propflow-stage, which is anonymized by construction (ADR-0097/0110 — phones in the impossible +1000 NPA, emails @example.test). The identical capture against prod would carry real tenants' names and balances and is not safe to attach anywhere, which is why the generator refuses to run against one.
1 · THE TABLE — 70 paths grouped by module, the mode select live only where the path is wired
Fairhaven Residential (TEST) on stage. One arsenal DataTable: Path with the (i), Module, To · by, Mode (our select), Level, Building overrides. A path no mode governs, or one Supervised would drop instead of hold, shows a grayed select whose title is the one-line reason (Gera, 2026-10-29: grayed until wired, never hidden).
Asserted in the captured DOM — Clara's paths · Answers prospects by text and email · Texts the in-house handyman the job · Rings the on-call list one by one · Always on · No mode. The page title, a Leasing row, a Maintenance row, an emergency row, and the two grayed-select words.
Sections 2–2
2 · THE OVERVIEW — the same customer, with the new pill strip beside the title
Overview · Clara's paths, links, so each page keeps its own URL. The Modules card is unchanged.
Asserted in the captured DOM — Overview · Clara's paths · Modules. Both strip items and the Modules card heading.
