Building › Knowledge in Settings — one editor, two homes
Board row sr-building-knowledge, part 1: the building page's knowledge card now also lives at /settings/property/knowledge, rendered by the same component.
24 Sept 2026 · branch sr-building-knowledge-p1 · captured against propflow-stage · at b578e10b72+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 · 1 · No building picked — it asks
With the whole company selected there is no one building, so the page says so and points at the picker. It does not quietly open the first building in the list.
Asserted in the captured DOM — Building knowledge · Pick a building
2 · 2 · One building picked — the building page's own editor
The same Knowledge Base card as the building page, with its sections, Add and Upload Document, read from that building's record. It is one component, PropertyKnowledgeEditor, used in both places.
Asserted in the captured DOM — Building knowledge · Property Knowledge Base · Upload Document
3 · 3 · The building page — unchanged in this part
Part 1 moves no pixels on the building page. It renders the extracted component where the inline card used to be. Part 2 replaces the full editor there with a summary and a link to Settings.
Asserted in the captured DOM — Property Knowledge Base · Upload Document
Not photographed
The empty building (nothing on file) and failed-read states are pinned by settings/property/knowledge/__tests__/page.dom.test.tsx. The first-upload re-read is pinned by PropertyKnowledgeEditor.first-upload.dom.test.tsx, which was positive-controlled: it goes red with the fix removed.