create-pmos 0.516.0 → 0.517.0

package/workspace/guide/live-notes.md

@@ -1,21 +1,19 @@
 ---
 type: Guide
-title: "Guide: live notes"
+title: "Live notes: talking points and the check by Jev"
 description: "How the Live notes view listens to a meeting, turns what is said into talking points, and lets you confirm each one, with an optional check by Jev."
-timestamp: 2026-10-04
+timestamp: 2026-11-03
 ---
 
 # Guide: live notes
 
+
 The Live notes view takes notes during a meeting. Each thing that is said becomes a talking point. The workspace guesses which open initiative the point is about. You confirm the guess, change it or reject it, one card at a time. Nothing changes an initiative until you confirm.
 
-## Open the view
+## Where it is
 
-1. Select the repository in the navigation column.
-2. Press ⌘K, type **live notes** and press Enter. The view opens as a tab for that repository.
-3. Press **New session**. A session is one meeting.
+The workspace has no screen for live notes today. The console had one, and it was removed. The routes stay, and the rules on this page still decide what a live-notes session does and what goes to Jev. To take notes in a meeting now, see [Notes](notes.md).
 
-If the repository has more than 255 open initiatives, the view asks you to select an anchor first. The session then uses only the initiatives of that anchor.
 
 ## Add talking points
 

package/workspace/guide/my-work.md

@@ -1,24 +1,17 @@
 ---
 type: Guide
-title: "My work: every Jira ticket and WBS item assigned to you, ranked, briefed to an agent, approved in Agenda"
-timestamp: 2026-10-13
+title: "My work: the Jira tickets and tasks assigned to you"
+description: "Where the work assigned to you shows in Home, where the items come from, how they are ordered, and the pmos my-work commands."
+timestamp: 2026-11-03
 ---
 
-# My work
+# My work: the Jira tickets and tasks assigned to you
 
-Open My work from the top bar, from ⌘K (**My work**), or press `g w`.
-
-My work lists every Jira ticket and every breakdown (WBS) item assigned to you, in all your registered repositories. It ranks them, shows what each one asks, and lets you give an agent an instruction for it. The agent's draft then waits for you in Agenda.
-
-## The screen
-
-The page has the same layout as Agenda. The title says how many items wait for a brief. At the right of the title, four buttons switch the list: **To brief**, **Agents**, **Ready** and **All**, each with its count. A strip below the title shows when Jira was last read and how many tickets and plan items the read holds. **Read again** is at the right of the strip.
-
-Two cards fill the rest of the page. The left card lists the items. Each row has a dot for its tier (red for P1, amber for P2, grey for the rest). A badge shows when the item is due, and a **Decision** badge marks an item that looks like a decision only you can make. The right card, **Brief**, shows the open item. On a phone, the two cards stack.
+There is no My work page. Home's list is your list. A task sits under its initiative, and your own items sit under **Not in an initiative**. Press a row to open the item's card in the Viewer: its due day, where it came from, **Keep for later**, the agent on the item (draft, stop, try again, send back) and **Done**. [Home](home.md) explains the list.
 
 ## Where the items come from
 
-- **Jira tickets.** The workspace does not read Jira. The **my-work-read** skill reads it in an agent session, with your own Atlassian connection. It reads the open issues assigned to you, with their comments and links, and writes a context card for each: who asked, what they ask, a short summary of the thread, the questions still open, and a suggested instruction for an agent. It does not copy the comments. Press **Read again** in My work to run it.
+- **Jira tickets.** The workspace does not read Jira. The **my-work-read** skill reads it in an agent session, with your own Atlassian connection. It reads the open issues assigned to you, with their comments and links, and writes a context card for each: who asked, what they ask, a short summary of the thread, the questions still open, and a suggested instruction for an agent. It does not copy the comments. It runs with the other reads of your tools.
 - **WBS items.** The plan items whose owner is you, in every registered repository. They come from the same data as the Board's Mine filter. My work changes no plan item.
 
 The read is kept in your own runtime folder on this machine. It never goes into a repository.
@@ -34,30 +27,7 @@ Each item gets a WSJF score: the cost of waiting divided by the size.
 | Unblocks | 3 for each item it blocks, at most 9. |
 | Size | XS 1, S 2, M 3, L 5, XL 8. No estimate counts as M. |
 
-The score is (value + urgency + unblocks) / size. P1 is 12 or more, P2 is 7 or more, P3 is 3 or more, and P4 is the rest. Open **Details** on an item to see each part.
-
-## Brief an agent
-
-Being assigned a ticket does not mean an agent must resolve it. Every new item starts in **To brief**.
-
-1. Open the item. Read **What the agent found**.
-2. Change the instruction. It starts as the agent's suggestion.
-3. Press **Run agent**. Or press **I'll handle it** to keep the item yourself.
-
-Run agent adds one job to today's day run, with your instruction. The job runs like every Agenda job: at most 5 at once, one draft, and nothing is sent. The **Decision** badge marks an item that looks like a decision only you can make. An agent can still prepare it.
-
-**Back to brief** returns an item to To brief, unless an agent is working on it.
-
-## Approve in Agenda
-
-When the draft is ready, the item moves to **Ready** in My work, and the job waits in Agenda. Approve, revise or retry it there. My work has no approve button.
-
-Agenda shows one card, **N items need your brief**, when items wait in To brief. Its button opens My work. The morning brief lists today's top items from My work and does not brief them for you.
-
-## What My work does not do
-
-- It does not write to Jira.
-- It does not open a pull request. A job drafts a reply, a comment, a plan or a document.
+The score is (value + urgency + unblocks) / size. P1 is 12 or more, P2 is 7 or more, P3 is 3 or more, and P4 is the rest. 
 
 ## Commands
 
