create-pmos 0.133.0 → 0.135.0

package/workspace/guide/console-calendar.md

@@ -1,13 +1,13 @@
 ---
 type: Guide
 title: "Guide: the Calendar tab of the console page"
-description: "The Calendar tab of the console page (/c3.html): the five zooms, the layer chips, the markers, the context of a meeting, free time and the empty states."
+description: "The Calendar tab of the console page (/c3.html): the five zooms, the layer chips, the markers, the context of a meeting, free time, the tidy-up suggestions and the empty states."
 timestamp: 2026-10-11
 ---
 
 # Guide: the Calendar tab of the console page
 
-The Calendar tab of the console page (`/c3.html`) shows time. It shows what happens and what falls due, by date. It shows no card deck, no task list and no strategy panel. Your due items live in Work. The strategy and progress panels live in Reports and Initiatives.
+The Calendar tab of the console page (`/c3.html`) shows time. It shows what happens and what falls due, by date. At the top it shows a short deck of headline cards about your calendar, for example a conflict or a meeting with no time to prepare. The deck shows nothing when PMOS has no card about your calendar. The tab shows no task list and no strategy panel. Your due items live in Work. The strategy and progress panels live in Reports and Initiatives.
 
 ## Zoom and move
 
@@ -26,26 +26,29 @@ The chips under the zoom bar are the layers. Each chip shows the number of items
 | Releases | The release dates. |
 | Report dates | The dates on which a report goes out. |
 | My due items | The due dates of your own items, as markers. |
-| Free time | The free blocks of your working day. This chip is off at the start. |
+| Free time | The free blocks of your working day. The chip shows the number of blocks in the range. |
+| Tidy-up | The suggestions to tidy up the calendar of the range. This chip is off at the start. |
 
-All layers are on at the start, except Free time.
+All layers and Free time are on at the start. Tidy-up is off.
 
 ## The grid
 
 - **Day** shows the timeline of the day. The markers of the day are in a strip above it.
-- **Week** shows a timeline for each day. The markers of each day are in a strip under the day name. Press a day name to open that day.
-- **Month** shows a cell for each day. A cell shows the number of meetings and up to three markers. "+2" means two more markers. Press the day number to open the day.
-- **Quarter** shows a row for each week. **Year** shows a card for each month. Each shows the number of meetings and dated items, and the most important markers.
+- **Week** shows a timeline for each day. Each day name has the hours of meetings of that day and a small bar. The bar has three parts: time tied to a promise or a decision, routine time, and the rest of a 6 hour day. The markers of each day are in a strip under the day name. Press a day name to open that day.
+- **Month** shows a cell for each day. A cell shows the number of meetings and up to three markers. "+2" is a button. It opens the day with the other markers. Press the day number to open the day.
+- **Quarter** shows a row for each week. **Year** shows a card for each month. Each shows the number of meetings and dated items, and the most important markers. A "+N" button opens the week or the month that holds the rest.
 
 A marker has a symbol and a short title. A red edge means late or at risk of missing. An amber edge means at risk.
 
+A meeting is blue when it is tied to a promise or a decision, and grey when it is routine. A red meeting is blocked: its prep waits on someone. A coming meeting with prep left ends its time line with "prep to do". A past meeting that PMOS holds a record for ends it with "held". A line under the grid explains the colours.
+
 ## Select a marker
 
-Press a marker to show its detail in the side column. The detail shows the title, the kind and the date. The link under it opens the item where it lives: an initiative opens in Initiatives, your item opens in Work, and a report opens in Reports. A marker has no action of its own. You act on the item in its home.
+Press a marker to show its detail in the side column. The detail shows the title, then a row with where the item lives, the kind, the date and its initiative. The link under it opens the item where it lives: an initiative opens in Initiatives, your item opens in Work, and a report opens in Reports. A marker has no action of its own. You act on the item in its home.
 
 ## Select a meeting
 
-Press a meeting to show its context in the side column. Each line has a link to its source.
+Press a meeting to show its context in the side column. Under the title, a row shows where the meeting lives, the people and the initiative. Each line has a link to its source.
 
 - For a past meeting, **What came out of it** lists the decisions and actions of its note. **What moved after it** lists the items that changed within 48 hours and refer to the meeting or its initiative.
 - For a coming meeting, **Prepared** lists what is ready, and **To prepare** lists what is still open.
@@ -54,12 +57,38 @@ When PMOS holds nothing for a meeting, the detail says so. It does not guess.
 
 ## Free time
 
-Press **Free time** to show the free blocks. A free block is 90 minutes or more inside your working hours. On Day and Week, each block is a hatched window on the timeline. On Month, each day shows the number of free blocks. The side column lists the blocks.
+Press **Free time** to show the free blocks. A free block is a gap inside your working hours that is long enough to use. On Day and Week, each block is a dashed purple window on the timeline, with its length, for example "1.5 h focus". The side column lists the blocks, up to 8, with the suggestion for each. On Month, Quarter and Year the list says that free time shows in the Day and Week views, and the chip still shows the number of blocks.
 
 Each block can have a suggested use, for example a prep step that is at risk or the top item due that week. When nothing fits, the block says "Free, nothing specific to suggest". A suggestion is only a proposal. PMOS writes nothing to your calendar.
 
