How to Use
A guide for reading the dashboard and understanding the system.
Reading the Dashboard
Scorecard
The four numbers at the top tell you the commit health at a glance. Committed is what was promised. Delivered is what shipped with evidence. In Progress and Not Started show the remaining work.
Initiatives
Each card is a strategic initiative — a goal the company is working toward. The progress bar shows how many of its committed tasks have been delivered. Tasks within an initiative are sorted by priority.
Tasks
Each row is a piece of work with a single owner and a verifiable outcome. Indented rows are subtasks — deliverables within a larger task. The badge on the right shows current status.
Decisions
Decisions extracted from meetings and logged with attribution. These are the choices that shape the work — who decided what, when, and why.
30-Day Commits
A commit is a monthly cycle. Every task in a commit is a promise — at the end of the month, it's either Delivered, Carried (with a reason), or Cut (with a reason).
Carried tasks get one grace period. If a task is carried twice, it gets escalated — flagged in the commit review with a pattern warning.
The commit review happens on the last business day of the month. The system generates the review: what delivered, what carried, what cut, and a velocity trend.
Not all tasks have a commit. Tasks without a commit assignment are backlog — defined and ready to be pulled into a future commit, but not promised for this cycle.
Status Badges
| Badge | Meaning |
|---|---|
| Delivered | Done with evidence. Shipped. |
| In Progress | Actively being worked on. |
| Not Started | Committed but work hasn't begun. |
| Blocked | Can't proceed — dependency or issue. |
| Committed | Promised for this month's commit. |
| Carried | Didn't deliver last month, carried forward. |
| Cut | Removed from the commit with a reason. |
How Data Gets In
Nobody updates the dashboard manually. The system ingests from six sources automatically:
- Meeting transcripts from Google Meet (via Gemini) — decisions, action items, and status updates extracted automatically.
- Jira tickets — engineering work tracked across multiple boards.
- Google Drive — documents and spreadsheets monitored for changes.
- GitHub commits — concrete evidence of what's being built.
- Notion — the source of truth for all structured data.
- Slack — real-time signals from team channels.
A sweep scans all sources, cross-references findings, writes to the knowledge graph, and proposes updates. Updates go through a review queue before anything is written to Notion. Sweeps run on demand now, daily by Phase 2.
Need Something?
The system is designed to answer questions about any initiative, task, or decision. Common questions:
- "Where are we on CRM?"
- "What happened in the engineering standup this week?"
- "What decisions have we made about processing?"
- "What's blocking PROD-01?"
Today, ask Noah. Soon, the system will have a conversational interface where you can ask directly and get a grounded answer with citations.