@@ -67,138 +37,4 @@ Agenda shows one card, **N items need your brief**, when items wait in To brief.
 | `pmos my-work show <ITEM> [--json]` | One item: what the agent found, the score and the state. ITEM is its key, its id or its number in the list. |
 | `pmos my-work submit --file <read.json>` | The my-work-read skill submits its read. |
 
-None of these briefs an agent or takes an item. Do that in My work.
-
-## The Work page: your work in seven views
-
-The Work page holds all the work that is yours:
-
-- the items you add for yourself, such as "send Dana the new date";
-- every open Jira ticket and WBS item assigned to you, from the same read as My work;
-- the items today's morning brief suggests for you. They are flagged, so they are in Today.
-
-A row of assigned work shows its Jira key (a link to the ticket) or **WBS** and the repository. When the read has a suggestion, the first chip on the row shows **Agent can:** and the suggestion. This chip is only a suggestion. No agent works on the item until you start it. A suggested row shows **Suggested** and the reason. An agent at work on a ticket puts it in Waiting; a ticket in progress, or with a draft ready for you, is flagged. A ticket that is done in Jira leaves the page.
-
-Every action works on these rows. The first action writes the item to your own list, with its source. **Drop** takes it off your Work page only; Jira and the Board keep it, and it does not come back.
-
-The server decides where each item shows, so one item is never in two views.
-
-The seven views follow the OmniFocus style. The **Work** tab badge counts Inbox plus Today.
-
-| View | What it holds |
-|---|---|
-| Inbox | Items with no date, not yet decided. Give each one a date, a defer date or a job, mark it waiting, move it to Someday, or drop it. |
-| Today | Items due today or overdue, and every flagged item. Overdue items come first, then flagged items, then the rest by due date. |
-| Upcoming | Items that arrive in the future. A later due date or a defer date puts an item here. The next 7 days are grouped by day, then **Later**. |
-| Waiting | Items where you wait for someone. The item that has waited longest comes first. |
-| Someday | Items you parked. They do not appear anywhere else. |
-| Review | Items in Inbox, Someday or Waiting that nobody touched for 7 days. The most stale item comes first. |
-| Done | Items you marked done in the last 30 days, newest first. Each one shows the outcome and how it closed. |
-
-An item goes to the first view that fits these rules, in this order. Parked is Someday. Waiting on someone is Waiting. A defer date after today is Upcoming. Flagged is Today. Due today or earlier is Today. A later due date is Upcoming. An undated item whose defer date has arrived is Today. No date is Inbox.
-
-### Let the agent draft an item
-
-Open an item that shows **Agent can:**. The case file shows **What the agent will do**.
-
-The offer is on Jira and WBS items with a suggestion, and on each item the morning brief suggests for you (for example a Slack reply or an email), also on the days after, while you keep the item in Work. On a brief item the offer is the reply or the note that the item asks for, and the draft goes back to the place the item came from, only when you post it.
-
-An item you added yourself shows **Agent can draft a first version**. The agent drafts what the item asks for (a document, a plan or a recommendation), and the draft stays on the item. It has no place to post to: read it, keep it, or send it back with a note.
-
-1. To change the instruction, select **Change what the agent does** and type a new one.
-2. Select **Let the agent draft this** and hold to confirm. This adds one job to today's day run, with the instruction.
-
-The row chip then shows the agent's state:
-
-| Chip | What it means |
-|---|---|
-| **Agent: queued** | The job waits for a free place in the day run. |
-| **Agent: working** | An agent session drafts the item. Select **stop** in the case file to end it. |
-| **Agent: draft ready** | The draft waits for you. |
-| **Agent: posting** | You approved the draft. A session posts exactly that text. |
-| **Posted to** the item | The draft went out. Select **Open what was posted** to see it. |
-| **Agent: needs you** | The agent asked you something, or waits for your OK to run a step, in its session. The case file gives the question. Select **Open the session** and answer it there: the job carries on. |
-| **Agent stopped** | The job failed or you stopped it. The case file gives the reason. Select **Try again** to run it again. |
-
-The page reads the state again every 15 seconds while an agent is queued, working or posting.
-
-When the draft is ready, the case file shows it as a document card, with its headings, lists and tables. Select **Open** to read it in the document sheet, the same sheet as your other documents: **Read** (with a box under the draft to write to the agent), **Edit**, **Proposals** (the same box) and **Edit log** (the conversation with the agent). Select **Copy** to copy the text.
-
-Under the draft is the conversation with the agent: your ask, each draft, each note you sent back and each edit. Select **View round** on an earlier draft to read that version. The conversation stays on the item on the next days too.
-
-To ask the agent for changes, type in the box under the conversation and press Enter or select **Send to the agent**. Shift+Enter adds a line. The agent drafts it again, and the draft and the conversation stay on the item while it works. You can send a draft back as many times as you want.
-
-Or choose one option:
-
-- **Post it to** the ticket posts the exact text. Nothing goes out until you hold to confirm.
-- **Edit the draft** opens the draft in the document sheet's editor. Select **Save**. The card then says **Edited by you**, and **Post it to** the ticket posts exactly your text.
-- **Keep it as a draft** leaves the draft as it is.
-- **Mark it done** closes the item. Nothing is posted.
-
-Some work needs an action in another system, for example creating an exploration in GA4. The agent does not try that action while it drafts. The draft names the action as its step, and the card shows **Step when you approve**. Then the first option is **Do it**, in place of **Post it to**, also on an item you added. Hold to confirm. A new job session starts with Claude in Chrome and permission to use the browser tools only, does that one step, and reports what it made. Chrome must be open with the Claude extension, and you must be signed in to the system.
-
-The agent only drafts. It never posts to Jira or acts in another system until you approve the draft.
-
-### Defer and flag
-
-A defer date means "not before this day". The item stays in Upcoming and shows **Not before** with the date. On that day it moves to Today by itself. A due date is when the work must be done. A defer date is when you start.
-
-Flag an item to put it in Today now, whatever its date. Remove the flag to send it back.
-
-### Focus
-
-Focus sits at the top of Today. PMOS suggests up to three jobs for the day and gives the reason for each, for example "2 items overdue, 1 flagged".
-
-PMOS groups the Today items by their job. An item with no job is its own group. It ranks a group by how late its items are, and by whether they are due today, flagged, P1 or work outside PMOS. It uses rules only and calls no model.
-
-For each suggestion, you accept it, change it or reject it. An accepted job stays at the top of Today for the day. A rejected job does not come back that day. Focus starts empty each new day.
-
-### Work outside PMOS
-
-Some items are not done in PMOS, such as "talk to Ana" or "set up a meeting with Raj". Mark these as offline work and name the person. An offline item offers three actions:
-
-- **Done.** Add a one-line outcome if you want to keep it.
-- **Not yet.** Choose later today, tomorrow or next week. Tomorrow and next week set a defer date, and the item returns to Today on that day. Next week means the next Monday. Later today reminds you in 3 hours.
-- **Drop.**
-
-An offline item can carry evidence that it is done. PMOS looks at your calendar and your notes for the person on the item. It uses a meeting that has ended and names the person, or a note that is not private and names the person, and that is newer than the item. The row then says **Looks done?**, gives the meeting or note title and its day, and shows a **Confirm** button. PMOS never reads a private note and never marks an item done by itself. You press Confirm.
-
-### Review
-
-Review is a weekly pass. It shows one item at a time. Press **Keep** to leave the item as it is and clear it from the queue for 7 days. Press **Change** to edit it. Press **Drop** to remove it. Any change to an item also clears it from the queue.
-
-### Done
-
-Done lists the items you marked done in the last 30 days, in four cards: **Today**, **Yesterday**, **Earlier this week** and **Earlier, last 30 days**. Each row shows the outcome you wrote, when the item was done, and how it closed: you marked it done, you closed it from the agent draft, the agent posted it, the agent did the step you approved, or you confirmed it. Press **Reopen** to put the item back in its view. The badge on Done counts the items done today. Older items stay in their job's sheet.
-
-### Link to a team task
-
-A Work item can link to the plan item it advances. The link shows on the item with the title of the plan item. Closing the plan item is a separate step, in the initiative.
-
-### Where decisions go
-
-A decision or an approval only you can make is not a Work item. It shows in Briefing, under **Needs you**.
-
-## Using the Work page
-
-The Work page in the console has seven views: **Inbox**, **Today**, **Upcoming**, **Waiting**, **Someday**, **Review** and **Done**. Each view button shows how many items it holds. The Done button shows how many items you finished today.
-
-Each item is in one view only. The rule, in order: an item in Someday stays in Someday. An item that waits on a person is in Waiting. An item with a Not before date after today is in Upcoming. A flagged item is in Today. An item due today or earlier is in Today. An item due later is in Upcoming. An item with no date is in Inbox.
-
-Decisions are not on the Work page. They have their own place in the console.
-
-The right column of every view shows **Focus: jobs to be done**. Focus suggests up to 3 jobs, each with the reason. Select **Accept** to pin one, **Edit** to change its title, **Not today** to remove the suggestion, or **Unpin** to take a pinned job back. The line under Focus says how many you marked not today, with **Bring back**. Select a Focus row, or its job chip, to open the job's sheet, where you edit or delete the job. The **+** button in the Focus header opens a sheet to create a job.
-
-**Today** has three cards: **Overdue**, **Due today** and **Flagged**. Each row has a **Done** check. In **Inbox**, **Decide** opens the row. In **Waiting**, **Nudge** drafts a nudge and sends nothing. The **Review** view also holds the agent's drafts, which Briefing used to show.
-
-**Upcoming** shows a **Next 7 days** card with one heading for each day, then a **Later** card.
-
-**Review** shows the items in Inbox, Waiting and Someday that nobody changed for 7 days or more, one at a time, the oldest first. For each item, select **Keep**, **Change** or **Drop**. When no items remain, the view shows **Review done**.
-
-Open an item to use these actions: **Flag**, **Not before** (a date), **Someday** or **Bring back**, **Waiting** (a name) or **Stop waiting**, **Done** and **Drop**.
-
-An item marked **outside PMOS** is work you do yourself, for example a talk with a person. It shows the person's name. Write the result in one line and select **Done**, or select **Not yet** and then **Later today**, **Tomorrow** or **Next week**. The item shows how many times you moved it. When PMOS finds evidence that the work is done, the item shows **Looks done?** and the evidence. Select **Confirm** to close it.
-
-Each action shows **Undo** for a short time.
-
-When you type a new line, the chip below the box tells you the view where the line will go.
+None of these briefs an agent or takes an item. Do that from the item's card in Home.

