create-pmos 0.516.0 → 0.517.0

package/workspace/guide/reports-dashboards.md

@@ -1,70 +0,0 @@
----
-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 send one as a report, and what the Charts tab holds."
-timestamp: 2026-10-12
----
-
-# Reports: dashboards of reports
-
-A report answers one question. A dashboard is a set of reports for one scope. Open the Reports tab of the console to see them.
-
-## The three tabs
-
-Each tab has one job. A line under the tabs repeats it: **Live** goes to Dashboards, **Sent** goes to Reports, **Building blocks** goes to Charts.
-
-- **Dashboards.** The charts of one scope, drawn from the repository's records. A dashboard is live: it changes when your work changes. The tab shows how many dashboards there are.
-- **Reports.** The documents you send, with their set-ups. See [Set up a report by asking](reports-set-up.md). The tab shows how many drafts wait for you.
-- **Charts.** Every chart the workspace can draw, with the question it answers, the dashboards that use it and the reports that use it. The tab shows how many charts there are. A chart that the Structure step of a report saved is listed too, tagged **Data chart**, with its source and the dashboards and reports that use it. See [Shape what a report says](report-structure.md).
-
-The old tab names still work. A link to Library opens Charts. A link to Drafts opens Reports.
-
-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
-
-Press **Portfolio**, **Board** or **Initiative**.
-
-- **Portfolio** covers every initiative.
-- **Board** covers the initiatives of one board. A board is a domain. Choose it from the list beside the scope.
-- **Initiative** covers one initiative. Choose it from the list.
-
-A report shows only the rows that belong to the scope. A report with no rows in the scope shows an empty card. The card says what is missing and what fills it. The workspace never invents a number.
-
-## The reports
-
-| Report | The question it answers |
-|---|---|
-| North star | Is the north-star metric on its plan? |
-| Quarter outcomes | Where is each key result, where should it be, and where will it land? |
-| Early signals | What is drifting before the numbers say so? |
-| Delivery against promise | Which promised dates will hold? |
-| Maturity by pillar | Where does each pillar stand against its target? |
-| Bets and their checkpoints | When does each bet persevere or pivot? |
-| Synergy and coverage | Do the bets add up to the key results? |
-
-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 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**.
-
-The workspace keeps your layout for each scope in its runtime state. It does not write to the repository. **Reset to default** returns a scope to its first layout.
-
-## Send a dashboard as a report
-
-A dashboard is live. A report is a document that you send on a day. To send a dashboard as a report, press **Send this as a report…** in the head of the dashboard.
-
-1. A sheet shows the proposed report: its name, what it is built from, the output, the schedule and the audience.
-2. Change the name. Choose the output: **PDF** or **Google Slides**. Choose the schedule: **Weekly**, **Every 2 weeks** or **Monthly**. Choose the audience: **Leadership** or **Team**.
-3. Press **Set up**.
-
-PMOS shows the first draft date. Each cycle is a snapshot document of the dashboard as it was on that day. The document is in Reports, under Documents, and the set-up is under Set up. The dashboard stays live.
-
-PMOS drafts only. It sends nothing. It writes to Google only when you press **Create the copy** in the document.
-
-The Share sheet and the schedule control of a dashboard are gone. Each schedule is now the schedule of a report. See and change it in Reports, under Set up.
-

package/workspace/guide/reports-page.md

