Onboarding tab, part 3d: Leasing › Applying
How applicants get the link, and six fixed questions saved as company knowledge Clara reads
30 Sept 2026 · branch feat/onboarding-leasing-knowledge-p3d · captured against propflow-stage · at 55cd0dd7d5e+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 · Leasing › Applying
The Applying section asks how applicants get the application link, then six fixed questions about the application. Each answer is a company knowledge section, which Clara reads for every building. Open questions carry a blue dot.
What to look at
The link question offers the same two choices, in the same words, as Company › Leasing. The six questions have fixed topics, so nobody can add a free-form one. That matches Fede's knowledge rules and Gera's "fixed questions only". Each answer is one short line, because Clara may read it aloud on a call.
Asserted in the captured DOM — Applying · How applicants get the application link · Income requirement · Co-signers and guarantors. The link question and the knowledge questions rendered.
Two critique rounds, against the mock and brand-and-design.md
Round 1 and round 2
Round 1 (against the mock). The mock's Applying section asks the same things, in the same order: how applicants apply, decision time, documents, income, portable screening, co-signers, vouchers. The mock shows three ways to apply. The product stores two (one link for everyone, or a new link per prospect), so the page offers exactly those and invents no third.
Round 2 (brand-and-design.md). Every label is a plain question, and every help line is one sentence. There are no field names and no ids on screen. The radio group is the arsenal's own. Nothing was saved in the capture. The writes are pinned by the route and DOM tests.