package/workspace/guide/notes.md

@@ -7,22 +7,16 @@ timestamp: 2026-11-03
 
 # Guide: notes
 
-**Notes** is a page in the top bar, between Docs and People. The list on the left shows every note by initiative, with the time or day and an amber dot when a note conflicts with a file. The note you pick opens on the right. That column is the full note: there is no second, pop-up version of it. It has the title with its icons, the meeting context, the conflicts, the highlights, the overview, the decisions, the next steps (each with a **Make task** icon), the open questions and a **Discussion** fold with the topics and the transcript. Press the title, the overview or any decision, next step or question to edit it. PMOS keeps the words the agent wrote.
+A note is what PMOS keeps from one meeting: your typed lines, the transcript, the decisions, next steps and questions it caught, and the final notes it writes after Stop. There is no Notes page any more. A note opens in the Viewer, from the meeting in Your day or the calendar in Home, and the meeting records in its own browser tab, the recording tab.
 
-Every button in the top bar and in the note is an icon. Hold the pointer on an icon to read its name.
+Every button in the recording tab and in the note is an icon. Hold the pointer on an icon to read its name.
 
-## The Record control
+## Start recording
 
-The Record control is at the right of the top bar. It has two groups, always in the same place.
+- **A meeting on your calendar.** Open it from Your day or the calendar in Home, and press **Record** in its card in the Viewer. The note is linked to the event and keeps its context.
+- **No meeting on the calendar.** Press **+** at the top of Home's list, then **Recording**. PMOS starts an untitled note.
 
