The inbox

The inbox is where the system asks you things. Each card is one sentence with a reply box. Answering it is the single most useful thing you can do, because your answer becomes something it knows for good.

The kinds of cards

• Something it heard. From the interview, a forwarded email, a note, or an agent. It says whether this is new, confirms what it knew, changes it, or contradicts it. Approve, and it becomes a confirmed fact with your name on it. Only a person can confirm; nothing a model writes is ever confirmed on its own.
• A number that moved. Every night it re-runs every definition. A value that moved more than a couple of percent from last time, or a query that now errors, becomes a card. Reply with why, and that reason travels with the number from then on.
• Something broke. A sync that failed, a key that expired, a table whose shape changed. The card says what and, where it can, offers the fix.
• A number computed twice. The same measure over the same base in two dashboards or queries with no definition yet. Approve it and it's defined once, with an owner.
• Something going stale. A fact it only heard, never confirmed, expires after thirty days unless someone says it's still true.

Cards by email

A card can be addressed to whoever owns that number. They get one email with the question and a reply box; their reply lands as a dated decision with the question as evidence. Nobody has to log in to answer.

What to say to it