The Today View

The Today view is your daily briefing as a page. /day builds the dashboard and opens it on this view, and chat carries only the link and up to five red items. The build script works out every figure from your files, and Claude adds a short set of notes.

How the View Comes Together

/day follows these steps whenever the dashboard build script and its template are present, as they are in this release.

1. Claude marks any in-progress project whose due date has passed as overdue.
2. If you switched on a calendar or meetings integration, Claude fetches events for the next seven days into an events file.
3. The build script runs with --landing today and works out every panel on the view.
4. Claude writes up to ten notes to a notes file, then runs the build again so the page carries them.
5. Claude opens the finished page in your default browser and reports the red items in chat.

/dashboard builds the same Today data from the events and notes files that /day last wrote, though it never writes those files itself. The Daily Briefing covers the /day side in full.

The Page Header

The header shows the day and date, the build time and your workspace name. A typical header reads “Wednesday, 14 October 2026 · built 08:42 · Example Consulting”.

Source Banners

The view opens with a banner for each source that failed. Each banner names the source, the error and the fix. A broken events file or a CRM database that will not open each produce one. An events file from an earlier day also produces a banner, which tells you to run /day again. The rest of the page still builds when a source fails.

Health Cards

Four cards count your projects by health, and clicking any card opens the Projects view.

Card	Projects counted
Active	In progress and worked within the last 7 days
Stale	In progress and last worked 8 to 27 days ago
Needs attention	Overdue, or in progress and last worked 28 or more days ago
Paused	Paused

An in-progress project with no lastWorked date counts as Needs attention.

The Panels

Panels sit in pairs below the health cards. The view hides a panel when its source is missing. A workspace without PRIMA CRM or a content pipeline therefore sees fewer panels.

Panel	What it lists	When it stays hidden
Where You Left Off	The summary of your last session, then each project worked in the last 7 days that has a stoppedAt note, newest first	Never. It says “No recent session recorded.” when empty
Today and Next 7 Days	Calendar and meeting events with CRM follow-ups due in the range, in date and time order, each with its source and a join link where the event has one	Never. It says “No events file” when /day has not written one
Needs You	Overdue projects, overdue CRM follow-ups, decisions waiting in the content pipeline and your pending items	Never. It says “Nothing waiting on you.” when empty
Claude’s Notes	Up to ten recommended actions and anomalies, each with its project ID where one applies	No notes file
Stale Clients	Active PRIMA CRM companies with relationship client whose last contact is older than their contact cadence, never-contacted first	No PRIMA CRM database
Content Pipeline	Content runs that are not complete, and articles prepared for publishing in the last 14 days with no run	No content pipeline set up
Priorities	Your Immediate and This Week priorities from the register	Both lists empty
Repo Drift	Projects whose notes name a code repository with commits newer than the project’s last worked date	Nothing to report

Any project ID in a row is a button that opens Project Detail for that project. A banner at the foot gives the build time and reminds you to run /day and reload.

Red and Amber Rows

Red marks overdue projects and overdue follow-ups. It also marks content runs older than seven days or with decisions pending, and prepared articles with no run. Amber marks follow-ups due today and stale clients. It also marks decisions waiting on you and anomalies in Claude’s notes.

The Files Behind the View

File	Written by	Contents
Documentation/Reports/prima-dashboard-events.json	Claude, during /day	Events for the next seven days, and the result of each calendar fetch
Documentation/Reports/prima-dashboard-notes.json	Claude, during /day	Up to ten notes, each an action or an anomaly
.prima-crm/crm.db	PRIMA CRM	Follow-ups and companies, read without changes
.claude/config/prima-dashboard.json	You	The content pipeline folders

The events file holds only the date, times, title, source and link of each event. Claude leaves out event descriptions, attendee lists, passcodes and dial-in details. Without a calendar or meetings integration, Claude writes no events file. The timeline panel then shows CRM follow-ups only.

Note

Keep the events and notes files out of your commits, using the .gitignore lines on the Installing PRIMA Project Management page.

Optional Panels in Detail

Stale Clients

The panel reads PRIMA CRM’s database without changing it. A company counts as a client when its relationship is client. A company with no relationship also counts when any of its project links is a client link. Clients have a default contact cadence of 30 days. PRIMA CRM’s settings, or a cadence on the company itself, change that figure. Stale Clients and Contact Cadence explains cadence.

Content Pipeline

This panel appears only when you create .claude/config/prima-dashboard.json and name a folder of content run files in it.

{
  "contentPipeline": {
    "runsDir": "Content/Runs",
    "articlesDir": "Content/Articles",
    "publishedSuffix": "-final.md"
  }
}

Key	Meaning
runsDir	A folder of JSON run files, one per piece of content. The panel leaves out a run whose currentStage is complete
articlesDir	Optional. A folder of article folders to check for work prepared for publishing with no run
publishedSuffix	Optional. The file name ending that marks an article as prepared for publishing. The default is -podia.md

The product ships no template for this file and no tool that writes run files. The panel suits a workspace that already keeps its content runs in this form.

Repo Drift

The build reads each in-progress project’s notes, description, stoppedAt and lastAction. It looks there for a path to a git repository inside a Developer folder in your home folder, such as ~/Developer/spring-site. If that repository has a commit dated after the project’s lastWorked date, the project appears in this panel with the commit date, hash and message. The build does not check repositories kept anywhere else, so a project whose code lives in another folder never shows here.

Related Pages

• The Daily Briefing explains /day, which builds and opens this view.
• Dashboard Views covers the other nine views.
• Status and Traffic Lights explains the Active, Stale and Needs attention bands.