Internal — Clara’s knowledge for Situs Group, built portfolio-first from a fact schema. Every value is extracted against the 112 fact keys in the onboarding question bank, from the lease and addendum text pulled from AppFolio on 2026-09-02, the company and property settings, the public listings, and the 2026 apartment message corpus. A document or setting wins and is confirmed; message-only evidence needs five messages from two authors, otherwise it is unconfirmed and goes to Needs you rather than into the facts. Live state is never stored. Knowledge lives at the portfolio level; a building carries only what differs. Interactions are staged. Residents and prospects are scrubbed; Situs’s own public contact details are facts and appear verbatim.

Situs Group / / Clara’s knowledge

What Clara knows

Demo viewUpload document

Ask Clara

Clara

Source

That’s wrong or outdatedAsk another

Tell Clara what changed — plain words are fine.

Saved. Clara uses it everywhere from now on — the value it replaced stays in history.

Leasing

We still don’t know — tell us, or upload the document that covers it.

    Needs you

    Answered once, for everyone. A conflict appears here once, not per building.

    Asked most, 2026

    Amber = the share she came up short on — click it.

    Fill list — go get it, nobody decides

    Rules nothing in writing covers. Upload the document that covers one and it is re-derived; nobody types a policy in.

    Live state — read, never stored

    These are not facts. Clara reads them from AppFolio when she is asked, so they cannot go stale.

    Property overrides

    Current settings — move-in concessions by building and month

    Not a conflict: the weeks free move by building and by month. Carried as unconfirmed until someone puts a rule and a valid-until date behind them.

    Recently learned

    What was dropped, and why →

    PropFlow Docs