Atlas map dangling claims
The org map lists the company's claims that no building carries, found through its own map log
2 Oct 2026 · branch ui-atl-d-dangling-claims · captured against propflow-stage · at 246eefb4b9d
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 · Fairhaven Residential (TEST): a logged claim off every column, correctly not listed
The focused TEST company in the Map view. Its map log holds one phone claim that no building's number column carries. That number is routed to a building in code, so the map already draws it as a pill, and it is correctly NOT listed as a claim no building carries. Stage holds no real dangling claim on any company (a read-only probe of every stage company found none), so the listed case is pinned by the render tests named in the PR body rather than photographed.
Masked for publishing: 8 × property-line, 1 × tester — PropFlow's own lines, as listed in config/phone-registry.json. Any other phone number on the page was left in place for the contact scan.
Asserted in the captured DOM — One tree per org · have no head row