-- **The meeting group** shows only while a meeting is recording or paused. It starts with the meeting's name and its clock (paused: **paused · 48 min left**). Press the name to open the note. While recording, the group has a highlighter icon, **Pause** and **Stop**. While paused, it has **Resume** and **Stop**. When there is nothing to resume, the group is not there.
-- **The new group** is the red microphone with a plus, and an arrow. The microphone starts an untitled note and listens at once. The arrow lists the meetings of today that have not ended and have no note, soonest first. These are the meetings the Calendar shows, including the ones you imported in Settings. A meeting that has started stays in the list until 10 minutes after it ends, so you can still record it. It shows "Now · started 5 min ago", or "Ended 3 min ago" in those last 10 minutes. **Next** marks the first meeting that has not started. Each shows who is coming and how many agenda items it has. Press one to start a note for that meeting, with its context. Both are unavailable while a meeting is recording. Pause or stop it first.
-
-Starting a note, from the Record control or from **Take notes** on a calendar event, shows the Notes page with that note.
-
-### The Record control in the console
-
-The console (the page at `/`) has the same Record control in its top bar, beside the Sessions button. It is always there, also when nothing is recording. **Record** (the microphone) starts an untitled note and listens at once. The arrow lists the meetings of today that have not ended, including one that has started, until 10 minutes after its end. Press one to start a note linked to that calendar event. While a meeting records, the red group shows its name and clock, **Highlight**, **Pause** and **Stop**. While it is paused, the group shows **Resume** and **Stop**. **Stop** asks first and offers **Pause instead**. A red dot shows on the Calendar tab while a meeting is held. Press the name in the red group to open the note on the console's Calendar tab, in **Notes**, on the **During** stage. See [the Calendar tab of the console page](console-calendar.md).
+Either way PMOS opens the recording tab, or brings it forward when it is already open, and starts to listen. The tab's bar has **Highlight the last 30 seconds**, **Pause** and **Stop** while it records, and **Resume** and **Stop** while it is paused. With a shared screen it also has the eye icon that pauses the screenshots.
 
 When Whisper or Qwen3-ASR transcribes the meeting, the red group also names the engine and the language, for example **Whisper · English**. Check it when lines come out in the wrong language: the language is set in the Notes settings.
 
@@ -42,7 +36,7 @@ The live transcript keeps each sentence once:
 
 ## Pause, resume and stop
 
