Knowledge requests — Buildings › Security deposit
The hub's own fee card, asked for the deposit only; pre-filled from the rent roll when ingest saw one; Apply confirms
23 Oct 2026 · branch feat/knowledge-requests-unit-sizes · captured against propflow-stage · at eca1505fc6d
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 · Pre-filled from the rent roll: "seen, confirm"
With one made-up pre-fill item for the TEST company (written to stage, deleted after this capture), the deposit card's Set-for-all box carries the amount most buildings showed, with its source. The note on hover reads "$1,200 at 3 of N buildings from your rent roll. Please confirm." Pets and Utilities show their notes the same way. Nothing is written until Apply / Save.
Asserted in the captured DOM — Pet rent seen · from your billing · Rent includes water and trash · Security deposit. The evidence notes from the synthetic item are on screen.
Sections 2–3 and notes
2 · Desktop: the Security deposit card under Pets and Utilities
The third Buildings question is the same fee card onboarding and Settings › Fees & deposits use (Set for all, then Set individually), limited to the deposit. Its Apply writes each building's deposit with the confirm stamp and confirms this section for the count.
Asserted in the captured DOM — Security deposit · Set for all · Set individually · Pets · Utilities. All three Buildings questions loaded from the one read.
3 · Phone width
The card fits at phone width; nothing scrolls sideways.
Asserted in the captured DOM — Security deposit
How the pre-filled state was captured
One synthetic pre-fill item for the TEST company was written to the STAGE table (not production: production already holds ingest's real item for this company, which a put would have overwritten), read by this branch's dev server through INGEST_SHEETS_TABLE, and deleted right after; its JSON and commands are kept in the lane notes. No save was run.