Building › Policies, read-only
One building's pet rules: its own value first, the company rule and lock, and what Clara quotes
25 Sept 2026 · branch sr-building-policies-page · captured against propflow-stage · at 023098989e+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 · One building's pet rules, as its manager sees them
The building picked in the top bar. Each pet charge says where this building's answer comes from (Set here, From your company, Locked by your company or Not provided) and what Clara quotes: the API's own answer, never re-derived here. With no value anywhere, nothing is invented. Policies now sits under Building in the menu.
Not shown: stage holds no pet charges for this building (prod has none either), so every row is Not provided. The other states are pinned by page.dom.test.tsx. I did not write values into the shared stage table for a picture. The top bar's All Properties comes from the capture setting the picker cookie directly, as in earlier captures.
Asserted in the captured DOM — Building policies · Pets · Pet fee · Pet deposit · Monthly pet rent · Unauthorized pet fee · Clara · Policies. All four rule names, a Clara line on each, and the menu entry.
Not in this part
Editing (Change for this building, Use company default) is part 2b. The server already refuses a change to a locked rule (#12191).