One card per person, not per booking or per handle. Someone who emailed, booked on Airbnb and later phoned is a single guest here, because their email, phone and platform id resolved to one contact.
Every listing across both Guesty tenants, ordered by the support traffic it generates. Each card says whether a reply template could actually be filled for that unit, which is the usual reason a draft gets refused.
Every draft Genie wrote is kept, rejections included. A rejected draft is the most informative row here: it is a case the catalogue got wrong. Paired with what the operator actually sent, it is the evidence for fixing a template rather than an opinion about it.
Every recurring thing a guest asks, and how much of the answer Genie is trusted with. A pattern climbs the ladder on evidence: matches earn a draft, accepted drafts earn autonomy, one rejection takes it back.
What actually arrives, per channel, from the database. This is the intake denominator the week-one memo said did not exist anywhere in the stack.
Every model call the platform makes, costed as it happens, against a ceiling somebody set. Anthropic does not publish a credit balance to an ordinary API key, so this measures what we spend rather than what remains.
Everything Genie reads, and whether it is still reading it. A connector that stops is only useful news if someone can see it stop, so each one carries its last successful pass and the actual failure text when there is one.