-**Pause** keeps the meeting open. PMOS stops listening and the clock stops. It does not ask, and it does not write the final notes yet. You can resume for one hour. The top bar shows the minutes left. After an hour the meeting ends by itself, and PMOS writes its final notes.
+**Pause** keeps the meeting open. PMOS stops listening and the clock stops. It does not ask, and it does not write the final notes yet. You can resume for one hour. The recording tab shows the minutes left. After an hour the meeting ends by itself, and PMOS writes its final notes.
 
 **Resume** continues the most recent paused meeting, in the same note, with the clock where it stopped. It is not available for a meeting that was stopped, for one that ran out of its hour, or for an older meeting after a later one was recorded. Its tooltip says why.
 
@@ -79,7 +73,7 @@ If you close the recording tab, the browser asks first. If you leave, the meetin
 
 ## While the meeting is held
 
-While a meeting is recording or paused, the note shows a live block under the context: the status, **Your notes** (type a line and press Enter) and the live transcript. The block stays steady while it listens. New lines are added at the end. Your place, the line you are typing and its cursor do not move. If the transcript is scrolled to its end, it follows the new lines. The note shows **Stop** while recording, and **Resume** and **Stop** while paused. **Highlight** and **Pause** are in the top bar only.
+While a meeting is recording or paused, the note shows a live block under the context: the status, **Your notes** (type a line and press Enter) and the live transcript. The block stays steady while it listens. New lines are added at the end. Your place, the line you are typing and its cursor do not move. If the transcript is scrolled to its end, it follows the new lines. The note shows **Stop** while recording, and **Resume** and **Stop** while paused. **Highlight** and **Pause** are in the recording tab's bar only.
 
 ## The meeting context
 
@@ -100,10 +94,10 @@ The Notes view shows one meeting, top to bottom. A bar at the top shows whether
 
 ## Start a meeting
 
-1. Press **Record** in the top bar, or press **Notes** to see all notes (or press ⌘K, type **notes** and press Enter). The page is the same in every repository.
+1. Start recording, as in **Start recording** above.
 2. Type a title. A note made with **Record** has none until you add one.
 3. Under **Your notes**, type a note and press Enter. Each note is its own line, with the meeting time you added it at. To remove a line, press the **x** beside it. Each line also shows in the transcript as **You, typed** and is labelled like a spoken line, so a decision or a next step you type goes into its section. Your notes steer the summary, and they save at once.
-4. Press **All notes** to open an earlier note. The **⋯** menu has Copy as Markdown, New meeting, the meeting and the initiative, Summary by agent, Mark private, Settings and **Delete note**.
+4. To open an earlier note, open its meeting in Home. The note's **⋯** menu has Copy as Markdown, New meeting, the meeting and the initiative, Summary by agent, Mark private, Settings and **Delete note**.
 
 ## Listen
 
@@ -304,7 +298,7 @@ When you press **Listen**, a sheet asks **Where is the meeting?** The choice is
 
 - **Zoom app** or **Another app**: the browser asks twice. The first share is **Entire screen** with system audio; PMOS uses its sound only, never its picture. Then a second sheet asks you to **Pick the meeting window**; the shots come from that window only, and it stays captured while you work in other apps. Press **Sound only, no shots** to skip the second share.
 - **Google Meet in Chrome**: one share of the Meet tab, with its sound, gives the sound and the shots.
-- **Pause shots**: the chip next to **REC** in Focus, and the eye icon on the recording chip in the top bar, stop the pictures and keep the sound. Press it again to take shots again.
+- **Pause shots**: the chip next to **REC** in Focus, and the eye icon in the recording tab's bar, stop the pictures and keep the sound. Press it again to take shots again.
 - **Set aside.** If the picture is the whole screen and tesseract is on this machine, PMOS reads each shot. A shot whose text looks like another app (Slack or a mailbox, for example) and not like the call is set aside: it is not in the note, the replay or anything the agent reads. The note shows **N set aside**. Press it to **Keep it**, **Delete** or **Delete all**. Set-aside shots are deleted on their own after 7 days. Without tesseract, every shot is kept.
 
 To stop taking screenshots, clear **Capture the shared screen** in the settings. The sound of the shared screen is still used. To stop sharing only the picture during a meeting, stop the share in the browser's sharing bar; the screenshots stop. To delete one note's screenshots, press **Delete this note's screenshots** in the settings, or **Delete screenshots** in the note's **More** menu. The notes, the transcript and the audio stay. Deleting a note, or marking it private, deletes its screenshots.
@@ -330,7 +324,7 @@ Claude reads the text of the latest screenshots of the shared screen, if your ma
 
 ## Capture highlights during the meeting
 
-While listening, press the highlighter in the top bar to capture the last 30 seconds of conversation. A pop-up opens just below the Record control and shows the highlight's progress. Its icons keep the highlight, discard it, or close the pop-up (the highlight keeps working):
+While listening, press the star (**Highlight the last 30 seconds**) in the recording tab's bar to capture the last 30 seconds of conversation. A pop-up shows the highlight's progress. Its icons keep the highlight, discard it, or close the pop-up (the highlight keeps working):
 
 1. **Capturing**: the last 30 seconds are being recorded.
 2. **Listening**: the highlight listens forward. Choose how long: **30 seconds**, **1 minute** or **2 minutes**. The remaining time counts down.
@@ -370,7 +364,7 @@ Under the title, a note shows two lines: **Meeting** and **Initiative**.
 
 When a note has no initiative, the summary suggests one: the open initiative that shares 3 or more words with what was said, when no other initiative shares as many. A suggestion never replaces an initiative you chose.
 
-To take notes for a calendar event, open the event's detail on the Agenda and press **Take notes**. PMOS starts to listen at once, to your microphone and to the meeting when local transcription is set up. Pick the meeting's tab or window when the browser asks. Let people know that you are taking notes. The note is linked to the event, and to the event's initiative when it has one. It keeps the event's context. The Notes page shows the note, and the top bar shows the meeting's name and clock on every page. One note is taken at a time: pause or stop the one that listens before you start another. An event that already has a note shows its summary and **Open notes**, which shows the note in Notes. See [Today](today.md) and [the initiative sheet](initiatives-screen.md).
+To take notes for a calendar event, open the meeting from Your day or the calendar in Home, and press **Record** in its card in the Viewer. To record with no event, press **+** at the top of Home's list, then **Recording**. PMOS starts to listen at once, to your microphone and to the meeting when local transcription is set up. Pick the meeting's tab or window when the browser asks. Let people know that you are taking notes. The note is linked to the event, and to the event's initiative when it has one. It keeps the event's context. One note is taken at a time: pause or stop the one that listens before you start another. A meeting that already has a note opens its summary and the note.
 
 ## Dictate into your notes
 
@@ -383,8 +377,7 @@ To take notes for a calendar event, open the event's detail on the Agenda and pr
 - **Copy as Markdown** puts the title, the summary, your notes, the caught items and the transcript on the clipboard.
 - In the settings, **Mark private** stops listening at once and deletes the note's audio. A private note is not recorded again, and nothing from it goes to Jev or to an agent. **Mark not private** undoes it.
 - **Summary by agent** starts an agent session in the selected repository that writes a summary into the note. Lines that look like a secret are removed first.
-- **Delete note** in the **⋯** menu, or **Delete** on a row of **All notes**, removes the note, its transcript, its summaries and its audio from this machine after you confirm. The note's summary goes from the calendar and the initiative. You cannot undo it. Deleting a note that is not being taken does not stop the one that is.
-- On the console3 page, open the note in **Calendar › Notes** and press the bin next to **Copy as Markdown** in its head. PMOS asks first: **Delete note** deletes it, **Keep it** keeps it. A note that is being recorded stops without keeping its audio, then it is deleted. The next note in the list opens.
+- **Delete note** in the **⋯** menu removes the note, its transcript, its summaries and its audio from this machine after you confirm. The note's summary goes from the calendar and the initiative. You cannot undo it. Deleting a note that is not being taken does not stop the one that is.
 
 ## What stays on your machine
 

package/workspace/guide/people.md

@@ -1,16 +1,15 @@
 ---
 type: Guide
-title: "People: the people you work with in a repository, their interactions, tone, notes and shared work"
-timestamp: 2026-10-07
+title: "People: the people you work with"
+description: "How PMOS keeps the people you work with in a repository, where they come from, where it keeps the records, and the pmos people commands."
+timestamp: 2026-11-03
 ---
 
-# People
+# People: the people you work with
 
-Open People from the top bar, from ⌘K (**People**), or press `g p`.
+PMOS keeps a list of the people you work with in each repository: who they are, your interactions with them, the tone of those interactions, your own notes and the work you share. The workspace has no People page. When you correct a line of meeting notes, PMOS offers names from this list. An agent reads it with `pmos people`.
 
-People lists the people you work with in the current repository. For each person it shows who they are, your interactions with them and where each one came from, the tone of those interactions, your own notes, and the work you share.
-
-## How people get into People
+## How a person gets onto the list
 
 People adds every person it finds. It reads the names the workspace already holds for the repository each time you open People:
 
@@ -30,38 +29,6 @@ Each record is a sighting: a name, a handle (a mail address, a chat or Jira name
 
 A sighting of a new handle adds the person. A sighting with the full name of a person in People joins that person. A first name alone, from a speaker or a name, joins the one person with that first name. When two people have that first name, it joins neither of them.
 
-## Waiting for you
-
-- **A possible duplicate.** When a session thinks two handles are one person, it says why. Press **Merge** to join the handle to that person, or **Keep separate** to close the question.
-- **Tones to confirm.** The count of people whose tone you have not confirmed. Open the person to confirm it.
-
-## The list
-
-People has the same two-card layout as the Agenda. The title says how many people there are. **All**, **Team** and **External** at the top right filter the list. The left card holds the list. Type in **Find a person** to search names, handles and initiatives. **Latest**, **Most** and **Name** sort it by the last interaction, the number of interactions or the name. Each row shows initials, the name, the role and organisation, and the tone as a coloured dot (a ? means you have not confirmed it). Press a person to open their page in the right card. Each card scrolls by itself, and the search box keeps its cursor while you type.
-
-## A person's page
-
-The top of the page shows the person's name and role, a **Confirm** button when a tone is waiting, and a **⋯** menu. Three tiles under it give the number of interactions, the tone and the shared work.
-
-- **Interactions.** Newest first. A meeting that comes up again is one line that says how often it happens (One-off, Daily, Weekly or Monthly meeting), how many times, and when it was last. A meeting the Agenda marks as key shows a **Key** label. Each other line shows the date, the kind (Mail, Chat, Meeting, 1:1, Jira, Doc, Call or Mention), the line, and where it came from with its pointer and tone.
-- **Tone.** The mix of tones (warm, neutral, cautious, tense) and a proposed overall tone: the most frequent tone of the latest 10 interactions. When two tones are tied, the latest one wins. Press **Confirm** (at the top or here) to keep the proposal, **Set another** to choose a different tone, or **Change** to clear your choice. Tone describes the exchanges, not the person.
-- **Shared work.** The initiatives your interactions name, the plan items the person owns (with **Blocked** when the item is blocked), and the coming meetings that name them when calendar names are on. Nothing here is typed by hand.
-- **Notes.** Type a note and press the **+** button (**Add note**). Press the **×** next to a note to remove it. Only you can add or remove a note. No command writes one.
-- **Identity and sources.** The person's handles, how many interactions each source gave, where People found them, and the file the person lives in.
-- **Remove from People.** In the **⋯** menu. Takes the person out. Later sightings of their handles stay out.
-
-## Ways in from other places
-
-- **Agenda.** A meeting's detail shows a link for each person its attendee line names.
-- **Initiative sheet.** The **People** tab lists the people whose interactions name the initiative or who own one of its items.
-- **Item sheet.** When an item's owner is a person in People, the owner is a link to their page.
-
-A link matches a full name, a first name of three letters or more, or a handle, as a whole word. Two people with the same first name both match.
-
-## Settings
-
-Settings has a **People** section for the current repository. **Keep attendee names from the calendar** is off until you turn it on. While it is off, the morning brief records nobody from the calendar, `pmos people record` refuses calendar sightings, and names recorded before stay hidden.
-
 ## Where People keeps its records
 
 People keeps one append-only file, `people.jsonl`, in the repository's state directory (`pmos/state/` in a product repository). Sync sends it with your other records, so People is the same on every machine that syncs the repository. Every clone of the repository can read your tone choices and notes. Keep them to work context.

package/workspace/guide/report-design.md

@@ -72,10 +72,10 @@ The top of the page shows one chip for each cycle. The current cycle is blue. Un
 - Move the pointer onto a value to show its detail.
 - Click a number or a status to show where it comes from.
 - Click a part that has more to show it.
-- Click an initiative to open it in Initiatives.
+- Click an initiative to open it.
 - Press **Show what changed** to mark the values that changed since the last cycle. The value of the last cycle shows next to each one.
 
-The deck shows in a frame that cannot run scripts. The console adds each of these actions.
+The deck shows in a frame that cannot run scripts. The Viewer adds each of these actions.
 
 ### When a draft differs from the design
 

package/workspace/guide/report-structure.md

@@ -88,4 +88,4 @@ Then press **Design how it looks** to do step 2.
 
 Nothing is sent from Structure.
 
-See also [Design how a report looks](report-design.md), [Set up a report by asking](reports-set-up.md) and [Reports: dashboards of reports](reports-dashboards.md).
+See also [Design how a report looks](report-design.md), [Set up a report by asking](reports-set-up.md) and [Ready-made dashboards and reports](ready-made-dashboards.md).

package/workspace/guide/reports-set-up.md

@@ -9,7 +9,7 @@ timestamp: 2026-10-15
 
 Many PMs send the same report again and again, for example an update for a standing meeting. PMOS can draft that report on its day. You read it, change it and issue it. PMOS drafts only. It never sends a report.
 
-Open the **Reports** tab of the console. It has four parts: Ask PMOS, Found in your work, Set up and Documents.
+Ask for the report in the chat on Home, for example "Set up my TSC update every month". Claude answers with the report, and its card opens in the Viewer, where you set it up, pick its schedule and format, and read each draft. The steps below are the same.
 
 ## Ask PMOS
 
@@ -25,19 +25,19 @@ If PMOS finds no earlier copy, the proposal says so and works from your words on
 
 ## Found in your work
 
-PMOS looks for reports that you send already. It reads your calendar, Slack, Drive and the subjects of mail you sent. It never reads a message body. Each finding says why PMOS thinks it is a report, shows the evidence, and says **Likely** or **Not sure**.
+PMOS looks for reports that you send already, and shows them in Intelligence under **Found in your work**. It reads your calendar, Slack, Drive and the subjects of mail you sent. It never reads a message body. Each finding says why PMOS thinks it is a report, shows the evidence, and says **Likely** or **Not sure**.
 
 For each finding you can:
 
-- Press **Set up** to accept the proposal as it is.
-- Press **Change first** to open the proposal and change it.
+- Press **Set it up** to accept the proposal as it is.
+- Press the finding's name to read what PMOS found before you set it up.
 - Press **Not a report**. The finding goes away at once, and PMOS says it will not suggest it again. Press **Undo** in the next five seconds to bring it back. After five seconds the choice is saved.
 
-The most likely finding also shows on the Briefing as **Report found**. Press **See what PMOS found** to open it on the Reports tab. Turn the finder off, or change its sources, in [Settings](settings.md), under Connectors.
+The most likely finding can also show on Home, with **Set up** and **Not a report**.
 
-## Set up and Documents
+## Your reports
 
-**Set up** has one row for each report: its source, output, schedule, next draft and last issue. Each row has these buttons:
+Intelligence lists every report you set up, with its next draft and its status. Open one to see it in the Viewer. Its actions are:
 
 - **Open** opens the current draft.
 - **Draft it now** shows in place of Open when the report has no draft. PMOS writes the draft of the next cycle and opens it.
@@ -48,10 +48,9 @@ The most likely finding also shows on the Briefing as **Report found**. Press **
 - **All cycles** lists every cycle of the report.
 - **Pause** stops the drafts. **Resume** starts them again.
 - **Shape the report** opens the Structure step of the report studio. There you decide what the report answers, where each number comes from and how it is worked out. See [Shape what a report says](report-structure.md). **Shape it with PMOS** on an answer sets the report up and opens the same step.
-- **Shape the report** opens the Structure step of the report studio. There you decide what the report answers, where each number comes from and how it is worked out. See [Shape what a report says](report-structure.md). **Shape it with PMOS** on an answer sets the report up and opens the same step.
 - **Design how it looks** opens the design studio. There you design how the report looks, as a deck or a document. See [Design how a report looks](report-design.md).
 
-**Documents** has one row for each cycle: Draft or Issued, the output, the copy state and who made it. Filter by state or by source. Press **Open** to read a document in the [document sheet](document-sheet.md).
+Each cycle is a document: Draft or Issued, with its output, its copy state and who made it. **All cycles** lists them.
 
 ## What PMOS does and does not do
 
@@ -62,4 +61,4 @@ The most likely finding also shows on the Briefing as **Report found**. Press **
 
 ## Send a dashboard as a report
 
-To make a report from a dashboard, use **Send this as a report…** on the dashboard. See [Reports: dashboards of reports](reports-dashboards.md).
+Every program, product and initiative also has a ready-made dashboard and reports. See [Ready-made dashboards and reports](ready-made-dashboards.md).

package/workspace/guide/reports.md

@@ -9,6 +9,22 @@ timestamp: 2026-11-02
 
 A cadence report tells its readers where each initiative stands. The biweekly report is the first one. The `pmos report` command drafts a report, issues it and lists the reports. It reads files in the repository only. It sends nothing and it fetches nothing.
 
+## The report engine
+
+Every new report is written by the report engine: one path for any report, ad hoc or recurring, in any domain. There is no fixed frame. The steps are brief, read, find, answer and render.
+
+1. `pmos report make <id>` writes the brief: who reads the report, their question, the window, the sources by name, the last issue, the outline the readers agreed and the asks carried over. It reads every source PMOS reaches and finds what changed. For an ad hoc report add `--ask "<the question>"`. Name a source with `--source`: `connector:<name>=<what it is>`, `document:<path>`, `pack:<file of readings>` or `pmos`.
+2. `pmos report read <id> --from <file>` files the readings the writer read through a connector or a document. Each reading has a source of the brief, a date and how it was read. A source that nothing read is a gap, and the report names it.
+3. `pmos report find <id> --from <file>` files the findings that answer the question. Each cites its readings. When there is no finding, there is no draft: nothing to report this cycle.
+4. The writer (the report-write skill) chooses the outline for these readers and writes `<slot>.report.json`. Every figure is a reading token, for example `{{r:web-login-rate}}`.
+5. `pmos report write <id> --from <file>` checks it and renders `<slot>.md`. The reader's slides, the PDF and the PowerPoint file are drawn from the same model, in the report's saved look.
+
+The checks come first on substance: there is an answer with a reading in it; each question is answered or named as a gap; every figure is a reading with its source and date; what moved since the last issue; the ask names who and by, or the options; each part beyond the ask cites a reading. A report with no answer, or with a figure that is not a reading, is refused. Then the form checks run.
+
+`pmos report check <id>` shows the checks of the last write. `pmos report rule <id> add wording "<rule>"` keeps a wording rule for every next issue; `pmos report rule <id> add off <part>` turns a part beyond the ask off; `pmos report rule <id> remove <n>` removes a rule.
+
+The sections below describe the older drafter, which the engine replaces for new reports.
+
 ## What a draft contains
 
 The script `pmos report draft` writes every number. No model runs. It reads the ledgers since the last issued report of the same cadence. If no report is issued yet, it reads the last 14 days (`report_cycle_days` in `planning/plan-rules.json`).
@@ -86,4 +102,4 @@ An initiative in the report lane completes its last step when you issue its repo
 
 ## Reports of your own
 
-The cadence report is the report that PMOS defines. For a report that you send already, such as an update for a standing meeting, use the Reports tab of the console. Describe the report, or let the report finder find it. See [Set up a report by asking](reports-set-up.md).
+The cadence report is the report that PMOS defines. For a report that you send already, such as an update for a standing meeting, ask for it in the chat on Home. Describe the report, and Claude sets it up. See [Set up a report by asking](reports-set-up.md).