Company Modules card: Off, Drafts and Live

Each module's company switch becomes Off · Drafts · Live, with emergencies shown locked on (gk-settings 12.1b)

29 Sept 2026 · branch gk-settings-12-1b · captured against propflow-stage · at 4b7d95948c+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 Modules card, three choices per module and one locked row

Each module's on/off switch is now a choice of Off · Drafts · Live. Drafts stores the module as on plus a moduleModes[m] = 'drafts' marker beside it; Live is on with no marker; Off clears the marker. The on/off answer every gate reads is unchanged.

The last row, Emergencies and team alerts, has no control: it reads Always on, because those sends are never held and never switched off. The line under the card says plainly that Drafts is not enforced yet.

Asserted in the captured DOM — Modules · Emergencies and team alerts · Always on · Never held for approval and never switched off. · Drafts means Clara prepares and a person approves before anything goes out.. The card rendered with the locked row and the not-enforced-yet line. No save was run.

The Modules card, three choices per module and one locked row

What is not in the picture

No save was run, so nothing was written to stage. The stored shape of each choice is pinned by the repository and route tests.

PropFlow Docs