@@ -1,87 +0,0 @@
----
-type: Guide
-title: "Reports: draft, read and issue"
-description: "How to draft a report, add your notes, issue it, and print or copy it. How the report schedules and the Today cards for reports work."
-timestamp: 2026-10-15
----
-
-# Reports: draft, read and issue
-
-A report tells one audience what moved in the repository. The workspace drafts it from the repository's own files. You read it, add your notes and issue it. A report that you issued is frozen.
-
-The workspace keeps each report in a file of the repository, for example `planning/reports/biweekly/2026-10-16.md`. The issues ledger, `planning/runs/issues.jsonl`, records each Issue. The page and the `pmos report` command use the same writers, so they always show the same reports.
-
-## Open Reports
-
-Open the Reports tab with the shortcut `g r`, from the command palette, or from the Today card of a report. Reports shows the repository that is open.
-
-The Reports page has three tabs: Dashboards, Reports and Charts. See [Reports: dashboards of reports](reports-dashboards.md) and [Set up a report by asking](reports-set-up.md).
-
-The Reports tab is for the documents that you issue. It has four parts:
-
-- **Ask PMOS.** Describe a report. PMOS drafts it.
-- **Found in your work.** The reports PMOS found that you already issue.
-- **Set up.** One row for each report with a schedule.
-- **Documents.** One row for each cycle of each report. A draft or an issued document opens in the [document sheet](document-sheet.md).
-
-The parts that this guide describes below, such as Draft now, Edit notes and the report schedules, are the controls of the cadence report. The Reports tab does not show them. The `pmos report` commands in "In a terminal" do the same acts.
-
-## Draft a report
-
-1. Press **Draft now**. The workspace writes the draft of the cadence you have selected, for example biweekly. A cadence is one kind of report: daily, weekly, biweekly or monthly.
-2. The new draft is selected. Every number in it comes from the repository's ledgers. The page never changes a number.
-
-For a report with a saved structure, **Draft now** starts a session that follows the structure. The button shows **Drafting…** until the draft is ready, and a notice says when it is. A **Redraft**, and a draft at a slot you name, stay instant. A report with no saved structure is drafted at once.
-
-A second **Draft now** for the same slot is refused. Press **Redraft** to write the draft again. A Redraft keeps every note. It moves a note with its initiative, even when the order of the initiatives changed. A note of an initiative that left the window stays at the end, under "Notes kept from an earlier draft".
-
-To draft another cadence, open the menu with the three dots and choose **Draft now** with the name of the cadence.
-
-## Edit notes
-
-Press **Edit notes**. One sheet shows every note of the draft: the headline, each initiative, and the needs-your-call part when the definition names an audience. Write your text and press **Save notes**. Saving a note draws the report again from the files as they are now, and keeps every note. Use it for the text, not to freeze a number: a number can change when the repository changed since the draft was written. A draft with no note markers has no note to edit. An issued report cannot be edited.
-
-## Issue a report
-
-Issue takes two presses.
-
-1. Press **Issue**. This button is on the page and on the Today card "A draft is ready to issue". A sheet reads the draft and shows its headline.
-2. Press **Issue** in the sheet. The workspace records the Issue in the issues ledger with the sha of the file you read.
-
-If the file changed after you read it, the workspace refuses and nothing is issued. Close the sheet, read the draft again and press Issue again.
-
-After Issue the file is frozen. **Redraft** and **Edit notes** are gone for that report. If someone edits the file anyway, the row shows "Edited after issue".
-
-Only you can issue. An agent cannot press Issue, and the page does not take a name from you: the workspace writes who pressed.
-
-## Print or copy an issued report
-
-An issued report offers two actions, in the sheet after Issue and on the page:
-
-- **Print / PDF** opens the print dialog with the report alone, in the light theme. Choose "Save as PDF" in that dialog to make a PDF.
-- **Copy as markdown** puts the report on the clipboard without its frontmatter and without the note markers.
-
-These are the only two ways a report leaves the page. The page has no control that moves a report out of the workspace. You decide where a printed or copied report goes.
-
-## Report schedules
-
-A schedule drafts a report at its time. It never issues one. A schedule belongs to a report by its skill: the skill `report-biweekly` feeds the biweekly report, whatever the cadence of the schedule says.
-
-- **Pause** stops a schedule. **Resume** starts it again.
-- **Set up report schedules** appears when the repository has none. One press creates the recommended schedules. It never creates one twice.
-- **Other schedules (n)** lists the schedules that feed no report. Manage them with the `pmos schedule` commands.
-
-A schedule fires only while the workspace server runs.
-
-## The Today cards
-
-| Card | When it shows | What the press does |
-|---|---|---|
-| A draft is ready to issue | A draft exists, it is newer than the last issued report of its cadence, and it is not issued. | Opens the Issue sheet. |
-| A schedule ran and left no draft | A schedule ran and no report file of its cadence is newer than the run, after two hours of grace. | Writes the draft now. |
-
-The card for the monthly kill-condition check is drawn with the initiative cards.
-
-## In a terminal
-
-The same acts exist as commands: `pmos report draft`, `pmos report issue` and `pmos report list`. The ledger records who ran each command.

package/workspace/guide/timeline.md

