Nineteen kinds of record. No screen for most of them.

What to look at, before you look at anything else.

• TodayWhat's overdue, due today, in flight, and stalled — assembled fresh each time you ask. Due today is not called late; the day boundary is yours.
• LoopsCommitments made out loud that haven't closed yet. Surfaced when you ask; nothing watches for you in the background.
• CalibrationWhether your decisions turned out the way you thought. Refuses to score below five closed decisions — with 0 outcomes recorded so far, it currently reports nothing.

What's moving, and what's stalled.

• Tasks506 logged, 211 completed. The rest sit open, stalled, or backlog — and backlog is excluded from the numbers so deferred work doesn't quietly drag them down.
• InitiativesHealth and momentum, computed from the state-change trail on every read. Nothing derived is stored here, so nothing goes stale between visits.
• Solutions47 recorded. Each one is meant to close a repeatable problem, not answer it once and get forgotten.

Where a stray thought lands before it becomes anything.

• Inbox190 observations logged, 0 triaged so far — nobody's gotten to them, and the page says so rather than hiding the backlog.
• Ideas51 logged, 2 acted on. Most ideas stay ideas, and that ratio is shown rather than smoothed over.
• SignalsConfigurable, and honestly inert. Nothing runs on a schedule, so a signal only exists the moment you ask for it.

The people and the deals attached to them.

• Deals14 in the pipeline. Every stage change is written to a trail, so "how long has this sat here" stays an answerable question.
• ContactsMatched from a name in conversation, or created if new. An ambiguous match is refused rather than guessed at — a duplicate contact has no undo.

The record you go back and read.

• Knowledge88 entries. Plain notes, searched for the words you actually said, not the inside of a file.
• DocumentsA filename and a link. The contents are never stored or searched — a real gap, not a design choice dressed up as one.
• Decisions112 recorded, 0 outcomes written yet. The review date gets set at the time; the verdict waits for the date to actually arrive.
• MeetingsLogged from what you say happened, dated when it happened. If you don't say when, you get asked instead of guessed for.
• Changelog564 entries. What shipped, kept separate from what was merely announced — the two disagreeing is itself a finding.

How it's built, and the one screen you actually use.

• AuditThe tenancy probe, in full: 55 cross-account attempts across 27 tables, 47 refused by the database itself, 8 guarded in code.
• SettingsThe one page reached with a browser instead of a sentence — modules, alerts, sync configuration. Everything a credential or an OAuth redirect requires.
• GraphHow records point at each other — a contact to a deal, a decision to an initiative — read back on request, not maintained as a separate map that can drift from the source.

What isn't on this list, and why.