Knowledge requests — the Policies tab
Optional core topics ingest found unwritten, asked with their own Settings editors; never onboarding
22 Oct 2026 · branch feat/knowledge-requests-p1 · captured against propflow-stage · at da34108cd65
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 · Desktop: /knowledge-requests
Three optional core topics ingest looked for in the company's own systems and found written nowhere, asked with the same editors Settings › Knowledge & policies uses: the same answer Clara reads, stored once. The count is the page's own and never moves go-live progress.
Asserted in the captured DOM — Knowledge requests · answered · Packages · Amenities · Quiet hours. The page loaded its counts (not the ghost or the error card) and shows the three topic editors.
Sections 2–3 and notes
2 · Phone width
The same page at phone width: choices and fields wrap inside each card, nothing scrolls sideways.
Asserted in the captured DOM — Knowledge requests · Quiet hours
3 · The old address redirects
The link sent to a customer on 2026-10-21 lands on Knowledge requests.
Asserted in the captured DOM — Knowledge requests · Policies
What is not in the picture
No answer was saved, so nothing was written to stage. The count, the re-count after a save, the company switch and the failed-read card are pinned by client-page.dom.test.tsx. The side-nav ring and the inbox item land in part 1b.