+## Tidy-up
+
+Press **Tidy-up** to see what to change in the calendar of the range. The chip shows the number of suggestions. PMOS finds them with fixed rules. It does not use a model.
+
+| Rule | When PMOS raises it | Severity |
+|---|---|---|
+| Overlap | Two meetings with a time overlap. | Needs a fix |
+| No break | A meeting starts less than 10 minutes after the one before it ends, on the same day. | At risk |
+| Prep at risk | A coming meeting has prep steps left, and less than 30 minutes of free time remain before it for each step. | At risk |
+| Stopped initiative | A meeting is about an initiative that is done, parked, on hold, closed or cancelled. | At risk |
+| Review too early | A review, sync or checkpoint comes before a milestone or promised date of its initiative that is not done. | Worth a look |
+| Late initiative | A milestone or promised date in the range belongs to an initiative that is delayed, overdue or at risk. | Needs a fix when delayed or overdue, At risk when at risk |
+| Heavy day | A working day has more than 6 hours of meetings. | Worth a look |
+
+All-day events take no time, so the time rules do not use them.
+
+The side column lists the suggestions in three groups: **Needs a fix**, **At risk** and **Worth a look**. Each suggestion tells you why PMOS raised it and proposes one change, for example "Move Design sync to 10:30 or shorten Standup." The links under it open the items involved: a meeting link shows the meeting in the detail, and an initiative link opens the initiative in Initiatives.
+
+On Day and Week, each meeting that a suggestion names has a coloured ring. Red means Needs a fix. Amber means At risk.
+
+A suggestion is only a proposal. PMOS has no access to your calendar and changes nothing. You make the change in your calendar or where the item lives.
+
+When the range has no suggestion, the list says "Nothing to tidy in this range." When a rule cannot run, for example because no calendar is imported, the list names the rule under **Not checked** and tells you why. When the server sends no tidy-up list, the list says so.
+
 ## Empty states
 
 The **In this range** list in the side column names each layer with its count. When a layer is empty, it tells you why. For example, no calendar is cached yet, or the server sent no dated items. When the range has nothing at all, the grid says so.
 
 On a narrow screen the side column is under the grid. From 1100 pixels wide it is at the right.
+
+Each suggestion has two buttons. **Propose it** marks it as proposed and shows a note that nothing changed in your calendar. **Dismiss** hides it for the rest of the visit. Neither button changes your calendar or sends anything to anyone.

package/workspace/guide/index.md

@@ -69,3 +69,4 @@ On a desktop the workspace is one frame. [Layout](layout.md) explains each part.
 - [Integrated work](integrated-work.md): how `pmos verify-work` turns a merged commit into Done, and what "Done · your call · not merged" means.
 - [Report slides](report-slides.md): how the Reports page shows a report as the PM-OS biweekly slides, Present and Print / PDF, and how your notes become the words on the slides.
 - [Reports: dashboards of reports](reports-dashboards.md): the console Reports page, its dashboards at portfolio, board and initiative scope, how to edit and share one as a draft, and the Drafts tab.
+- [Settings in console3](settings.md): how to open Settings, what each section holds, the scope tags, the environment notes, and where the settings are kept.

package/workspace/guide/initiative-boards.md

@@ -0,0 +1,65 @@
+---
+type: Guide
+title: "Initiatives on the console: Portfolio, boards and workflows"
+description: "How to use the Initiatives tab of the console page (/c3.html): the Portfolio of boards, a board and its nine tabs, an initiative with its own workflow and stage records, and the Build and deliver setting."
+timestamp: 2026-10-11
+---
+
+# Initiatives on the console: Portfolio, boards and workflows
+
+The Initiatives tab of the console page (`/c3.html`) has these levels: **Portfolio** › **Board** › **Initiative** › **Epic** › **Item**. A breadcrumb at the top takes you back one level. The address bar keeps your place in the `init=` parameter, so a reload opens the same page.
+
+## Portfolio
+
+The Portfolio shows one row per board. A board is a product folder, for example IDPF. Each row shows:
+
+- the board name and its health: On track, Needs attention or Off track
+- the owner, and **Build and deliver** with the Jira project key, or "PMOS tasks only"
+- the initiatives per category: Discover, Plan, Do and Learn
+- the next release
+
+Under the rows are a timeline of all boards (board › initiative › epic) and the boards that have new asks. Press a board name to open the board. Press **New board** to add a board.
+
+## A board
+
+The tabs are **Summary**, **Initiatives**, **Triage**, **Backlog**, **Board**, **Timeline**, **Releases**, **Docs** and **Sprints**. A board with Build and deliver off has no Releases and no Sprints tab.
+
+- **Summary** shows the initiatives at a glance and one bar per category. Press a bar to open the Initiatives tab with that category.
+- **Initiatives** lists the initiatives of the board, 25 on each page. Use the saved views (Now and next, Mine, At risk, No owner, All), the filters and the sort. Press **Move** on a row to move the initiative to a stage of its own workflow.
+- **Triage** lists the new asks. Add an ask, then open it to see its draft. Press **Accept** to start an initiative. An initiative needs an anchor (a KR or a health budget). Press **Ask for more** to ask a question, or **Decline** and give a reason.
+- **Backlog**, **Board** and **Timeline** show the epics and items. Jira items and PMOS tasks are mixed. The **Initiative** and **Source** filters are the same on the three tabs.
+  - In Backlog, add a PMOS task to an initiative.
+  - In Board, drag a PMOS task to a column, or use its menu. A Jira item has a lock: change it in Jira.
+  - In Timeline, use **Week**, **Month** and **Quarter** to zoom, and drag the empty chart to pan. Drag a PMOS bar to reschedule the task, or focus the bar and press the Left or Right arrow key. The toast has **Undo**. A Jira bar is locked.
+- **Releases** shows the next release, the later ones and the past ones, with their scope initiatives.
+- **Docs** lists the documents of the board by initiative.
+- **Sprints** shows the Jira sprints and the sprint burndown. They are read-only.
+
+### Board settings
+
+Press the gear in the board header to open the board settings.
+
+- **Build and deliver**: turn it on to mirror a Jira project. Type the Jira project key. With it off, every item is a PMOS task and the Build workflows are not available.
+- **Workflows this board offers**: the templates that a new initiative on this board can use.
+- **Default for new initiatives and accepted asks**: the template that a new initiative or an accepted ask starts on.
+
+## An initiative
+
+Each initiative has its own workflow, picked from a template: for example Product, Quick fix, Research only, or Content and launch. The stepper shows the stages of that workflow. Press a stage to move the initiative there. The move is your decision, so nothing blocks it. An order rule shows as a warning chip, for example "Skipped Plan" or "No spec yet". Press **Workflow** to change the template or edit the stages. When you remove a stage that holds the initiative, the editor asks where it goes.
+
+Under the stepper are the tools of the current stage. **More tools** lists the tools of the other stages. The tabs are **Overview**, **Breakdown**, **Docs**, **Tickets**, **Timeline** and **History**.
+
+The **Overview** shows the stage records of the current stage:
+
+| Category | Records |
+|---|---|
+| Discover | Problem statement |
+| Plan | RICE score, with its rank on the board |
+| Do | Launch checklist, sprint burndown (from Jira, read-only) |
+| Learn | Kill conditions, learnings |
+
+A project workflow has the launch checklist and the learnings only. If the workspace server cannot store stage records yet, the cards say "Nothing recorded yet." and nothing is saved.
+
+## Demo mode
+
+Open `/c3.html?demo=1` to see five sample boards and about 310 initiatives. In demo mode nothing is saved, and a reload starts again.

package/workspace/guide/jira.md

@@ -2,7 +2,7 @@
 type: Guide
 title: "Jira: tickets drafted from the PRD, and their status"
 description: "How to draft Jira tickets from a PRD in your ticket template, push the ones that are ready, and see their status, sprint and progress on the initiative's Jira tickets tab."
-timestamp: 2026-10-06
+timestamp: 2026-10-11
 ---
 
 # Jira: tickets drafted from the PRD, and their status
@@ -95,6 +95,8 @@ The agent runs the **Push to Jira** skill. It reads what to send with `pmos jira
 
 Each row shows the ticket's status in Jira, and whether it is in the **Active sprint**, the **Next sprint** or the **Backlog**, with its subtasks done. A blocked ticket shows **Blocked** and the reason.
 
+The check also reads each ticket's story points, its resolution date, and the start and end dates of its sprint. The initiative's sprint burndown uses them. When the sprints have no dates or the tickets have no story points, the burndown is not shown. The burndown uses the tickets in the sprint at the time of the last check. It does not show scope that was added or removed during the sprint.
+
 The **Jira status check** reads this for every initiative. **Check now** on the tab reads it for one. To run it every day before the morning brief (06:45), schedule it at 06:30:
 
 ```

package/workspace/guide/layout.md

@@ -157,6 +157,8 @@ On an iPhone or an iPad, the terminal gets smaller when the keyboard opens, so t
 
 The address options `?layout=legacy` and `?fixture=cockpit` keep the older layouts. The rest of this page describes them. In the cockpit, the workspace has four columns: the repository rail, the list, the detail and the tabs. With `?layout=legacy` it has three columns: navigation, detail and tabs.
 
+In the older layout, each working tree of a repository has **＋ session here**. It starts a shell in that tree. If you press it while the page is still loading, the session starts when the terminal is ready.
+
 ### The repository rail, the list and the tools
 
 The rail is 64 pixels wide and shows one tile for each repository. A dot on a tile means that repository has something that needs you. The selected repository has no dot, because the list beside it shows what needs you. The `+` tile adds a repository. The rail has no tools menu: the repository list and Validate are in Settings, and everything else is in ⌘K.

