create-pmos 0.59.3 → 0.60.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "create-pmos",
-  "version": "0.59.3",
+  "version": "0.60.0",
   "description": "Scaffold the PMOS portable kit — run the PMOS product-management workflow (initiative → lane-fit spec → contract → build → three gates, with work-type lanes for features, research, maintenance, incidents, and content) entirely inside your own repo, with all state as git-versioned files. Includes `workflow-sweep`, which audits the state every board derives from and separates real defects from work you simply have not done. `create-pmos workspace` also installs + launches the local Terminal Workspace GUI. No database, no network, no telemetry.",
   "license": "MIT",
   "bin": {

package/payload/KIT-VERSION

@@ -1,3 +1,3 @@
-kernel-source: pmos@ad3caaf
+kernel-source: pmos@45d7d1e
 assembled: 2026-10-06
 mode: vendor

package/payload/planning/evals/eval-calibration.md

@@ -2,7 +2,7 @@
 type: Reference
 title: "Eval calibration log"
 description: "Append-only record of every PM override of an evaluator verdict."
-generated: {by: process:create-pmos, at: "2026-10-06T14:43:28Z"}
+generated: {by: process:create-pmos, at: "2026-10-06T15:12:25Z"}
 status: stable
 ---
 

package/payload/planning/okrs/health-budgets.md

@@ -2,7 +2,7 @@
 type: Reference
 title: "Health budgets"
 description: "Closed registry of health-budget anchors (D59), edited only by the PM."
-generated: {by: process:create-pmos, at: "2026-10-06T14:43:28Z"}
+generated: {by: process:create-pmos, at: "2026-10-06T15:12:25Z"}
 status: stable
 ---
 

package/payload/scripts/delivery-index.js

@@ -5,7 +5,7 @@
  *
  *   const D = require('./delivery-index');
  *   const idx = D.deliveryIndex(root, ids);     // { ok, reason?, byBranch:Set, byMention:Set }
- *   D.attribution(idx, id)                      // 'branch' | 'mention' | null | 'unknown'
+ *   D.attribution(idx, id)                      // 'branch' | 'mention' | 'change' | null | 'unknown'
  *   D.isDeliveryPath('workspace/server.js')     // true — a build path, not planning prose
  *
  * WHY THIS EXISTS. This derivation shipped inside `workspace/server.js` as a module-private
@@ -101,13 +101,13 @@ const deliveryCache = new Map();      // root -> { head, index }
  *                                any commit subject into a delivery claim
  * @returns {{ok:boolean, reason?:string, byBranch:Set<string>, byMention:Set<string>}}
  */
-function deliveryIndex(root, ids) {
+function deliveryIndex(root, ids, opts) {
   const t = trunkRef(root);
   if (!t) {
     return {
       ok: false,
       reason: 'no trunk branch (main/master) is reachable from this repository — delivery cannot be derived',
-      byBranch: new Set(), byMention: new Set(),
+      byBranch: new Set(), byMention: new Set(), byChange: new Set(),
     };
   }
   const hit = deliveryCache.get(root);
@@ -119,7 +119,7 @@ function deliveryIndex(root, ids) {
     return {
       ok: false,
       reason: `git could not read the history at ${t.ref}${r.err ? ` — ${r.err}` : ''}`,
-      byBranch: new Set(), byMention: new Set(),
+      byBranch: new Set(), byMention: new Set(), byChange: new Set(),
     };
   }
   const byBranch = new Set();
@@ -137,11 +137,87 @@ function deliveryIndex(root, ids) {
     // the safe direction and the one the surface already errs in.
     for (const id of known) if (id.length > 3 && msg.includes(id)) byMention.add(id);
   }
-  const index = { ok: true, byBranch, byMention };
+  // 3. THE CHANGE THAT CARRIED THE SPEC (scan-consistency R1). See changeSignal below.
+  const byChange = changeSignal(root, t.head, known, opts);
+  const index = { ok: true, byBranch, byMention, byChange };
   deliveryCache.set(root, { head: t.head, index });
   return index;
 }
 
+/*
+ * THE THIRD SIGNAL — a change on the trunk that touched this initiative's OWN documents and build
+ * paths together (scan-consistency R1).
+ *
+ * Signals 1 and 2 both need the id spelled in a commit message. On this repository most pull
+ * requests ship on `claude/<slug>-<suffix>` branches and their commits name the area (`feat(workspace):
+ * …`), not the id, so 102 of 283 initiatives read `build pending` although their PRD, record and code
+ * merged in one pull request. The tie is concrete and git holds it: the pull request that changed
+ * `planning/initiatives/<id>.md` (or the PRD the record names) ALSO changed build files.
+ *
+ * A UNIT is one first-parent commit of the trunk: a merge commit (its diff against the first parent
+ * is the whole pull request), a squash merge, or a direct commit. Two guards keep it from becoming a
+ * similarity score:
+ *   · the unit must change at least one build path (isDeliveryPath) — a docs-only pull request
+ *     delivers nothing;
+ *   · the unit may touch the documents of at most MAX_CO_INITIATIVES initiatives. A sweep that edits
+ *     forty records while changing a script is evidence for none of them.
+ * A merged branch whose name, less its random suffix, IS a known id (`claude/jira-wbs-kpamaz`) counts
+ * too, when its pull request changed build paths.
+ */
+const MAX_CO_INITIATIVES = 2;
+const RECORD_DIRS = ['planning/initiatives', 'pmos/state/initiatives', 'state/initiatives'];
+/** { [repo-relative path]: Set<id> } — each record and every `*_path` its frontmatter names. */
+function documentOwners(root, ids, recordsDir) {
+  const fs = require('fs');
+  const path = require('path');
+  const dirs = recordsDir ? [recordsDir] : RECORD_DIRS.map((d) => path.join(root, d));
+  const owners = new Map();
+  const add = (rel, id) => {
+    const k = String(rel || '').trim().replace(/^["']|["']$/g, '').replace(/^\.?\//, '');
+    if (!k || /\s/.test(k) || k.includes('..')) return;
+    if (!owners.has(k)) owners.set(k, new Set());
+    owners.get(k).add(id);
+  };
+  for (const id of ids) {
+    for (const dir of dirs) {
+      const file = path.join(dir, id + '.md');
+      let text;
+      try { text = fs.readFileSync(file, 'utf8'); } catch { continue; }
+      add(path.relative(root, file).split(path.sep).join('/'), id);
+      const fm = /^---\r?\n([\s\S]*?)\r?\n---/.exec(text);
+      if (fm) for (const m of fm[1].matchAll(/^[a-z_]*_path[ \t]*:[ \t]*(\S.*?)[ \t]*$/gm)) add(m[1], id);
+      break;
+    }
+  }
+  return owners;
+}
+function changeSignal(root, head, known, opts) {
+  const out = new Set();
+  if (!known.length) return out;
+  const owners = documentOwners(root, known, opts && opts.recordsDir);
+  const ids = new Set(known);
+  const r = gitCap(root, ['log', '--first-parent', '--diff-merges=first-parent', '--format=%x1e%s%x1f', '--name-only', head]);
+  if (!r.ok) return out;
+  for (const chunk of r.out.split('\x1e')) {
+    if (!chunk.trim()) continue;
+    const cut = chunk.indexOf('\x1f');
+    const subject = cut < 0 ? chunk : chunk.slice(0, cut);
+    const files = cut < 0 ? [] : chunk.slice(cut + 1).split('\n').map((s) => s.trim()).filter(Boolean);
+    if (!files.some(isDeliveryPath)) continue;
+    const touched = new Set();
+    for (const f of files) for (const id of owners.get(f) || []) touched.add(id);
+    if (touched.size && touched.size <= MAX_CO_INITIATIVES) for (const id of touched) out.add(id);
+    const b = /^Merge (?:pull request #\d+ from|branch ')\s*(?:[^/\s]+\/)?(?:claude|feature|feat|fix|chore)\/([A-Za-z0-9][\w.-]*?)'?(?:\s|$)/.exec(subject.trim());
+    if (b) {
+      const slug = b[1];
+      const bare = slug.replace(/-[a-z0-9]{4,8}$/, '');
+      if (ids.has(slug)) out.add(slug);
+      else if (bare !== slug && ids.has(bare)) out.add(bare);
+    }
+  }
+  return out;
+}
+
 /*
  * The branches that actually MERGED — a strictly narrower signal than `byBranch`, and the two are
  * kept apart on purpose.
@@ -251,12 +327,13 @@ function declaredDelivery(root, declared) {
  * caller that collapses the two reports "nothing was delivered" for a repository whose history it
  * failed to read, which is a claim the missing evidence cannot support.
  *
- * @returns {'branch'|'mention'|'unknown'|null}
+ * @returns {'branch'|'mention'|'change'|'unknown'|null}
  */
 function attribution(index, id) {
   if (!index || !index.ok) return 'unknown';
   if (index.byBranch.has(id)) return 'branch';
   if (index.byMention.has(id)) return 'mention';
+  if (index.byChange && index.byChange.has(id)) return 'change';
   return null;
 }
 
@@ -264,6 +341,7 @@ function attribution(index, id) {
 function attributionEvidence(signal, id, extra) {
   if (signal === 'branch') return `an initiative/${id} branch merged to the trunk`;
   if (signal === 'mention') return 'a commit on the trunk names this initiative and changes build files';
+  if (signal === 'change') return 'a change merged to the trunk carried this initiative\'s own documents and build files together';
   if (signal === 'declared') return `delivered_by ${String(extra || '').slice(0, 8)} — verified on the trunk, and it changes build paths`;
   if (signal === 'unknown') return 'the trunk history could not be read — delivery cannot be derived here';
   return 'no commit on the trunk is attributable to this initiative';
@@ -274,5 +352,5 @@ function _resetCache() { deliveryCache.clear(); }
 
 module.exports = {
   deliveryIndex, attribution, attributionEvidence, declaredDelivery, mergedBranches,
-  isDeliveryPath, trunkRef, _resetCache,
+  isDeliveryPath, trunkRef, documentOwners, _resetCache,
 };

package/payload/scripts/workflow-state.js

@@ -438,7 +438,7 @@ function buildCommits(root, range, lane, opts) {
     if (declared && declared.declared && !declared.ok) {
       return { unknown: false, failedDeclaration: declared, first: null, count: 0, sample: null, signal: null, attributed: true };
     }
-    const index = (opts && opts.deliveryIndex) || delivery.deliveryIndex(root, listInitiatives(root));
+    const index = (opts && opts.deliveryIndex) || delivery.deliveryIndex(root, listInitiatives(root), { recordsDir: layout(root).initiatives });
     signal = delivery.attribution(index, id);
     if (declared && declared.ok) {
       // A verified declaration attributes the work regardless of what the conventions found. It is
@@ -478,7 +478,7 @@ function buildCommits(root, range, lane, opts) {
     count++;
     if (first === null) { first = i; sample = hit; }
   }
-  if (whole && id && signal === 'branch' && first === null) {
+  if (whole && id && (signal === 'branch' || signal === 'change') && first === null) {
     // The branch merged and every commit it carried was written on the branch, so no trunk commit
     // subject names the id. The merge itself is the evidence, and saying "0 commits" over a merged
     // branch would be the under-claim in a new place.
@@ -1657,7 +1657,7 @@ function main(argv) {
   // reason the commit range is: `deliveryIndex` memoises per trunk head, so a per-initiative build
   // would be cheap but the intent — one read, shared — is what keeps the rows consistent with each
   // other even if the trunk moved mid-run.
-  const deliveryIdx = delivery.deliveryIndex(root, ids);
+  const deliveryIdx = delivery.deliveryIndex(root, ids, { recordsDir: layout(root).initiatives });
   const rows = ids.map((i) => computeWorkflow(i, { root, range, changeRange, deliveryIndex: deliveryIdx }));
   if (json) { process.stdout.write(JSON.stringify(rows, null, 2) + '\n'); return 0; }
   if (!rows.length) { process.stdout.write('\n  no initiative records found — is this a PMOS repo?\n\n'); return 1; }

package/payload/state/discoveries.md

@@ -2,7 +2,7 @@
 type: Reference
 title: "Discoveries and friction log"
 description: "Append-only record of what runs discovered and where the process rubbed."
-generated: {by: process:create-pmos, at: "2026-10-06T14:43:28Z"}
+generated: {by: process:create-pmos, at: "2026-10-06T15:12:25Z"}
 status: stable
 ---
 

package/workspace/fixtures/initiatives-api/sheet.json

@@ -54,27 +54,32 @@
     {
       "id": "intake",
       "label": "Intake",
-      "state": "done"
+      "state": "done",
+      "owed": null
     },
     {
       "id": "spec",
       "label": "Spec",
-      "state": "done"
+      "state": "done",
+      "owed": null
     },
     {
       "id": "build",
       "label": "Build",
-      "state": "current"
+      "state": "current",
+      "owed": null
     },
     {
       "id": "evaluate",
       "label": "Evaluate",
-      "state": "todo"
+      "state": "todo",
+      "owed": null
     },
     {
       "id": "accept",
       "label": "Accept",
-      "state": "todo"
+      "state": "todo",
+      "owed": null
     }
   ],
   "waiting": {
@@ -90,14 +95,31 @@
     {
       "kind": "prd",
       "label": "PRD",
-      "path": "planning/prd/partner-sso.md"
+      "path": "planning/prd/partner-sso.md",
+      "source": "record"
     },
     {
       "kind": "rubric",
       "label": "Rubric",
-      "path": "planning/evals/partner-sso.md"
+      "path": "planning/evals/partner-sso.md",
+      "source": "record"
+    },
+    {
+      "kind": "explainer",
+      "label": "Explainer",
+      "path": "planning/explainers/partner-sso-surface-explainer.md",
+      "source": "knowledge-graph",
+      "shared": false
+    },
+    {
+      "kind": "code",
+      "label": "Code",
+      "path": "workspace/lib/partner-sso.js",
+      "source": "git",
+      "commits": 2
     }
   ],
+  "derived": null,
   "history": [
     {
       "at": "2026-10-04T09:00:00Z",

package/workspace/guide/index.md

@@ -13,15 +13,15 @@ This guide describes the PMOS workspace as it works today. It ships with the app
 On a desktop the workspace is one frame. [Layout](layout.md) explains each part.
 
 1. **The top bar.** Repository ▾, the five places (Docs included), search (⌘K), Sync when the repository is not in sync, and Settings.
-2. **The place.** One of Today, Initiatives, Board or Reports, or Docs (⌘K or `g d`). It fills the screen under the bar.
+2. **The place.** One of Agenda, Initiatives, Board or Reports, or Docs (⌘K or `g d`). It fills the screen under the bar.
 3. **The detail.** The item you opened: an initiative with its status, next steps and artifacts, or the profiles. It opens beside the place and closes with ×.
-4. **The agent dock.** Terminals, documents, conversations and web pages. It is open on Today and a thin rail elsewhere.
+4. **The agent dock.** Terminals, documents, conversations and web pages. It is open on Agenda and a thin rail elsewhere.
 
 ## Where things are
 
 | You want | Go to |
 |---|---|
-| What is waiting for you now | Today |
+| What is waiting for you now | Agenda |
 | The initiatives of a repository, or of every repository | Initiatives. Choose **All repositories** in Repository ▾ for every repository. |
 | The sessions of a repository, by initiative | The agent dock. ⌘K → **Branches and sessions** lists the branches. |
 | The items of an initiative | Board, or Breakdown in the initiative detail |

package/workspace/guide/initiatives-screen.md

@@ -2,7 +2,7 @@
 type: Guide
 title: "Initiatives: the Roadmap, the List and the initiative sheet"
 description: "How to read and order the initiatives of a repository on the Roadmap and the List, open the initiative sheet, make a new initiative, and review the cycle."
-timestamp: 2026-10-05
+timestamp: 2026-10-06
 ---
 
 # Initiatives: the Roadmap, the List and the initiative sheet
@@ -11,6 +11,12 @@ The Initiatives place shows every initiative of the selected repository. Each in
 
 Press **Roadmap** or **List** at the top to change the view. The workspace keeps your choice in this browser.
 
+### Re-scan
+
+The workspace reads the stage, the files and the breakdown of each initiative from the repository. It reads them again when an initiative record changes, and at the latest after ten minutes. A change that does not touch a record, for example a pull request merged on the trunk, can show late.
+
+To read the repository again now, use **Re-scan the repository**. It is in the **⋯** menu of an initiative sheet, and in the command menu (⌘K). A toast shows **Re-scanning…**, and another shows the time when the read ends. Then the view updates. Re-scan writes nothing. It works the same on PMOS itself and on a tenant repository.
+
 ## The Roadmap
 
 The Roadmap has three columns: Now, Next and Later. Each column is a ranked list of cards. The line at the top reads, for example, "Now · 5 KR · 3 health". It counts the initiatives in Now by what they serve: a key result (KR) or a health budget. When the rules set an advisory cap for Now, the line shows it. The cap only advises. It never stops a move.
@@ -56,6 +62,24 @@ From the top:
 
 An initiative that is finished reads "Accepted". An initiative on hold, closed or cancelled reads that word instead of a stage. After 5 days with no activity, the line adds "idle 5 d".
 
+### How the stage is read
+
+The stage is the first stage with an open step at or after the furthest stage that has evidence. Work that went past a step, for example a build that merged before a contract was logged, is not held at the earlier stage. The earlier stage shows a warning mark, and its tooltip names the step that is still open, for example "Skipped: contract is still open". An accepted initiative has no current stage.
+
+The build counts as done when the trunk holds evidence for this initiative: a merged `initiative/<id>` branch, a commit that names the id and changes build files, or a merged change that changed this initiative's own documents (its record, or a file the record names) and build files together. A change that touched the documents of more than two initiatives is not evidence for any of them.
+
+### The Files tab
+
+The Files tab lists every file that belongs to the initiative, in three groups:
+
+- **Named by the record.** The record, and each file its frontmatter names with a key that ends in `_path`: `prd_path`, `rubric_path`, `explainer_path`, `design_path` and others. A file the record names that does not exist is shown as missing.
+- **Linked documents.** The documents the library joins to the initiative: a document that declares its `initiative_id`, a document the record names, a file name that starts with the id.
+- **Changed for it in git.** The files that the commits for this initiative changed and that still exist. These are its own branch, trunk commits that name the id, and merged changes that carried its documents. The file opens read-only.
+
+### A breakdown read from the spec
+
+When nobody has planned items for an initiative, the Breakdown tab shows the items of its spec above the empty Breakdown: the user stories, or the entries of the Requirements section of the PRD that the record names. Each item shows the state of the whole initiative: **Done** after you accept it, **Built** when its build is on the trunk, and **Todo** before that. These items are read-only and nothing is written. To track an item, add it to the Breakdown. The card and the row show the same count, for example "0 of 8 · from board-delivery-truth-prd.md".
+
 The More button in the sheet has:
 
 - **Move to Now**, **Move to Next**, **Move to Later**.

package/workspace/guide/layout.md

@@ -15,7 +15,7 @@ The top bar has these parts, from left to right:
 
 - **Repository ▾** names the current repository. Press it to choose another repository, or **All repositories** to see the work of every repository at once. All repositories replaces the old Portfolio mode.
 - **Branches and sessions** is in ⌘K. It opens a sheet with every branch of the repository (main first) and how many sessions run in each. Press a branch to see its sessions, open one, end one, or start a session there. **＋ branch** makes a branch, and **＋ session** starts one with a branch, an agent and a profile. With All repositories, the sheet lists every repository.
-- **Today, Initiatives, Board, Reports and Docs** are the five places. Press one to show it. The Today count shows how many items need you. Docs shows whether each document is the same as its Google Docs and Confluence copy.
+- **Agenda, Initiatives, Board, Reports and Docs** are the five places. Press one to show it. The Agenda count shows how many items need you. Docs shows whether each document is the same as its Google Docs and Confluence copy.
 - **Search or capture ⌘K** opens the command palette. Type to find an initiative, a repository, an open tab or a command.
 - **Sync** shows only when the current repository is not in sync with its remote. Press it to fetch, bring in the work of the other machine, record your changes and push. If the repository has not fetched in the last 10 minutes, Sync also shows, because a push from another machine is not visible until a fetch. When the repository fetched recently and is in sync, Sync is not shown. If Sync stops, the message names the step that stopped.
 - **Sync on its own.** If you forget to press Sync, the workspace syncs for you. It syncs each repository once when the workspace starts. It also syncs a repository that has records not yet pushed when no record changed for 5 minutes. In a document repository it syncs every changed file on any branch. In a code repository it syncs only on the default branch (for example `main`), and only when every commit not yet pushed changes records and no code. If you close the tab while records are not yet pushed, the browser asks you first. To turn automatic sync off, start the workspace with `PMOS_AUTO_SYNC=0`.
@@ -37,11 +37,11 @@ Settings holds settings only, in seven sections:
   - **Update the kit** does what `npx create-pmos@latest --update` does in a terminal. It changes only the kit's own files under `pmos/` (skills, scripts, templates and guides). Your records in `state/`, `planning/` and `okf/product/` do not change. The last lines of the output show under the button. The changed files are under `pmos/`, which Sync treats as records, so Sync (or automatic sync) sends them with your other records. To read them first, look at `git diff pmos/` before you sync.
   - **Update the workspace** does what `pmos upgrade` does in a terminal. It asks you first. The workspace stops, installs the new version and starts again, and the page reloads when the new version starts. Sessions keep running in tmux. Press it on the computer that runs the workspace. From a phone it is refused, because the phone cannot see the restart through. When the workspace runs from a PMOS checkout, update it with `git pull` instead.
 
-Your work is never in Settings. It is in Today, Initiatives, Board and Reports.
+Your work is never in Settings. It is in Agenda, Initiatives, Board and Reports.
 
 ## The agent dock
 
-The dock holds your terminals, documents, conversations, skills and web pages. It is open on Today. On every other place it is a 44-pixel rail at the right edge.
+The dock holds your terminals, documents, conversations, skills and web pages. It is open on Agenda. On every other place it is a 44-pixel rail at the right edge.
 
 - Press ⌘J (Ctrl-J), or the button on the rail, to open the dock. Press ⌘J again, or the fold button in the dock, to fold it to the rail.
 - The dock never opens by itself. A tab that opens while the dock is a rail waits in the dock until you open it.
@@ -67,13 +67,13 @@ When the workspace needs an answer from you, for example the name for a rename o
 
 ## Colour and size
 
-The workspace is neutral. A primary button is the text colour on the page colour, in both themes. The one brand colour marks the Today dot and the Today count, and nothing else. The bar, the dock and the bottom bar follow the theme; only a terminal stays dark. Corners are square. Controls are icons from one set, not text symbols. On a touch screen every field is 16 pixels, so the phone does not zoom when you tap it, and every control is at least 44 pixels high.
+The workspace is neutral. A primary button is the text colour on the page colour, in both themes. The one brand colour marks the Agenda dot and the Agenda count, and nothing else. The bar, the dock and the bottom bar follow the theme; only a terminal stays dark. Corners are square. Controls are icons from one set, not text symbols. On a touch screen every field is 16 pixels, so the phone does not zoom when you tap it, and every control is at least 44 pixels high.
 
 ## Keys
 
 | Key | What it does |
 |---|---|
-| g t, g i, g b, g r, g d | Show Today, Initiatives, Board, Reports or Docs. |
+| g t, g i, g b, g r, g d | Show Agenda, Initiatives, Board, Reports or Docs. |
 | ⌘K (Ctrl-K) | Open or close the command palette. |
 | ⌘J (Ctrl-J) | Open or fold the dock. |
 | ⌘⇧J (Ctrl-Shift-J) | Focus: give the dock the whole window, or show the place again. |
@@ -89,7 +89,7 @@ A key that you type in a field, or in a terminal, goes to the field or the termi
 
 ## On a phone
 
-A phone shows one panel at a time. The tabs at the bottom are **Today, Initiatives, Board, Reports and Agent**. Agent shows the dock, with your terminals. Search or capture ⌘K is pinned at the top of Today.
+A phone shows one panel at a time. The tabs at the bottom are **Agenda, Initiatives, Board, Reports and Agent**. Agent shows the dock, with your terminals. Search or capture ⌘K is pinned at the top of Agenda.
 
 The bar at the top has Back (when you are deeper than a tab), Repository, the name of the screen, ⌘K, Sync (when the repository is not in sync, or has not fetched in the last 10 minutes) and Settings. Settings opens over the current tab. Back returns to the tab.
 

package/workspace/guide/proactive-engine.md

@@ -180,6 +180,7 @@ Text that you type in a setting (the name, the stalled days, the quiet hours) or
 - `pmos proactive settings` shows the settings. Add `--enabled`, `--trigger NAME=on|off`, `--stalled-days`, `--quiet HH:MM-HH:MM|none`, `--pause-learning`, `--background-prepare on|off`, `--brief-source NAME=on|off`, `--scope SERVICE:NAME=watch|search|ignore`, `--day-check 30|60|off`, `--website URL`, `--no-website URL`, `--brief-scoring on|off` or `--name` to change one.
 - `pmos proactive goals` lists today's goals with their steps. `pmos proactive goals add TEXT [--initiative ID]` adds one. `done N`, `drop N`, `reopen N` and `remove N` change the Nth goal. `pmos proactive goals plan` does the same as **Prepare my day**.
 - `pmos proactive brief` shows today's brief. `pmos proactive brief submit --file PATH` submits one. `pmos proactive brief submit --file PATH --merge` merges one into the stored brief of the same day. `pmos proactive brief schedule` makes the 06:45 schedule for the current repository.
+- `pmos proactive calendar` shows what the calendar memory holds (the number of events, the days it covers and when it was read) and the window the next morning brief reads: 90 days back and 31 ahead when the memory is empty or older than 7 days, else from today to 31 days ahead. It only reads.
 - `pmos proactive day` shows the stage of the day and its tasks. `pmos proactive day show TASK` prints one task with its item, its draft and the notes of each revision. Sessions read it.
 - `pmos proactive day deliver TASK --summary TEXT --body-file PATH [--link URL]` delivers the draft of a working task. `pmos proactive day sent TASK [--link URL]` reports that the approved step was done. `pmos proactive day fail TASK --reason TEXT` reports that a task cannot be done. Sessions run these three.
 - `pmos proactive day approve TASK`, `pmos proactive day revise TASK --note TEXT` and `pmos proactive day retry TASK` are your decisions, the same as the buttons. `pmos proactive day check` starts a check now.

package/workspace/guide/today.md

@@ -1,7 +1,7 @@
 ---
 type: Guide
 title: "Today: what needs you"
-description: "The two-column day (your jobs and the agent's jobs), the eight kinds of card on Today, the one button on each card, the count, the empty state, and the pmos today command."
+description: "The Agenda month and the calendar it remembers, the two-column day (your jobs and the agent's jobs), the eight kinds of card on Today, the one button on each card, the count, the empty state, and the pmos today command."
 timestamp: 2026-10-06
 ---
 
@@ -32,6 +32,28 @@ Each job session is named "Job ·" and the first words of the job, so the sessio
 
 **Agent results**, at the top of the left column, counts the jobs and lists each finished one with its draft summary or the reason it failed. Your goals for today come under it, above the calendar. The other things that wait for you, such as outcome checks, report drafts and sessions, are in **Also waiting for you** at the end of the left column. When the day is folded, they show under it.
 
+### The Agenda month
+
+The menu calls this page **Agenda**. At the top of the left column is the month, with today marked. Each week starts with its number, for example W41.
+
+- Press a day to see its agenda under the month. Three tiles open the agenda: the time in meetings, the meeting that matters most, and your prep.
+- Press a week number to see the agenda of that week, day by day.
+- Press a meeting to see its memory in the right column. The month marks every day of the same meeting, so you see when it happens again.
+
+Meetings that repeat and have nothing for you fold into one line, for example "+4 repeating, nothing for you". Press it to see them.
+
+Each day of the month answers three questions:
+
+- **How full is the day?** The bar covers 09:00 to 18:00. Each block is a meeting. A dark block is an important meeting.
+- **What matters?** The ★ line names the one meeting of the day that matters. A meeting matters when you present or decide, when people from outside the company or leadership join, or when 8 people or more join. A meeting whose prep is at risk also shows.
+- **How ready are you?** The badge shows the prep steps done out of the steps needed, for example 1/3. It is red when the free time before the meeting is shorter than 30 minutes for each step left. A past day shows how many one-to-ones and important meetings have no notes.
+
+The switch above the month shows one answer at a time: **Overview** (all three), **Full** (the time in meetings), **Key** (the meeting that matters), **Prep** (how ready you are) or **Free** (the free blocks of 90 minutes or more).
+
+The memory of a meeting says what kind of meeting it is (one-to-one, onboarding or group), how many times it was held, how many are to come, and why it matters. **Before this meeting** lists the prep. **Last time** is folded: open it to read the notes and what stayed open.
+
+The month comes from the calendar memory. The morning-brief session reads your calendar 90 days back and 31 days ahead the first time, and from today to 31 days ahead after that, and sends it with the brief. The workspace keeps 100 days back and 45 days ahead, in `calendar-memory.json` in the state folder. Nothing on the Agenda writes to your calendar. To see what the memory holds, run `pmos proactive calendar`.
+
 ### One day for every repository
 
 The day is yours, not a repository's. Every repository shows the same calendar, goals, jobs and mentions. To narrow the day, use the **Show** switch at the top of Today: