SELF • first draft • 20 September 2026

Notion dashboard blueprint

One readable home for plans, conversations, priorities, ideas and audio.

Review specification. Checkboxes are review aids, not proof a real planning session happened. Automated saves, retrieval and audio delivery are proposed until verified.

Dashboard above the fold

Three revenue priorities

Prominent current-project callout, revenue hypothesis, constraint, next experiment, metric and last review. Leave choices unconfirmed until Matt selects actual projects.

Today and this week

Current daily plan, latest digest, weekly plan, morning audio links and pending closeout results. Habit tracking remains a link to the existing Google Sheet.

Agent context

Current planning mode, readable sources, write scope, actually loaded content, freshness and missing access. No implication that an entire dashboard is automatically in context.

Seven databases · one physical home

All new source databases live under Matt’s existing Databases page. The fresh private dashboard shows linked filtered views only.

Daily Plans

Date, target date, main outcome, approval/status, version and related conversations/projects/audio. Plan and actual review remain distinct.

Planning Horizons

Weekly, monthly, quarterly and yearly records with horizon, dates, state and related projects. Separate filtered views provide each horizon.

Projects

Revenue hypothesis, constraint, experiment/action, leading metric, priority, review date and status. Active focus displays the selected top three.

Conversations

Full transcript in page content/attachment, date, type, source/session, summary, decisions, completeness and indexing state.

Audio Library

Audio kind, full transcript, private playback link, duration, source-plan relation, version, generation and delivery states.

Knowledge and Direction

Daily/weekly routines, goals, principles, beliefs, lessons, pitfalls and review artifacts. Current/draft/superseded status and version provenance.

Ideas and Future Projects

Title, concise idea, tags, date, source conversation and inbox/later/review/rejected state. Capture and deduplicate at closeout.

Read, write, verify

Linked views provide clarity for Matt. A small source index gives agents stable database identities and retrieval instructions independent of a particular model. Future skills can use those services from another harness if its connectors, authentication and tool support exist; portability is not automatic.

Draft structure is created now. Conversation closeout automation, routine retrieval and audio delivery remain later build work. The Notion verification report will distinguish what actually passed from what is only designed.