package/workspace/guide/my-work.md

@@ -108,7 +108,7 @@ Some items are not done in PMOS, such as "talk to Ana" or "set up a meeting with
 - **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, for example a meeting that took place. The row then says **Looks done?** and shows a **Confirm** button. PMOS never marks an item done by itself. You press Confirm.
+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
 
@@ -130,9 +130,11 @@ Each item is in one view only. The rule, in order: an item in Someday stays in S
 
 Decisions are not on the Work page. They have their own place in the console.
 
-**Today** starts with a Focus band. It suggests up to 3 items. Select **Accept** to pin one, **Not today** to remove the suggestion, or **Unpin** to remove a pinned item. You can edit the title of a pinned item.
+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.
 
-**Upcoming** shows one block for each of the next 7 days, then **Later**.
+**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**.
 

package/workspace/guide/notes.md

@@ -1,8 +1,8 @@
 ---
 type: Guide
 title: "Guide: notes"
-description: "How to take notes in a meeting: one note top to bottom, typed notes as timed lines, key points written each minute and labelled by Jev, delete a note; final notes written after Stop from the whole recording, with speakers and a quote for each item, decisions with their why and who, next steps with an open question, a discussion paragraph, and Wispr Flow's notes merged in and fetched by hand when the fetch fails; listen to your microphone and the meeting on this machine, see decisions, actions and questions caught as they are said, check them against the repository for conflicts, capture highlights during the meeting, create tasks from next steps, correct and tag lines, see what changed in your notes, replay the meeting, link a note to its meeting and its initiative, and get a summary."
-timestamp: 2026-10-08
+description: "How to take notes in a meeting: one note top to bottom, typed notes as timed lines, key points written each minute and labelled by Jev, delete a note; final notes written after Stop from the whole recording, with speakers and a quote for each item, decisions with their why and who, next steps with an open question, a discussion paragraph, and Wispr Flow's notes merged in and fetched by hand when the fetch fails; listen to your microphone and the meeting on this machine, see decisions, actions and questions caught as they are said, check them against the repository for conflicts, capture highlights during the meeting, create tasks from next steps, correct and tag lines, see what changed in your notes, replay the meeting, see screenshots of the shared screen beside the transcript, link a note to its meeting and its initiative, and get a summary."
+timestamp: 2026-10-11
 ---
 
 # Guide: notes
@@ -20,6 +20,24 @@ The Record control is at the right of the top bar. It has two groups, always in
 
 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 `/c3.html`) 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 started. 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. The console has no Notes page, so the name in the red group opens the note in the main app.
+
+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.
+
+One meeting records in one tab at a time. If another tab or window already records the meeting, **Record** there says so and starts nothing.
+
+
+## What the live transcript leaves out
+
+The live transcript keeps each sentence once:
+
+- When the meeting plays on your speakers, your microphone hears the other people too. PMOS takes their words out of your microphone's line, and keeps the line from the meeting. Your own words stay.
+- A line that only repeats the line before it is left out. A sentence said twice in a row in one line is kept once.
+- If the meeting language is English (the default), a line that comes back in another language, for example Hindi, Indonesian or Chinese, is transcribed again in English. The first text stays with the line.
+- If the workspace restarts during a meeting, the recording continues where it was. Nothing is written twice.
+
 ## 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.
@@ -189,6 +207,21 @@ The workspace makes the copy from the replay only. It does not change the transc
 
 To stop keeping audio, clear **Keep the audio for replay** in the settings. To delete one note's audio, press **Delete this note's audio** in the settings; the notes and the transcript stay. The browser's own recognition keeps no audio, so a meeting heard that way cannot be replayed.
 
+## See the shared screen
+
+When you share the meeting's screen, the workspace also keeps screenshots of it, so the note shows what people saw. The browser's sharing window is your permission: the workspace takes no screenshot of a screen you did not share, and the browser shows that it is sharing for as long as you listen.
+
+- The workspace follows the meeting to choose when to keep a screenshot. It keeps one when the picture changes and then holds still, such as a new slide, a new window or the end of a scroll. A still screen keeps no new screenshot, and the frames of a transition are not kept.
+- When the picture keeps moving, such as a video or a demo, the workspace keeps one sample every 15 seconds while it moves, not every frame.
+- When someone says something about the screen, such as "as you can see" or "this slide", the workspace keeps the picture that was on the screen when the line was said. It does the same for a line that the workspace labels a decision or a next step, and when you press the highlighter.
+- Each screenshot says why it was kept, for example "Kept when the screen changed" or "Kept when someone said "this slide"". A picture that the last screenshot already shows is not kept again.
+- Each screenshot has the meeting time, the same clock as the transcript and the replay. Screenshots are kept on this machine with the note, outside every repository, and are never sent anywhere. A private note keeps none.
+- After **Stop**, the note shows **Screen** below the replay: one picture for each screenshot, with its time. Press a picture to see it large, with **Previous**, **Next** and **Play from here**. While the replay plays, the picture on the screen at that time is marked.
+- In the transcript, a line said while a new screenshot came up has a small picture beside it. Press it to see the screenshot.
+- When **tesseract** is on this machine, the workspace reads the text on each screenshot, on this machine, and shows it under the large picture. To install it, run `brew install tesseract` in a terminal.
+
+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.
+
 ## 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):

package/workspace/guide/reports-dashboards.md

@@ -1,7 +1,7 @@
 ---
 type: Guide
 title: "Reports: dashboards of reports"
-description: "How the console Reports page shows dashboards at portfolio, board and initiative scope, how to edit one, how to share one as a draft, and where the report drafts went."
+description: "How the console Reports page shows dashboards at portfolio, board and initiative scope, how to edit one, how to share one as a draft, how to put one on a schedule, and where the report drafts went."
 timestamp: 2026-10-11
 ---
 
@@ -13,7 +13,9 @@ A report answers one question. A dashboard is a set of reports for one scope. Op
 
 - **Dashboards.** The reports of one scope, drawn from the repository's records.
 - **Library.** Every report the workspace can draw, with the question it answers and where it is used.
-- **Drafts.** The four report families, the claims check and the outbox. They work as before.
+- **Drafts.** The dashboard drafts you made with Share, what the Briefing used to show below Needs you, and the report families. See "Drafts" below.
+
+The headline deck of the Reports page is above the tabs. It shows only report signals: claims that block sending, ticket keys in a leadership report, a digest that is due, and people who hold an old date. It never repeats the Briefing's cards. When there is no report signal, the deck says that nothing needs you. The scope buttons are on the same row as the tabs.
 
 ## Choose a scope
 
@@ -42,7 +44,7 @@ The Calendar page no longer carries these. They moved here.
 ## Edit a dashboard
 
 1. Press **Edit dashboard**.
-2. Use the arrows to move a report. Press **Remove** to take one off. The report stays in the library, and **Undo** brings it back.
+2. Use the arrows to move a report. Press the cross to take one off. The report stays in the library, and **Undo** brings it back.
 3. Choose a report under **Add from the report library**.
 4. Press **Done editing**.
 
@@ -52,6 +54,28 @@ The workspace keeps your layout for each scope in its runtime state. It does not
 
 Press **Share**. A sheet shows the dashboard as a report: a headline, one section per report, what needs your call, and the sources. Choose **Leadership** for one sentence per report. Choose **Team** to add the numbers behind each sentence.
 
-**Save as draft** puts one draft in the outbox. Nothing is sent. With no channel connected, the outbox says so.
+**Make a draft now** puts one draft in the outbox. Nothing is sent. With no channel connected, the outbox says so.
+
+## Put a dashboard on a schedule
+
+A schedule makes a ready draft of a dashboard and tells you on the bell. Nothing is sent. No sender channel is connected yet, so you send the draft yourself.
+
+1. Press **Share**.
+2. Choose the audience: **Leadership** or **Team**.
+3. Choose **Weekly, Mondays 08:00** or **Monthly, 1st at 08:00**. The sheet shows the next draft.
+4. Press **Save schedule**.
+
+The dashboard head then says "Scheduled: ..., draft only". To stop a schedule, choose **Not scheduled** and press **Save schedule**. A dashboard has one schedule. The times are the time on this computer.
+
+On each run, the workspace reads the dashboard as it is then, with your layout, and puts one draft in the outbox. The draft text is the same as the text **Make a draft now** makes. The bell shows "a scheduled draft is ready" for 7 days, or until you discard the draft. Press the notice to open **Drafts**.
+
+If the workspace is not running at the time, the run happens once when it starts again. It does not make one draft for each run it missed. If a run cannot read the dashboard, **Scheduled** shows why, and the next run tries again.
+
+## Drafts
+
+Open the **Drafts** tab. It has these parts, in order.
 
-Scheduled sending is not available yet. The schedule control is off, and the sheet says why.
+- **Drafts.** One row for each dashboard draft. A row says **Made by schedule** or **Made by you**. Press **Preview** to read the text. Press **Discard** to remove it from the list. **Undo** in the message brings it back. The log keeps the line.
+- **Scheduled.** One row for each schedule: the dashboard, how often, the audience and the next draft.
+- **Handled for you**, **What I could stop** and **Data you can lean on.** The Briefing used to show these. They come from the same briefing data. A card with no data does not show.
+- **Reports to send.** The four report families, the claims check and the outbox. They work as before.

package/workspace/guide/settings.md

