Everything I could decide myself is decided. What's left needs
you. Each one carries the recommendation of the session that raised it — if you
agree, pick it and press Done. A model's opinion, where there is one, appears on the card
as a receipt line; cards with no receipt were never put to a model. "I'm not sure" is a real answer and becomes work for me.
You don't need to open the session — pressing Done sends your answer back and it picks up.
1Wire resolveEffective over knowledge.section.<id> into the voice knowledge read (leasing-context-injection.ts:1555 and voice/personalization/route.ts:1099) so org-level sections append to property sections. Today both call getPropertyKnowledge(propertyId) only; resolveEffective and putSettingAttachment have zero production callers. Design-final assigns rekey-umbrella-rows.ts to Gera by Sep 19; the resolver slice itself is unowned. Order after this: verify anchor still speaks all six sections -> match 15 listings to the 60 existing PROP# rows (5 are unit-level) -> move facts -> anchor retirement as Fede's separate go.
In plain terms. Should lane 003 build the company-level knowledge read for Clara's phone calls now, or wait for Gera? Today Clara only reads each building's own facts, never the company's. Western Slope's company rules (screening, fees, pets, contact) work on the phone only because they sit on the stand-in front-door building. Moving them up to the company before Clara can read company facts would silence those answers on a live line. The read plumbing is the first step, changes nothing callers hear on its own, and sits next to the anchor retirement the design already assigned to Gera. Nothing moves and nothing goes live until this is answered.
The session raising this recommends: 003 builds the read plumbing now, dark Read-side only, no caller-visible change, and it unblocks Gera's Sep 19 re-key instead of competing with it. Tried first, unsuccessfully: Read origin/main and prod: voice knowledge comes from getPropertyKnowledge only (two call sites); the org resolver and attachment writer exist with zero production callers; prod holds 60 property rows for the org so no rows need minting. Design settles the shape and assigns the anchor retirement to Gera, but names no owner for the resolver wiring, so ownership is the one thing code and docs cannot answer.