@@ -1,70 +0,0 @@
----
-type: Guide
-title: "Breakdown › Timeline: the items on a time axis"
-description: "How to read the Timeline view of a Breakdown, move the dates of an item by dragging its bar, change a due date by dragging the end of a bar, and read the health flags."
-timestamp: 2026-10-05
----
-
-# Breakdown › Timeline: the items on a time axis
-
-The Timeline view shows the items of one initiative on a time axis. Each item that has a start date or a due date has a bar. The bar runs from the start date to the due date.
-
-## Open the Timeline
-
-1. Open the Breakdown of an initiative.
-2. At the top of the Breakdown, press **Timeline**. The Timeline is next to **Tree** and **Board**.
-
-## Read the Timeline
-
-- **Months.** The months are across the top. The axis starts at the first month that has a date and stops at the last month that has a date. It always shows today and at least three months.
-- **Today.** A vertical line shows today. The label **Today** is on its own line above the month labels, next to the line.
-- **Scrolling.** The chart scrolls to the side inside its own area, on every screen width. When the Timeline opens, the chart scrolls so that today shows. The column with the titles stays in its position while the chart scrolls.
-- **All items.** The first row shows the full initiative, from the first start date to the last due date. It has one segment for each stage. A small gap shows where each stage starts, also when two stages overlap.
-- **Stage rows.** Under the first row, the items are in groups by stage. The stages are in the same order as in the Tree. Each stage row shows the dates of its items and the number of dated items, for example "Build, 3 dated items".
-- **Item rows.** Each item row shows the title, the dates and the bar. A Done item has a darker bar.
-- **Milestones.** An item that is a milestone shows a diamond on its due date. The diamond also shows on the stage row and on the first row.
-- **Proposed items.** An item that an agent proposed and that you did not keep yet has a lighter bar with a dashed edge and the signal **Proposed**. A proposed item does not make a stage bar or the first row longer.
-- **Items with no dates.** An item with no start date and no due date has no bar. A line under the chart gives the number of such items. To give an item dates, open it and set **Start** and **Due** in the item sheet.
-
-An item with only a start date or only a due date has a bar of one day.
-
-## Move the dates of an item
-
-- **Move both dates.** Drag the bar to the left or to the right. The start date and the due date move by the same number of days.
-- **Change the due date.** Drag the end of the bar (the line at its right edge). Only the due date changes. The due date cannot go before the start date.
-- **Short bars.** A bar that is narrower than about 24 pixels always moves whole. To change only its due date, use the keyboard or the item sheet.
-- **Open the item.** Press the bar without moving it. The item sheet opens.
-
-The bar shows the new dates while you drag it. When you let go, the workspace saves the change.
-
-With the keyboard:
-
-1. Press Tab until the bar has the focus.
-2. Press the Left or Right arrow key to move both dates by one day.
-3. Press Shift with the Left or Right arrow key to change only the due date.
-4. Press Enter to save. Press Escape to go back to the saved dates.
-
-If you move the focus away from a bar that has a change, the workspace saves the change. If you press Tab, the focus then goes to the next bar.
-
-What a move writes:
-
-- Each drag adds one line to `planning/runs/plan-items.jsonl`. The line is a `set` line with the dates of the item. When you change only the due date, the line has only the due date.
-- An item that has only a due date keeps only a due date when you move it.
-- A move changes one item only. The dates of other items do not change, also when they come after the item. The Timeline does not count effort in days.
-- If the workspace cannot save the change, a message gives the reason. The bar goes back to the saved dates.
-
-## Health
-
-The Timeline shows a flag only when an item is not on track. The flag is text and a small dot, on its own line under the dates of the item. The bar of the item has a coloured outline.
-
-- **At risk: starts before an item ends.** The item starts on or before the day that one of its predecessors ends. The flag names that predecessor and its due date. A Done predecessor does not cause this flag. A Done item never shows it.
-- **At risk: due on a date, not done.** The due date is before today and the item is not Done.
-- **Off track: milestone due on a date, not done.** A milestone has a due date before today and it is not Done. Its diamond has the same colour as the text of the flag.
-
-Limit: this view checks only the predecessors in the same initiative. A predecessor in a different initiative does not cause a flag here. To see such a clash, compare the dates of the two items.
-
-To remove a flag, change the dates of the item or of its predecessor, or move the item to Done.
-
-## On a phone
-
-On a narrow screen, the page does not scroll to the side: only the chart does. To move a bar, touch it and drag it to the side. A short bar takes a touch a little to its left or right. To scroll the chart, drag the empty part of a row.