@@ -0,0 +1,68 @@
+---
+type: Guide
+title: "Settings in console3: one home for each setting"
+description: "How to open Settings in console3, what each section holds, what the scope tags and the environment notes mean, and where the settings are kept."
+timestamp: 2026-10-11
+---
+
+# Settings in console3: one home for each setting
+
+Settings is the page in console3 (`/c3.html`) where you change how PMOS works. Each setting has one home on this page. When another page shows a setting, it shows a link to this page and not a second control.
+
+## Open Settings
+
+Use one of these:
+
+1. Press the gear in the top bar, next to More.
+2. Press More, then **Settings**.
+3. Press ⌘K, type `settings`, and press Enter.
+4. Open `/c3.html?tab=settings`. Add `&section=recording` to open one section, for example.
+
+Settings is not a tab. While it is open, no tab is selected. Press a tab to go back to that tab.
+
+## The sections
+
+| Section | What it holds |
+|---|---|
+| About you | Your name, your role, what you do and your job description. The Welcome page asks for the same four on first run. |
+| Workspaces | Your workspaces: rename, remove, add one by its folder. Which workspace opens on start, and what the Briefing covers. |
+| Boards and workflows | The workflow templates for new boards and the default template. The rules that move a card. To change the workflow of one board, open that board in Initiatives. |
+| Connectors | How your Claude session reaches Google Calendar, Jira, Wispr Flow and a sender. The import window, the refresh time, how private events show, and attendee names. |
+| Recording | The live transcript: what to listen to, the Whisper model, the language, the echo removal, the final pass after Stop, the words to recognize, and how long kept audio stays. A card at the top says what recording uses now. |
+| Day and time | The time zone, the first day of the week, your working hours, the free time before a meeting with prep, the buffer between meetings, and the time-of-day tint and daylight strip. |
+| Sharing | How a dashboard is shared: off, a link, or sent by the sender. The audiences of the workspace. |
+| Access and devices | Use from a phone or another computer: the host, the tunnel and the people who may open it. |
+| Claude sessions | What a new session starts with: the CLI, the model, the Claude profile and the launch flags. The session limits. Validate consent for this workspace. |
+| Privacy and data | A list of what leaves this computer and when. Whether a TypeSafe key is saved, and the data folder. |
+| Appearance | The theme (Same as system, Light or Dark) and the page that opens first. |
+| Updates | The version of the app and of each workspace's kit. Check for updates, and how updates are found and applied. |
+
+Type in **Search settings** to find a setting in any section. Press **Open section** to go to its section.
+
+## Read a row
+
+Each row has a label, a help line and a control.
+
+- **This computer** means the setting applies to every workspace on this computer.
+- **Workspace · name** means the setting applies only to the workspace in the **Workspace** list at the top of the page. Pick another workspace to see or change its value.
+- A dot after the scope tag means the value is not the default. **Reset** puts the default back. The section name in the list on the left shows how many of its settings you changed.
+- A yellow note with a name such as `PMOS_WHISPER_LANG=en` means a variable in the environment where PMOS starts sets this value. The variable wins over the page. Remove it from your shell profile, then restart PMOS.
+- A lock means the value is fixed or is set somewhere else. The row says where.
+
+A change is saved when you make it. A message at the bottom of the page says **Saved** and the setting's name. Press **Undo** in the message to put the old value back. If a value is refused, the row shows why.
+
+When a section has changed settings, **Reset section** at the top of the section puts all of them back to the default.
+
+Some rows show a feature that PMOS does not have yet, such as choosing calendars, mapping Jira projects, pairing a phone, the device list, and export or reset of every setting. The control on these rows is off, and the row says why.
+
+## Where the settings are kept
+
+The settings that had a home before this page keep it. For example, the recording engine is kept by the notes engine, Validate consent by the validate route, and the theme and the new-session defaults in this browser.
+
+The other settings are kept in the PMOS state directory, in `settings.json` for this computer and in `settings-ws/<workspace>.json` for each workspace. Only you can read these files. `GET /api/settings` returns every setting with its value and default. A change goes through `POST /api/settings` and must come from the workspace page.
+
+## Limits
+
+- A setting changes what the page stores. Some features read their setting in a later release. Until then, the feature uses its default.
+- Settings changes templates and defaults for boards. It does not change an existing board.
+- Nothing on this page sends a message or shares a dashboard by itself.

package/workspace/guide/welcome.md

@@ -6,7 +6,7 @@ timestamp: 2026-10-11
 
 # Welcome (first run)
 
-The Welcome page is the first screen of a new folder. It reads your folder, shows what it found, and sets up your portfolio from it. You do not need to answer questions first.
+The Welcome page is the first screen of a new folder. It asks who you are and where your work lives, reads your folder and the tools you choose, shows what it found, and sets up your portfolio from it.
 
 ## How you get there
 
@@ -14,20 +14,20 @@ Run `pmos` in a plain folder that PMOS has not imported. The terminal says "firs
 
 Run `pmos welcome` to open the page on purpose, for example to scan a folder again or to undo an import. `pmos welcome <path>` opens it for another folder.
 
-Choose **Not now** on the first screen to go to the console. Welcome then stops opening on its own for that folder. `pmos welcome` still opens it.
+Choose **Not now** on the first screen, or **Skip setup** on the screens after it, to go to the console. Welcome then stops opening on its own for that folder. `pmos welcome` still opens it. To go back, choose **Back** or a step you finished in the steps bar at the top.
 
 ## The promise
 
-The page says it before the scan: PMOS reads only, writes nothing in your folder, and nothing leaves this computer. The scan runs on your machine and uses no model. The import is stored in the PMOS state folder, never in your folder.
+The page says it before the scan: PMOS reads only, writes nothing in your folders or your tools, and sends nothing out. The folder scan runs on your machine and uses no model. The tools you tick are read by your agent session with your own connection, read-only. The import is stored in the PMOS state folder, never in your folder.
 
 ## The steps
 
-1. **Welcome.** The page shows the folder name and path. Choose **Add another folder** to open the system folder chooser and add a second folder. Choose **Scan** to start. A spinner shows while the scan runs. A large folder can take a minute or two, and the rest of PMOS keeps working.
-2. **First look.** One sentence gives the counts: initiatives, documents, deadlines, stale documents, duplicates, people and risks. Up to ten findings follow. Each finding shows the file and line it comes from. Choose **Continue**.
-3. **Your portfolio.** PMOS proposes one board for each product folder (`products/<name>/`). If there is no product folder, it proposes one board for the whole folder. Each board lists its initiatives. Each row has a checkbox, a title you can edit, a lane, an anchor, a stage and a document count. Choose the document count to see the documents. Use the board list on a row to move it to another board. Each board shows how many documents PMOS could not place. High and medium confidence rows start checked. The button reads **Import N initiatives into M boards**. The numbers change as you check, uncheck and move rows.
-4. **Questions.** This step appears only when the scan could not decide something. There are three questions at most. Each question shows its default already chosen. Choose **Import** to accept what is chosen. Choose **Skip** to leave a question open: for the anchor question, the proposed anchors then stay marked for you to confirm later.
-5. **First Briefing.** After the import, the page lists up to five things that need you first. An item that belongs to an imported initiative names the initiative and its board. Choose **Continue**. Choose **Undo this import** to take the import back and return to your portfolio.
-6. **More sources.** This step is optional. It offers Calendar (your meetings today and for the next 14 days) and Jira (the issues assigned to you). PMOS reads nothing from them until you choose **Bring in**. Bring in starts the source's read-only skill as an agent session in the workspace, with your own connection. The skill writes nothing to the tool. Choose **Skip** to leave a source out. You can bring it in later from Settings. Inbox and Slack have no import yet. Choose **Open PMOS** to go to the console.
+1. **About you.** Type your name, your role, what you do in one line, and your job description. Every field is optional. Choose **Continue** to save them. The morning brief and the day check use them to judge what matters to you. `pmos proactive settings` shows them, and `pmos proactive settings --role <text> --work <text> --duties <text>` changes them.
+2. **Your sources.** The page shows the folder and its path. Choose **Add another folder** to open the system folder chooser and add a second folder. Under **Tools**, tick the tools PMOS can read: Calendar (your meetings today and for the next 14 days), Jira (the issues assigned to you), Inbox (the threads waiting on you, by subject and sender only) and Slack (messages that mention you and your direct messages, as short summaries). None is ticked at first. Choose **Scan** to start. With tools ticked, the button reads, for example, **Scan the folder and read 2 tools**. Calendar and Jira each start their read-only skill as an agent session. Inbox and Slack are turned on for your daily brief, and the day is prepared now; if the morning brief was not scheduled, it is scheduled for 06:45 each day. A spinner shows while the scan runs. A large folder can take a minute or two, and the rest of PMOS keeps working.
+3. **First look.** One sentence gives the counts: initiatives, documents, deadlines, stale documents, duplicates, people and risks. Up to ten findings follow. Each finding shows the file and line it comes from. Choose **Continue**.
+4. **Your portfolio.** PMOS proposes one board for each product folder (`products/<name>/`). If there is no product folder, it proposes one board for the whole folder. Each board lists its initiatives. Each row has a checkbox, a title you can edit, a lane, an anchor, a stage and a document count. Choose the document count to see the documents. Use the board list on a row to move it to another board. Each board shows how many documents PMOS could not place. High and medium confidence rows start checked. The button reads **Import N initiatives into M boards**. The numbers change as you check, uncheck and move rows.
+5. **Questions.** This step appears only when the scan could not decide something. There are three questions at most. Each question shows its default already chosen. Choose **Import** to accept what is chosen. Choose **Skip** to leave a question open: for the anchor question, the proposed anchors then stay marked for you to confirm later.
+6. **First Briefing.** After the import, the page lists up to five things that need you first. An item that belongs to an imported initiative names the initiative and its board. Under **Your tools**, each tool you ticked says it is being read; its items join your Briefing in PMOS when the agent session finishes. Choose **Open PMOS** to go to the console. Choose **Undo this import** to take the import back and return to your portfolio.
 
 ## Undo
 
@@ -35,4 +35,4 @@ The page says it before the scan: PMOS reads only, writes nothing in your folder
 
 ## What the page does not do
 
-The page does not change your folder. It does not open the files that the exclusion list names, such as `.git`, `node_modules` and files that look like secrets. It does not read Calendar or Jira until you choose **Bring in** on More sources, and the PMOS server itself calls nothing outside this computer. It does not import from Drive, Inbox, Slack or other tools.
+The page does not change your folder. It does not open the files that the exclusion list names, such as `.git`, `node_modules` and files that look like secrets. It reads no tool you did not tick, and nothing before you choose **Scan**. The PMOS server itself calls nothing outside this computer. It does not import from Drive or other tools.

package/workspace/lib/calendar-cli.js

@@ -11,8 +11,9 @@
 const fs = require('fs');
 const path = require('path');
 const stateRoot = require('./state-root');
-const CI = require('../../scripts/calendar-import.js');
-const L = require('../../scripts/trust/ledger.js');
+const { repoScript } = require('./repo-script.js');
+const CI = require(repoScript('calendar-import.js'));
+const L = require(repoScript('trust/ledger.js'));
 
 const COMMANDS = { calendar: ['import', 'status'] };
 const USAGE = [

package/workspace/lib/calendar-layers.js

@@ -213,29 +213,40 @@ function prepOf(e) {
 
 function nextWorkday(date) { let d = addDays(date, 1); while (!isWorkday(d)) d = addDays(d, 1); return d; }
 
-function freeFrom(events, range, today, opts = {}) {
-  const view = range.view;
-  const nowMs = Number.isFinite(opts.nowMs) ? opts.nowMs : localMs(today);
+/** Prep at risk (calendar-memory's PER_STEP rule): each coming timed event with prep steps left and less free working time
+ *  before it than PER_STEP minutes for each step left. Sorted by start. Shared by freeFrom and lib/calendar-tidy.js. */
+function prepRisks(events, today, nowMs) {
+  const now = Number.isFinite(nowMs) ? nowMs : localMs(today);
   const spans = (events || []).map((e) => ({ e, ...(spanOf(e) || {}) })).filter((x) => x.s !== undefined);
   const memo = new Map();
   const loadOf = (date) => { if (!memo.has(date)) memo.set(date, memory.dayLoad(minutesOn(spans, date))); return memo.get(date); };
-
-  // prep at risk: a coming event with steps left and less free time before it than PER_STEP for each step
   const risky = [];
   for (const x of spans) {
     const p = prepOf(x.e);
     const left = p.steps.length - p.done;
-    if (!left || x.f <= nowMs) continue;
+    if (!left || x.f <= now) continue;
     const date = localDay(x.s);
     const startMin = minuteOfDay(x.s);
-    let free = freeBetween(loadOf(date).merged, date === today ? minuteOfDay(nowMs) : DAY_START, startMin);
+    let free = freeBetween(loadOf(date).merged, date === today ? minuteOfDay(now) : DAY_START, startMin);
     for (let dd = today; dd < date; dd = addDays(dd, 1)) {
       if (!isWorkday(dd)) continue;
-      free += Math.min(PER_DAY, freeBetween(loadOf(dd).merged, dd === today ? minuteOfDay(nowMs) : DAY_START, DAY_END));
+      free += Math.min(PER_DAY, freeBetween(loadOf(dd).merged, dd === today ? minuteOfDay(now) : DAY_START, DAY_END));
     }
-    if (free < left * PER_STEP) risky.push({ id: x.e.id, title: str(x.e.title) || 'a meeting', date, s: x.s, left });
+    if (free < left * PER_STEP) risky.push({ id: x.e.id, title: str(x.e.title) || 'a meeting', date, s: x.s, left, free: Math.max(0, free) });
   }
   risky.sort((a, b) => a.s - b.s);
+  return risky;
+}
+
+function freeFrom(events, range, today, opts = {}) {
+  const view = range.view;
+  const nowMs = Number.isFinite(opts.nowMs) ? opts.nowMs : localMs(today);
+  const spans = (events || []).map((e) => ({ e, ...(spanOf(e) || {}) })).filter((x) => x.s !== undefined);
+  const memo = new Map();
+  const loadOf = (date) => { if (!memo.has(date)) memo.set(date, memory.dayLoad(minutesOn(spans, date))); return memo.get(date); };
+
+  // prep at risk: a coming event with steps left and less free time before it than PER_STEP for each step
+  const risky = prepRisks(events, today, nowMs);
 
   // items due soon, most pressing first: overdue and nearest due date, then the higher priority, then the title
   const prio = (p) => (/^P[1-3]$/.test(String(p || '')) ? Number(String(p)[1]) : 9);
@@ -369,4 +380,4 @@ function build({ range, today, nowMs, events, dated, src, own, planItemsDue }) {
   return { layers: l.layers, layers_total: l.layers_total, layers_note: l.layers_note, free, context: c.context, context_total: c.context_total };
 }
 
-module.exports = { layersFrom, freeFrom, contextFrom, build, toneOf, prepOf, spanOf, LAYER_CAP, CONTEXT_CAP, MIN_BLOCK, WINDOW_MS };
+module.exports = { layersFrom, freeFrom, contextFrom, build, toneOf, prepOf, spanOf, prepRisks, minutesOn, localDay, minuteOfDay, LAYER_CAP, CONTEXT_CAP, MIN_BLOCK, WINDOW_MS };