create-pmos 0.516.0 → 0.517.0

package/workspace/guide/index.md

@@ -8,97 +8,96 @@ timestamp: 2026-11-03
 
 This guide describes the PMOS workspace as it works today. It ships with the app. When a change alters how the workspace looks or behaves, the same change updates this guide.
 
+To open the guide from any page, press the round menu button at the bottom of the page, then the **?** icon (Guide). The guide opens wide in the Viewer. Every page is in the list on the left, by group, with **Find a page** on top; a group folds and stays folded. Above each page, one chip for each of its sections takes you there. A link to another guide page opens that page in the same place. Press ← to go back. On a phone, or when the Viewer is narrow, the list icon beside the title shows the list.
+
 ## The screen
 
-On a desktop the workspace is one frame. [Layout](layout.md) explains each part.
+PMOS has three places: **Home**, **Board** and **Intelligence**. The round menu button at the bottom of every page (bottom left on a computer, bottom right on a phone) moves between them.
 
-1. **The top bar.** Repository ▾, the six places (Docs and People included), search (⌘K), Sync when the repository is not in sync, and Settings.
-2. **The place.** One of Agenda, Initiatives, Board or Reports, or Docs (⌘K or `g d`), or People (⌘K or `g p`). It fills the screen under the bar.
-3. **The detail.** The item you opened: an initiative with its status, next steps and artifacts, or the profiles. It opens beside the place and closes with ×.
-4. **The agent dock.** Terminals, documents, conversations and web pages. It is open on Agenda and a thin rail elsewhere.
+1. **Home.** The list of your work on the left, the chat in the middle and the Viewer on the right. [Home](home.md) explains each part.
+2. **Board.** Every initiative of the products you pick, by stage, with programs, a timeline and a list. [Programs on the Board](programs.md) explains the views.
+3. **Intelligence.** Your goals, read from each product's OKR file, with the readings, forecasts and **Did it work?**. [Intelligence reads your OKR file](intelligence-okr-goals.md) explains it.
+4. **The Viewer.** The item you opened: an initiative, a document, a meeting, a report, your day or a page of this guide. It closes with ×.
+5. **The menu's icons.** **Search** (⌘K or `/`), **Guide** (this guide) and **Settings**.
 
 ## Where things are
 
 | You want | Go to |
 |---|---|
-| What is waiting for you now | Agenda |
-| Your day as a brief: today's meetings, what needs you, the portfolio | The Briefing page of the console (`/`) |
-| Every Jira ticket and WBS item assigned to you, ranked, to brief an agent | My work, or press `g w` |
-| The initiatives of a repository, or of every repository | Initiatives. Choose **All repositories** in Repository ▾ for every repository. |
-| The sessions of a repository, by initiative | The agent dock. ⌘K → **Branches and sessions** lists the branches. |
-| The items of an initiative | Board, or Breakdown in the initiative detail |
-| How the Briefing cards, day part, Portfolio pulse and overdue items work | [Briefing](briefing-cards.md) |
-| Home in the Agreed design: the list by product, New for you, Search, and the designed features | [Home](home.md) |
-| The premium Briefing page at /premium.html | [Premium Briefing](briefing-premium.md) |
-| Run reports | Reports |
-| Whether a document is the same as its Google Docs or Confluence copy | Docs: ⌘K → **Docs**, or press `g d` |
-| The people you work with: who they are, your interactions, their tone, your notes and shared work | People: ⌘K → **People**, or press `g p` |
-| Repositories, Profiles, New sessions (the default CLI, model, Claude profile and launch flags), Validate consent, People (calendar names), Theme | Settings |
-| Validate | Settings, under Validate consent: **Open Validate** |
-| A document, a decision record, a memory entry, a page of this guide | ⌘K, with its scope: Knowledge, Memory or Guide |
-| A report across every repository | ⌘K: Portfolio report |
-| A note, or a message to a session | ⌘K |
-
-## Where to read next
+| What is waiting for you today | Home: press **Good morning** to open **Your day** |
+| An initiative, its tasks, sessions and documents | Home: press its row in the list |
+| A new task, chat, recording or initiative | Home: **+** at the top of the list |
+| Every initiative by stage, programs and milestones | Board |
+| Goals, readings, forecasts and whether shipped work worked | Intelligence |
+| A document, an initiative, a meeting or a file | Search (⌘K) |
+| The calendar | Home: the calendar icon in Your day's header |
+| Theme, products, Claude, Claude's checks, Jev and Laya, Adler, connectors, repositories, workflows and updates | Settings |
+| A page of this guide | The menu: **Guide** |
+
+## Read next
+
+### Get started
 
 - [What Claude does behind the scenes](agent-capabilities.md): every job Claude runs by itself, when it runs, what it reads, where you see it, how to stop it, and what it fixes by itself.
 - [First run](welcome.md): test your Claude login, describe the project, choose its folder, search your tools read-only, and set up PMOS from Home.
-- [The Briefing](briefing.md): the console's first page: Today's meetings, Needs you (Done, Not yet, Drop) and the Portfolio pulse.
+- [Layout](layout.md): the three places, the menu button, the Viewer and its trail, docking panels, the keys, and the phone.
 - [Start the workspace without a terminal](launcher.md): the PMOS app, the login item and `pmos launcher`.
-- [Jira tickets](jira.md): Jira tickets drafted from the PRD, pushed when you select them, and their status.
-- [My work](my-work.md): the work assigned to you, its order, the brief to an agent, and `pmos my-work`.
-- [Data freshness](data-freshness.md): when each source is read again, how old it is, Settings › Data refresh and its log, and `pmos calendar`.
-- [People](people.md): the people you work with in a repository, how they get there, and `pmos people`.
-- [Docs](docs.md): whether each linked document is the same as, ahead of or behind its Google Docs and Confluence copy.
-- [Calendar popup](calendar-popup.md): open the full calendar over any page of the console with the calendar button or the C key, and close it.
-- [The phone companion](phone-companion.md): what the console shows at phone width: one moment of your day, your items one at a time, Tell PMOS and Record.
-- [Layout](layout.md): the frame, the keys and the rule for where a list or a detail opens.
-- [The Calendar tab of the console page](console-calendar.md): the zooms, the layer chips, the markers, the context of a meeting and free time.
-- [Statuses](statuses.md): what each status means, where it comes from, and what you can change.
-- [Initiatives and next steps](initiatives-and-next-steps.md): the detail, the next steps, and the artifacts.
-- [Breakdown](breakdown.md): an initiative's items in the Tree and on the Board, the item sheet, Undo, Keep, Hand to agent and `pmos item`.
-- [Scheduled tasks and the command line](scheduled-tasks-and-cli.md): how to make, edit and run scheduled tasks.
-- [Validate a repository](validate-with-typesafe.md): what each kind of document is compared with, how to read the verdict, and what leaves your machine.
-- [Today and the proactive engine](proactive-engine.md): what Today finds, what you can do with an item, the settings, the commands and the limits.
-- [Live notes](live-notes.md): take notes in a meeting, confirm each talking point, and what goes to Jev when you turn it on.
-- [Present while a meeting records](present-in-a-meeting.md): Present in the recording tab, the audience tab, the presenter view, and presenting a window.
-- [Notes](notes.md): listen to a meeting on this machine, see decisions, actions and questions caught and checked against the repository, and get a summary.
-- [Find knowledge without reading whole files](knowledge-graph.md): what `pmos kg` finds, its commands, how to read its numbers, and its limits.
-- [Ask about the past](ask-the-past.md): why something was decided or dropped, answered in the initiative chat from the records, with the line each claim rests on; "You decided this before" on a new initiative.
-- [Initiatives: the Roadmap, the List and the initiative sheet](initiatives-screen.md): how to read and order the initiatives of a repository, open the sheet, make a new initiative, and review the cycle.
-- [Initiatives and the Roadmap: one ranked list](initiatives-roadmap.md): what day one shows, what happened to Now, Next and Later, and `pmos initiative` and `pmos measure` from a terminal.
-- [The Initiative Driver: drafts the agent files for you](initiative-driver.md): when the driver runs, the unblock sweep, the limits, Keep, Send back and Drop, the board modes, and `pmos driver`.
+- [Settings](settings.md): what each section of Settings holds.
+- [Data freshness](data-freshness.md): when each source is read again, how old it is, and `pmos calendar`.
+- [Adler, Claude's face](adler.md): who Adler is, where he shows, what his six moods mean, and Settings › Adler.
+
+### Home and your day
+
+- [Home](home.md): the list by product, Your day and New for you, the chat, the Viewer, Search and the place menu.
+- [What waits for you, and pmos today](today.md): Your day in Home, and `pmos today` from a terminal.
+- [My work](my-work.md): the Jira tickets and tasks assigned to you in Home's list, their order, and `pmos my-work`.
+- [Documents and their copies](docs.md): a document in the Viewer, its Google Docs or Confluence copy, and `pmos docs`.
+- [People](people.md): the people you work with, where they come from, and `pmos people`.
 - [Claude proposes: the one ✦ on each initiative](claude-proposes.md): what Claude finds when you add an initiative, new dates, done and tidy names for late tasks, ✓, ✕, Undo, and `pmos propose`.
-- [Claude drafts metrics without being asked](metric-drafts.md): when Claude drafts the metrics of a product, a program or an initiative, keep, drop, Undo, and `pmos metrics draft`.
+- [The next prompt, suggested and sharpened](next-prompt.md): what the chat suggests after a reply, and the sharper version of a rough prompt.
+- [Ask about the past](ask-the-past.md): why something was decided or dropped, answered in the initiative chat from the records; "You decided this before" on a new initiative.
+- [Expected outcomes](outcomes.md): what each initiative should change once it ships, the date to check it, and `pmos outcomes`.
+- [Rehearse a plan](rehearse.md): what a date change or a cut breaks or helps, before you approve it, and `pmos rehearse`.
 - [Your impact](your-impact.md): what counts as your impact, the weekly check in Home's chat, the switch, and `pmos impact`. Private to you.
 - [What you might have missed](what-you-missed.md): the weekly check for quiet drift, at most three items in Home's chat, its replay, and `pmos drift`.
-- [Adler, Claude's face](adler.md): who Adler is, where he shows, what his six moods mean, and Settings › Adler.
-- [Ready-made dashboards and reports](ready-made-dashboards.md): the dashboard and reports every program, product and initiative has, the Work | Dashboard icon, the Sponsors and Team cuts, late and held reports.
-- [Core documents: what each level keeps](core-documents.md): the core documents of the portfolio, a board and an initiative, their states, how PMOS drafts them, Issue it, and `pmos coredoc write`.
-- [The Horizon scan: the agent looks outside your initiatives](horizon-scan.md): how often it runs, the watch list you keep, what a scan does, where findings land, what it cannot do, and `pmos scan`.
-- [PM-only acts: what you and your agents can do](pm-only-acts.md): the acts that were yours alone, how the workspace checks that a press comes from your page, your terminal or an agent session, how an agent's act is logged under its name (D98), and what to do when a press is refused.
-- [PM-only lines: how the workspace checks your acts](pm-only-lines.md): how each act is recorded, what the Today card "A PM-only line is not attested" means, and the grants for a bulk lifecycle change and a Release.
-- [Breakdown › Timeline](timeline.md): an initiative's items on a time axis, split by stage, with milestones, today, and the at-risk flag when an item starts before its predecessor ends.
-- [Initiatives › Timeline](initiatives-timeline.md): when each initiative runs, one row per initiative, and how to reorder rows by their grip.
-- [Workflows](workflows.md): Settings › Workflows, the stages each kind of initiative goes through, New workflow in the chat, and `pmos workflow`.
-- [Intelligence reads your OKR file](intelligence-okr-goals.md): each key result of the OKR file is a row, with its reading or the source it needs; Did it work?, All products and Delivery trends.
-- [Reports and dashboards: what needs you](reports-needs-you.md): the reports that wait for you come first, each with one ✓ (Issue, Confirm the definition, Move to a product, Resume); the first dashboard is drafted from the OKR file.
-- [Expected outcomes](outcomes.md): every initiative says what should change once it ships and when to check it. Claude drafts each one from the PRD or the KR, you keep it with ✓, and `pmos outcomes`.
-- [The next prompt, suggested and sharpened](next-prompt.md): after a reply, up to two prompts to send next; while you type a rough prompt, a sharper version in your style (Polish, Prompt engineer, Your own).
-- [Rehearse a plan](rehearse.md): before you approve a date change or a cut, Claude shows what it breaks or helps in other initiatives, goals and program milestones, with the record each effect comes from, and `pmos rehearse`.
-- [Forecasts](forecast.md): how a goal, a delivery, a program and a health budget are forecast, the states, the kept baseline, and `pmos forecast`.
-- [Programs on the Board](programs.md): All products, programs first then products, By product, the program panel and its milestones, and the 60 % side panels.
-- [Board](board.md): one Kanban for the items of every initiative, its filters, Release, and `pmos board`.
-- [Published board](published-board.md): a read-only copy of a Board for a teammate, what a reader sees and cannot do, the data pack and how to preview one.
-- [The lifecycle](lifecycle.md): the six stages and two milestones of an initiative, what each makes, which steps each lane uses, and how the step is read from the records.
-- [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 one, how to send one as a report, and the Charts tab.
-- [Set up a report by asking, and the report finder](reports-set-up.md): how to ask PMOS to draft a report you send, how the finder finds reports you already send, and how a cycle becomes a document.
-- [Shape what a report says: the Structure step](report-structure.md): how to decide with PMOS what a report answers, where each number comes from and how it is worked out, add a page in Chrome or an app as a source, and try the plan on real data.
-- [Shape what a report says: the Structure step](report-structure.md): how to decide with PMOS what a report answers, where each number comes from and how it is worked out, add a page in Chrome or an app as a source, and try the plan on real data.
-- [Design how a report looks, and read it as a deck](report-design.md): how to design a report in the design studio, read each cycle as a deck or an interactive document, present it, and use speaker notes and notes on the slide.
-- [The document sheet](document-sheet.md): read a document as rich text, edit it, accept the agent's proposals section by section, read the edit log, and clear a stale document.
-- [Ask the agent from the page](ask-the-agent.md): the five presses that start an agent from the console, what the agent may do, and what stays yours.
-- [Sessions in console3](console3-sessions.md): the Sessions panel, how to open the terminal of a session on the same page, and how to end a session.
-- [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.
+- [Notes](notes.md): listen to a meeting on this machine, see decisions, actions and questions caught and checked against the repository, and get a summary.
+- [Present while a meeting records](present-in-a-meeting.md): Present in the recording tab, the audience tab, the presenter view, and presenting a window.
+- [Meeting focus over Google Meet](console-calendar.md): the Chrome extension's panel over a call, and `pmos extension`.
+- [Live notes](live-notes.md): talking points and the check by Jev; the rules stay, the screen was removed.
+
+### Board and initiatives
+
+- [Programs on the Board](programs.md): All products, groupings, the stage track, Kanban, timeline and List, and the program panel.
+- [Published board](published-board.md): a read-only copy of a Board, what a reader sees, and how to publish one.
+- [The lifecycle](lifecycle.md): the steps every initiative goes through, what each step makes, and how the workspace knows where an initiative is.
+- [Statuses](statuses.md): what each status means, where it comes from, and what you can change.
+- [Next steps to done](initiatives-and-next-steps.md): how PMOS works out an initiative's next steps, who owns each, and what a session started on one may do.
+- [An initiative's tasks, and pmos item](breakdown.md): tasks under their initiative, tasks an agent adds, who made a change, and `pmos item`.
+- [pmos board](board.md): every initiative's items in four columns, from a terminal.
+- [Workflows](workflows.md): Settings › Workflows, the stages each kind of initiative goes through, and the default workflow.
+- [Core documents: what each level keeps](core-documents.md): the core documents of the portfolio, a board and an initiative, their states, Issue it, and `pmos coredoc write`.
+- [Ready-made dashboards and reports](ready-made-dashboards.md): the dashboard and reports every program, product and initiative has, the Work | Dashboard icon, the Sponsors and Team cuts.
+- [The Initiative Driver](initiative-driver.md): when the driver drafts the agent files, the unblock sweep, the limits, Keep, Send back and Drop, and `pmos driver`.
+- [Jira tickets](jira.md): Jira tickets drafted from the PRD, pushed when you select them, and their status.
+- [Integrated work](integrated-work.md): from a merged commit to Done, and `pmos verify-work`.
+- [Initiatives and the Roadmap: one ranked list](initiatives-roadmap.md): what happened to Now, Next and Later, and `pmos initiative` and `pmos measure`.
+
+### Intelligence and reports
+
+- [Intelligence reads your OKR file](intelligence-okr-goals.md): the goal list from the OKR file, readings, Did it work?, All products and Delivery trends.
+- [Reports and dashboards: what needs you](reports-needs-you.md): the reports that wait for you come first, each with one ✓; the first dashboard is drafted from the OKR file.
+- [Forecasts](forecast.md): how PMOS forecasts a goal, a delivery, a program's milestones and a health budget, and `pmos forecast`.
+- [Claude drafts metrics without being asked](metric-drafts.md): when Claude drafts the metrics of a product, a program or an initiative, keep, drop, Undo, and `pmos metrics draft`.
+- [The Horizon scan](horizon-scan.md): how often it runs, the watch list, where findings land, what it cannot do, and `pmos scan`.
+- [Set up a report by asking](reports-set-up.md), [Shape what a report says](report-structure.md), [Design how a report looks](report-design.md) and [Report slides](report-slides.md): a report from setup to slides.
+- [Draft and issue a cadence report](reports.md): `pmos report`, the notes kept when you draft again, and Issue.
+
+### Rules and the command line
+
+- [PM-only acts](pm-only-acts.md): the acts that were yours alone, how the workspace checks where a press comes from, and how an agent's act is logged under its name (D98).
+- [PM-only lines](pm-only-lines.md): how each act is recorded, and the grants for a bulk lifecycle change and a Release.
+- [Scheduled tasks and the command line](scheduled-tasks-and-cli.md): how to make, edit and run scheduled tasks.
+- [Today and the proactive engine](proactive-engine.md): what the engine finds, the morning brief, the settings, the commands and the limits.
+- [Claude's leads](briefing-premium.md): `pmos lead` and the leads Claude writes ahead of time.
+- [Find knowledge without reading whole files](knowledge-graph.md): what `pmos kg` finds, its commands, how to read its numbers, and its limits.
+- [Validate a repository](validate-with-typesafe.md): what each kind of document is compared with, how to read the verdict, and what leaves your machine.

package/workspace/guide/initiatives-and-next-steps.md

@@ -1,22 +1,15 @@
 ---
 type: Guide
-title: "Guide: initiatives and next steps"
-description: "What the initiative detail shows, top to bottom: status, lifecycle control, and the next step the workspace proposes."
-timestamp: 2026-10-08
+title: "Next steps to done: how PMOS works out what comes next"
+description: "How PMOS works out an initiative's next steps, who each one belongs to, how a step an agent can do is prepared and started, and what that session may do."
+timestamp: 2026-11-03
 ---
 
-# Guide: initiatives and next steps
+# Next steps to done: how PMOS works out what comes next
 
-Select an initiative in the list. The detail opens in the detail column.
+Open an initiative from Home's list. It opens as a page in the Viewer. Its stage card shows the stage, how many of its steps are done, and the steps still open: yours first, then a running agent, then late or blocked steps, then the ones waiting on someone. The last node is the next stage. [Home](home.md) explains the initiative's page.
 
-## What the detail shows, top to bottom
-
-1. **Status.** The status, why it has that status, who acts now, the next thing to do, and when the status changes. If the status is Needs you, each open item is listed in its own words. If the status cannot be read, the detail says so and shows no status.
-2. **Lifecycle control.** Hold, close, cancel or reopen. Beneath it, the history of every change.
-3. **Next steps to done.** Everything between now and acceptance, in order. See below.
-4. **Phases and links.** The workflow phases and the external links.
-5. **What the documents say.** Up to three lines, and Jev's suggestions if you turned them on. See below.
-6. **Artifacts.** Documents, conversations and files.
+This page explains the rules behind those steps: where they come from, who owns each one, and what an agent session started on a step may do. The console drew a **prepare** and **go** control under each step, and it was removed. The same plan can still be prepared, approved and started with `pmos proactive prepare`, under the same rules (see [Today and the proactive engine](proactive-engine.md)).
 
 ## What the documents say
 
@@ -80,9 +73,3 @@ You can turn on the Typesafe skill for a run. It helps the session categorise, s
 ### Review
 
 After the session ends, the step offers **review what it did**. The review lists the files the branch changed against trunk, shows the end of the conversation, and lists any judgments the session reported, with those that failed the shape check marked. Then choose **accept the step** or **send it back**. A send-back needs a note. Your verdict is recorded in the runtime state folder. Accepting a step does not accept the initiative. Acceptance stays at the Acceptance Gate.
-
-## Artifacts
-
-- **Documents** open in a tab. You can edit them.
-- **Conversations** are sessions bound to the initiative. A conversation is saved when its session ends. It opens read-only. It stays on this computer, in the runtime state folder. It is not in the repository.
-- **Files from git** are the files changed for the initiative. They open read-only in a tab. A file that exists only on the initiative branch opens from that branch. A file that cannot be previewed, such as a binary file, says so.

package/workspace/guide/layout.md

@@ -1,255 +1,48 @@
 ---
 type: Guide
-title: "Guide: layout"
-description: "The frame: one top bar, the place on screen, the detail and the agent dock; the phone tabs and lists; the keys; and the older layout."
-timestamp: 2026-11-02
+title: "Layout: the places, the menu and the Viewer"
+description: "The three places, the round menu button, the Viewer and its trail, docking panels, the keys, and the phone."
+timestamp: 2026-11-03
 ---
 
-# Guide: layout
+# Layout: the places, the menu and the Viewer
 
-This page describes the classic workspace. The classic workspace and the console are deleted, and `/classic.html` opens Home. Keep this page only as a record until the guide is rewritten for Home.
+PMOS has three places: **Home**, **Board** and **Intelligence**. Each fills the window. There is no top bar and no left sidebar of places. The console and its three columns were removed; their old addresses open Home.
 
-On a desktop screen the workspace is one frame. It has one top bar, the place on screen under it, the detail when you open one, and the agent dock at the right. There is no left sidebar.
+## The menu button
 
-## The top bar
+The round button at the bottom of every page moves between the places: bottom left on a computer, bottom right on a phone. Press it to open the menu: **Home**, **Board** and **Intelligence**, then three icons: **Search**, **Guide** and **Settings**. The menu holds nothing else.
 
-Corners are rounded a little: 6 pixels on buttons and fields, 8 pixels on cards and sheets. Buttons and tabs use normal capital letters. Only the small headings above a list stay in capitals. The page does not scroll. Only the place on screen scrolls, and the top bar stays where it is. The tab you are on is marked with a straight line under it.
+- The button has a blue dot when something is new for you and an amber dot when a source is stale.
+- Press the place you are on to go back to its start.
+- [Home](home.md) explains the menu in full.
 
-The top bar has these parts, from left to right:
+## Home
 
-- **Repository ▾** names the current repository. Press it to choose another repository, or **All repositories** to see the work of every repository at once. All repositories replaces the old Portfolio mode.
-- **Branches and sessions** is in ⌘K. It opens a sheet with every branch of the repository (main first) and how many sessions run in each. Press a branch to see its sessions, open one, end one, or start a session there. **＋ branch** makes a branch, and **＋ session** starts one with a branch, an agent, a profile and launch flags. The form starts from the defaults in Settings, under New sessions. With All repositories, the sheet lists every repository.
-- **Agenda, My work, Initiatives, Board, Reports, Docs and People** are the places. Each has an icon before its name, the same icon as on the phone. Press one to show it. The Agenda count shows how many items need you. Docs shows whether each document is the same as its Google Docs and Confluence copy. People shows the people you work with in the repository ([People](people.md)).
-- **Search or capture ⌘K** opens the command palette. Type to find an initiative, a repository, an open tab or a command.
-- **Sync** shows only when the current repository is not in sync with its remote. Press it to fetch, bring in the work of the other machine, record your changes and push. If the repository has not fetched in the last 10 minutes, Sync also shows, because a push from another machine is not visible until a fetch. When the repository fetched recently and is in sync, Sync is not shown. When two machines add lines to the same ledger (a `.jsonl` file under `pmos/` or `planning/`), Sync keeps the lines from both machines. If Sync stops, the message names the step that stopped. If both machines changed the same lines of another file, Sync changes nothing and names the files. Then choose **Push this machine’s version** or **Pull the other machine’s version**. Sync keeps that version of those files, keeps all other changes from both machines, and finishes. It never overwrites the remote history.
-- **Sync on its own.** If you forget to press Sync, the workspace syncs for you. It syncs each repository once when the workspace starts. It also syncs a repository that has records not yet pushed when no record changed for 5 minutes. It syncs only on the default branch (for example `main`). In a document repository it syncs every changed file. In a code repository it also needs every commit not yet pushed to change records and no code. If a document folder has been left on another branch, the workspace puts it back on the default branch for you, with your records saved, when that loses nothing. It tells you only when it cannot do this safely, for example when two saved versions of one page do not match. If you close the tab while records are not yet pushed, the browser asks you first. To turn automatic sync off, start the workspace with `PMOS_AUTO_SYNC=0`.
-- **Old work folders clean up on their own.** When a piece of work has been merged and its extra folder has been untouched for 14 days, with nothing unsaved in it and no session using it, the workspace removes the folder. The work itself is kept. To turn this off, start the workspace with `PMOS_AUTO_CLEAN=0`.
-- **Settings** opens the settings of the workspace.
+The list of your work is on the left, the chat is in the middle, and the Viewer is on the right. A row opens its item in the Viewer. The panel icon shows or hides the list, and PMOS keeps that choice on this computer.
 
-Each place is drawn when its run is built. Until then the place says which run brings it, for example "Board arrives in Run 4."
+## The Viewer
 
-## Settings
+The Viewer shows one item: an initiative, a program, a task, a document, a meeting, a report, Your day or a page of this guide.
 
-Settings holds settings only, in eight sections. On a wide screen they are cards in two columns, like Agenda: Repositories, New sessions, Profiles and Theme on the left, and Validate consent, People, Online and Updates on the right. On a narrow screen the cards stack in one column. Each switch (Validate consent, People, Online) turns on when you press it. **Check for updates** is at the top right of the page.
+- It opens beside the page. Settings › General › **Viewer opens as** makes it a popup over the page instead.
+- Drag its edge to change its width. The expand icon opens it wide. Each kind of item keeps the width you gave it.
+- It keeps one trail: a press inside it keeps the item behind, ← goes back, → goes forward, and the browser's Back and Forward move along the same trail. × or Escape closes it.
 
-- **Repositories**: every registered repository. Press a repository to make it the current one. Press its ⋯ for **Rename** or **Remove from PMOS**. Each asks in a sheet, and a remove asks you to confirm. **Add repository** shows the scan of a folder before you add it.
-- **Profiles**: the Claude profiles a session can start with. These are the descriptors in `~/.claude/profiles`, and also the profiles you already run: a shell command that sets `CLAUDE_CONFIG_DIR` (for example `alias claude-work='CLAUDE_CONFIG_DIR=~/.claude-work claude'`), a launcher script named `claude-*`, or a config folder such as `~/.claude-work`. Each profile is a row with a **Detected** badge when PMOS found it rather than wrote it, and a **Default** badge when it is the default. Its ⋯ menu has **Use as default**. A profile found this way says where it was found, and a session under it sets only `CLAUDE_CONFIG_DIR`. The list reads again every few seconds while Settings is open, and **Look again** in the Claude profiles menu reads it at once. When nothing is found, the note names the start-up files and folders PMOS looked at. Press **New profile** to make one. This writes `~/.claude/profiles/<id>.json`. Account secrets are never shown in the browser.
-- **Claude login and profile** (Settings › Claude): the same profile-specific sign-in and verification controls as [Welcome](welcome.md). Set up a separate PMOS login or choose an existing setup. If that login is signed in already, PMOS checks it at once. Otherwise PMOS runs `claude auth login` in that profile’s terminal: Claude opens your browser, and the terminal takes your keys if Claude asks for a code, also when you open the session from the sessions list. Claude’s first-run screens (theme, folder trust) do not appear. PMOS checks the login when the sign-in ends. When the check fails, the message names the login it checked and its folder. Signing in to a different Claude login, for example in another terminal, does not sign this one in. PMOS does not copy credentials. A missing selected profile refuses new sessions instead of silently changing accounts.
-- **New sessions**: the default CLI, the default model, the default Claude profile and the default launch flags for a new session. The flags come from `claude --help`, for example `--chrome`. A flag that needs a value lists the values it accepts. **Flags for automatic sessions** is a second list for the sessions PMOS starts for you, such as a scheduled brief. Such a session cannot answer a permission question, so it waits. Until you save a choice it starts with `--permission-mode=acceptEdits`, which ends the file-edit questions. A tool from a connector can still ask; allow it in your Claude settings or choose a looser mode here. The default profile is one setting for the whole workspace. PMOS keeps it on the server, so every browser, port and device starts a Claude session with the same profile. Choose it here or with "make … the default" in the New session form. Both change the same setting.
-- **Validate consent**: the consent of the current repository. Use its switch to turn it on or off. **Open Validate** opens the Validate page as a tab.
-- **People**: whether the morning brief keeps attendee names from the calendar for the current repository. It is off until you turn it on. Turning it off also hides the names recorded before.
-- **Online**: puts this workspace at your own address, such as `pmos.pm-os.app`, through a Cloudflare tunnel. Enter the public address, the tunnel name, your Cloudflare team domain, the Access audience (AUD) tag and your email, then turn on the **Online** switch. The workspace runs the tunnel and remembers the switch when it restarts. On your phone, open the address and sign in with Cloudflare Access (Google or an email code). The workspace does not ask for its token there. Only the computer that runs the workspace can change this section. A phone sees whether it is on. When a sign-in at the address is refused, this section names the check that failed, such as the email or the AUD tag. [REMOTE.md](../REMOTE.md) has the one-time Cloudflare steps.
-- **Theme**: Dark or Light.
-- **Updates**: the version of the workspace app and the version of the kit in the current repository. Press **Check for updates** at the top of the page to compare them with the latest published version of PMOS. This is the only time the workspace asks the internet for a version, and it asks only when you press. When a newer version is available, one button shows: **Update to** and the version. It updates every part that is older, in this order:
-  - **The kit** in the current repository, when it is older. This does what `npx create-pmos@latest --update` does in a terminal. It changes only the kit's own files under `pmos/` (skills, scripts, templates and guides). Your records in `state/`, `planning/` and `okf/product/` do not change. The last lines of the output show under the button. The changed files are under `pmos/`, which Sync treats as records, so Sync (or automatic sync) sends them with your other records. To read them first, look at `git diff pmos/` before you sync.
-  - **The workspace app**, when it is older. This does what `pmos upgrade` does in a terminal. The button asks you first. The workspace stops, installs the new version and starts again, and the page reloads when the new version starts. The reloaded page runs the new version's code: each start gives the page files a new address, so neither the browser nor the Online address's tunnel can keep the old ones. You do not need a terminal or a hard refresh. Sessions keep running in tmux. It works on the computer that runs the workspace and at its Online address, because the page comes back there after the restart. It also works on a phone or public address that signs in with a token set in `PMOS_TOKEN`, which the workspace keeps. When the workspace made its own token at start, the token changes on the restart, so the page refuses and says where to press it. When the workspace runs from a PMOS checkout, update it with `git pull` instead.
-  - **Testing an update before it is published.** In a PMOS checkout, run `bash scripts/build-local-package.sh`. It builds the package that a publish would build, in `~/.pmos-local-package`, with a version newer than the published one, and prints the command that starts the workspace on it. That command sets `PMOS_UPDATE_SOURCE` to the package on the same computer: its folder, or the `.tgz` that `npm pack` makes. Then **Check for updates** reads that package's version and does not ask npm, and both updates install that package. The Updates card names the package it checks, and the line under the buttons says "from the local package" after a check. There is no checkbox for this; the variable is the only switch. A checkout may update the app this way. When the path is wrong, the card says why and does not fall back to npm. Unset the variable, or set it to `npm`, to use the registry again.
+## Board and Intelligence
 
-  A new screen or a renamed menu comes with the workspace app, not with the kit.
-
-Your work is never in Settings. It is in Agenda, Initiatives, Board and Reports.
-
-## The agent dock
-
-The dock holds your terminals, documents, conversations, skills and web pages. It is open on Agenda. On every other place it is a 44-pixel rail at the right edge.
-
-- Press ⌘J (Ctrl-J), or the button on the rail, to open the dock. Press ⌘J again, or the fold button in the dock, to fold it to the rail.
-- The dock never opens by itself. A tab that opens while the dock is a rail waits in the dock until you open it.
-- The dock lists the sessions of the repository by initiative. A session is in the group of the initiative it is recorded on, or of its `initiative/<id>` branch. Then come **Not linked** (no initiative) and **Automatic** (anything you did not start yourself, for example a schedule, the day run, a note's summary or bullets, or a Jira push). **Automatic** is hidden until you press **Show automatic** at the foot of the list (or beside the group select in the strip). A session in front, or one held on a permission question, is always shown. An agent that has finished and reads "needs you" is hidden like the rest. Finished automatic sessions remove themselves a minute after a clean exit, and one with no output for 60 minutes is ended and removed. A failed one stays for a day. When a schedule starts a new run, it ends its previous run first, unless that run is still working or waits for your answer. Any session that has ended, also one you started, is removed after 7 days. Its conversation is kept when it ends. A session you started is never ended for you. When a session has been removed, its terminal tab closes too, also when the workspace was stopped for an update, so the tab does not come back as a row under **Open**. The setting is in `state/session-policy.json`: `finish` (true or false), `idleMinutes` (5 or more, or 0 for off) and `keepExitedDays` (1 to 365, or 0 to keep ended sessions). Then **Open** lists the tabs that are not sessions, for example documents and skills. Each one shows its title, what it is (for example PRD, Document or Web page) and its branch when it is not main. **✕** on an Open row closes the tab only. A terminal keeps running.
-- Each session row starts with a mark for its state: ● working, ◼ quiet, ◆ needs you, ◇ maybe blocked, ○ ended. Under the name, the row shows the state when the session is not working, the type of work when one is set, and the branch when it is not main and not the initiative's own branch. Running sessions come first and ended sessions last. Press the row to bring the session to the front.
-- Press the name of a group to fold it or open it. The number beside it counts its sessions. **Automatic** is folded while none of its sessions is running, because each run leaves an ended session. The group of the session in front always stays open, and the workspace keeps your choice for each group.
-- **⋯** and **✕** show on the row in front, on the row under the pointer and on the row with the keyboard focus. On a touch screen they always show.
-- Press **⋯** on a row to change the name, the initiative or the type of work.
-- Press **✕** on a row to end the session. The row asks "End “name”?". Press **End** or **Cancel**. When you end the last running session on its own working copy, the message offers **Remove working copy**. This removes the folder only. The branch stays. If the folder has unsaved work, the workspace keeps it and tells you why.
-- **＋ Session** at the top of the dock, or **＋** on an initiative, opens one sheet. Type a name, or leave it empty to name the session after the skill and the initiative. **For** is the initiative. **On** is where the session runs. **Automatic** uses the initiative's own working copy on `initiative/<id>` (made the first time), or the main tree when there is no initiative. You can also choose a branch that has a working copy, or **New branch…**. Then press **Blank session** (the CLI and model from Settings) or a skill. The session starts at once.
-- The icons at the top of the session list, under **＋ Session**, switch the sessions as a strip on top or a list at the side, set the dock size, and fold the dock. They stay in view when you scroll the list. On top, a select chooses the group, and each session of the group is a button. **＋** starts a session, and **✕** ends the session in front.
-- To make the dock wider or narrower, drag its left edge. With the edge focused, the left and right arrow keys change the width in steps. Double-click the edge to go back to the default width. The width is kept in this browser.
-- **Dock size** opens a menu of four sizes: Normal (the default width), Half the window, Two-thirds, and Whole window (focus). Choose one to set the dock to that size. The size is remembered in this browser. Dragging the edge clears the chosen size and sets a pixel width instead. Whole window (focus) gives the dock the entire screen; the place and the detail are hidden, and the dock stays full width on every place. Press Whole window again, or ⌘⇧J (Ctrl-Shift-J), to show the place. Folding the dock also ends focus.
-- **Scratchpad** in the bar at the bottom of the dock opens and closes the scratchpad. The pad keeps one note for each terminal session, and one for the repository when no terminal is in front. **Send to terminal** types the note into the session in front and presses Enter. It is available only when a terminal is in front. **Copy** and **Clear** act on the note.
-- The same bottom bar shows the title of the tab in front and a copy button that names what it copies: **Copy document** for a document, **Copy attach command** for a terminal.
-- A document tab has one bar. The words at its start say whether the file is saved on disk or has unsaved changes. The copy button beside them shows the file's Confluence or Google Docs copy (see [Edit a document in place](#edit-a-document-in-place)). **Changes**, **Revert** and **Save** show when there are unsaved changes. **Markdown** shows the whole file as markdown in one box; press it again to go back. A file that you cannot edit has **Source** in its place. **⋯** holds the rest: the reading width (full width, or lines of 72 characters), **Normalize line breaks** (it joins hard-wrapped paragraphs into one line each in the buffer; read the result in Changes, then save) and **Hide the outline and connections**. **Run scripts** shows on the bar for an HTML page that can run its own scripts.
-
-Folding the dock, or going to another place, does not touch your terminals.
-
-## Edit a document in place
-
-A markdown document is edited where you read it. The layout does not change when you edit.
-
-- Press a paragraph, a heading, a list or a table to edit it. That block shows as markdown, with the cursor where you pressed. The other blocks stay as they are.
-- **Esc** finishes the block. **Enter** at the end of a block starts a new block, and continues a list. **Backspace** at the start of a block joins it to the block above. The arrow keys move to the block above or below.
-- **Ctrl** or **⌘** with **B**, **I**, **E** or **K** makes the selection bold, italic, code or a link. The same four buttons show above the block. **Ctrl** or **⌘** with **S** saves.
-- Type `/` in an empty block to make it a heading, a list, a checklist, a quote or code.
-- Press a checklist box to tick it.
-- The frontmatter shows as **Properties**. Change a one-line value in its box. To change any other value, press **Markdown** and edit the file as text.
-- **+ Add a block** at the end of the document adds a paragraph.
-
-A block that you did not edit is saved exactly as it was. Nothing is saved until you press **Save**. **Changes** shows what will change, and **Revert** removes all unsaved changes.
-
-The rail on the right has two tabs:
-
-- **Outline** lists the headings. Press one to go to it.
-- **Connections** shows the files that this document is tied to, as a graph and as a list. A tie is a link, a frontmatter path, the initiative, the anchor or a decision id. Nothing is guessed from words. Press a file to open it. The list also shows the document's copies, and the findings of the last consistency check that name the document.
-
-To hide the rail, use **Hide the outline and connections** in the **⋯** menu.
-
-The copy button on the bar shows the document's Confluence (or Google Docs) copy, from the same record as the [Docs page](docs.md). It says which side is newer. Press it to see both sides and the first difference. **Use PMOS version** writes the document to the copy, and **Use Confluence version** writes the copy to the document. Each waits 5 seconds, during which you can press **Undo**. **Compare again** reads every copy and changes nothing. A copy never changes by itself. If the document has no copy, the button says **Add a copy**: paste the address of a Confluence page or a Google Doc. Save your edits before you sync, because a sync uses the saved file.
-
-## The detail
-
-The detail shows one item in full, for example an initiative or the profiles. It opens as a column between the place and the dock when you open an item. Press × at its top, or press Esc, to close it.
-
-## Questions
-
-When the workspace needs an answer from you, for example the name for a rename or a confirmation before a remove, it opens a sheet. A sheet has a title, the question, and two buttons: the one that does it and **Cancel**. Esc, the close button and a press outside the sheet all mean Cancel. The workspace never uses the browser's own dialogs.
-
-## Colour and size
-
-The workspace is neutral. A primary button is the text colour on the page colour, in both themes. The one brand colour marks the Agenda dot and the Agenda count, and nothing else. The bar, the dock and the bottom bar follow the theme; only a terminal stays dark. Corners are square. Controls are icons from one set, not text symbols. On a touch screen every field is 16 pixels, so the phone does not zoom when you tap it, and every control is at least 44 pixels high.
-
-On the console page (`/`), text on the blue accent and on a red badge is white in both themes. The page takes this colour from one token, so the colours stay the same when the theme changes.
+The Board shows initiatives by stage, with programs, a timeline and a list. Intelligence shows the goals from each product's OKR file. A panel on either page (an initiative, a program, a goal, the chat) can dock on the left or the right: drag its header to that half of the window, or press **Arrange** in its header. Each kind of panel stays on its side after a reload. [Programs on the Board](programs.md) and [Intelligence reads your OKR file](intelligence-okr-goals.md) explain them.
 
 ## Keys
 
 | Key | What it does |
 |---|---|
-| g t, g i, g b, g r, g d, g p | Show Agenda, Initiatives, Board, Reports, Docs or People. |
-| ⌘K (Ctrl-K) | Open or close the command palette. |
-| ⌘J (Ctrl-J) | Open or fold the dock. |
-| C | On the console page (`/`): open the [calendar popup](calendar-popup.md). Ignored while you type or while a sheet is open. |
-| ⌘⇧J (Ctrl-Shift-J) | Focus: give the dock the whole window, or show the place again. |
-| j, k | Move down or up the rows of the place. |
-| Enter | Open the row that has the focus. |
-| Space | Tick the row. Space never opens a row. On another button of the row, for example ⋯, Space presses that button. |
-| a | Do the main action of the row, when the row has one. |
-| x | Dismiss the row, when the row can be dismissed. |
-| Alt-Up, Alt-Down | Move the row up or down, when the row can move. |
-| Esc | Close the palette, then the detail. In the open dock, Esc closes the tab in front. After a click in the place or the detail, Esc does not close a tab. |
+| ⌘K (Ctrl-K) or / | Open Search from any page. A second press focuses the box. |
+| Esc | Close Search or the menu, then the Viewer. |
+| ↑ ↓ and Enter | Move through Search results and open one. |
 
 A key that you type in a field, or in a terminal, goes to the field or the terminal.
 
 ## On a phone
 
-A phone shows one panel at a time. The tabs at the bottom are **Agenda, Initiatives, Board, Docs and Agent**. Each tab has an icon and a short name. The Agenda tab shows how many things need you. Agent shows the dock, with your terminals. Reports is in the Board tab.
-
-Where a tab has a list, the list goes from top to bottom. Only the list scrolls. The bar at the top, the line above the list and the tabs at the bottom stay in place. The line above the list shows how many items the list has, for example "5 need you".
-
-Some tabs have a second view. Use the two buttons at the right of the line above the list to change the view:
-
-| Tab | The list | The other view | Not on a phone |
-| --- | --- | --- | --- |
-| Agenda | **Needs you**: one card for each thing that needs you. When your day is not prepared yet, the first card is **Prepare your day**. Press **Prepare my day** to start it, or **See the day** to open My day. | **My day**: your calendar, your goals and the jobs the agent does for the day. | The Repository / All repositories switch (use Repository in the bar). |
-| Initiatives | **Roadmap**: the initiatives on one ranked list, each with its lifecycle stage. | **All**: the list of every initiative. Press one to open it. | The title, New initiative, the count line and the drag grips. |
-| Board | **Board**: the items in the column you choose. Choose the initiative in the menu at the top, and the column with the column buttons. | **Reports**: read a report, or draft one. The Board tab stays lit. | The item count, the report title and Report schedules. |
-| Docs | **Out of sync**: one row for each document that needs you. | **All**: every document, in its groups. | The title. |
-| Agent | Talk to a session. | None. | The scratchpad bar when no terminal is in front. |
-
-When you open a terminal, the terminal fills the screen. The tabs at the bottom are not shown, so the output has the most space. The control keys stay at the bottom. Press Back to return to the tabs.
-
-Nothing is lost. New initiative is in the search. To move a card on the Roadmap, press its **⋯**. To set up report schedules or use the Timeline, use a desktop.
-
-The bar at the top has Back (when you are deeper than a tab), Repository, the search button, Sync (when the repository is not in sync, or has not fetched in the last 10 minutes) and Settings, which is the gear. The search button opens ⌘K, where you search and capture. At a tab, the bar shows no screen name, because the tabs at the bottom show where you are. When you open something over a tab, such as an initiative, a document or Settings, the bar shows its name. Settings opens over the current tab. Back returns to the tab.
-
-In the initiative sheet on a phone, the Breakdown shows the tree of items. It does not show the Board and Timeline switch or the list of starter items. Use the Board tab to see the items as a board.
-
-Every row has a visible ⋯ button. Every control is at least 44 pixels high. Nothing works only when you hover.
-
-You can have the same session open on your phone and your computer. A session has one size, so the screen you type in or tap last sets it. The other screen keeps showing the session and takes the size back as soon as you type in it.
-
-On an iPhone or an iPad, the terminal gets smaller when the keyboard opens, so the agent's prompt stays above the keyboard. Tapping the terminal does not zoom the page, and dragging at its top or bottom does not pull or reload the page. Swipe up or down on the terminal to scroll it, also inside Claude Code or any other program that uses the mouse. A swipe from the left edge of the screen is Safari's Back gesture and leaves the workspace. To avoid that, add the workspace to your Home Screen and open it from there.
-
-## The older layout
-
-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.
-
-Today, Validate, live notes, notes and Add repository open as a tab, not in place of the list. Choose the same one again and the existing tab comes to the front.
-
-Press ⌘K (Ctrl-K) to jump to anything: an initiative, a repository, an open tab, a session or a tool. Type to filter, use the arrow keys to choose, and press Enter. Esc closes it.
-
-In the older layouts, Today is a tab. It shows what needs you, with an action and a reason to dismiss each item, what is being prepared, and a Repository / All switch.
-
-If a part of a board has no data behind it, the board does not show that part, or it says that the data is not read.
-
-The `+` tile on the rail opens Add repository as a tab. The tab shows the scan of the folder before you add it.
-
-The list has a switch for Initiatives and Files. Choose Files to see the files of the current repository. Type in the filter to find a file. Press a file to open it in a tab.
-
-Under a terminal tab, the scratchpad holds a note that you can send to the terminal, copy or clear. The `+` session button opens a chooser for the new session. In a document tab, the rail on the right shows the document's outline and its connections.
-
-The list has a switch for Work, Today and All repos, a filter, and the groups Needs you, In progress and Done. The badge on a row names the step where the initiative is, for example `review`, `accept` or `build`.
-
-The detail shows the title, the summary, the chips, the blocker (when the initiative is blocked), the phases and the artifacts. Only the phase where the initiative is opens by itself, and the task where it is has a highlight. Press a phase to open or close it. Under each artifact are its link and sync controls.
-
-Each tab shows a dot, its title and, under the title, its initiative and its session. Press × on a tab to close it. The `+ session` button is at the right end of the tabs.
-
-If many tabs are open, the strip stays one row and scrolls sideways. Use the mouse wheel on the strip to scroll it. The tab in front always scrolls into view. Press `⇅ tabs at side` to show the tabs as a list down the left of the tabs column. In the list, each tab is one row, with its title, its initiative and session, and ×. The `+ session` button is at the top of the list, and the other controls are at the bottom. Press `⇆ tabs on top` to go back to the strip. The workspace remembers your choice in this browser. A phone and `?layout=legacy` always show the strip.
-
-### Navigation
-
-The first column holds the list of repositories. Under it is the list for the current mode. When you choose a repository, its initiatives appear there. 
-
-If you have many repositories, the repository list scrolls inside its own space. The list under it stays on screen.
-
-Drag the right edge of the column to change its width. Double-click the edge to restore the default width.
-
-### Detail
-
-The second column shows one item in full. Choose an initiative or the profiles, and its detail opens here.
-
-### Tabs
-
-The third column holds your terminals, documents, conversations and guide pages. Folding or resizing the other columns does not touch your terminals.
-
-### Open a file
-
-Press a file anywhere in the workspace to open it in a tab. Any text file opens, whatever its extension.
-
-- **Markdown** opens as a document that you edit in place. See [Edit a document in place](#edit-a-document-in-place).
-- **JSON** opens pretty-printed. If the file is not valid JSON, the tab shows the text as written and says why.
-- **JSONL** opens as numbered records, one for each line. The tab marks a line that is not valid JSON.
-- **HTML** opens as the page it is. Press **Source** to see its source. The page cannot run scripts and cannot load anything from the network. To run the page's own scripts, press `run scripts`. This grant is for this tab only. The page can then run the scripts written inside it, but it still cannot load anything from the network, cannot load a script from another location, and cannot read the workspace. Press `scripts running — stop` to stop the scripts. Closing the tab also removes the grant.
-- **Other text** opens as numbered source lines. Spreadsheets, PDFs and images open in their own views.
-
-A tab for a file that is not markdown is read-only. It has no Markdown, Changes or save control, because the workspace saves only markdown.
-
-If a file cannot be shown, the tab says why. The reasons are: the file is binary, it is larger than 2 MB, it is not valid text, or it is outside the workspace.
-
-### The rule for where things open
-
-A list or a directory opens in the navigation column, under the repository list. A detail opens in the detail column. A file-like row opens in a tab, as any document does.
-
-| Item | Kind | Opens in |
-|---|---|---|
-| Initiatives | list | navigation |
-| Validate | list | navigation |
-
-What a row in a list opens:
-
-- A row in Initiatives opens the initiative in the detail column.
-- Validate opens as a tab, beside your terminals.
-- A Knowledge, Memory or Guide result in ⌘K opens a document in a tab, or a memory entry in a sheet.
-
-### Folding
-
-On a desktop screen, the list and the detail each have a `⟨` button. The list's button is at the right of `+ New initiative`. The detail's button is at its top right. Press it to fold that column to a thin strip. Press the strip to open the column again. The rail does not fold.
-
-In the older layout:
-
-- Choose the arrow in the header of the list to fold it to one line under the repositories. Choose the line to open it again.
-- Fold the navigation column to a thin strip. The list folds with it. Choose the strip to open it again.
-- Fold the detail column to its strip in the same way.
-
-The workspace remembers which columns are open and how wide the navigation column is.
-
-### Light theme
-
-In the light theme, the whole workspace is light: the top bar, the dock, the tab strip and the bar under the tabs follow the theme. Only the terminal stays dark, because a terminal is dark in both themes.
-
-### On a phone
-
-In the older layouts, a phone also shows one panel at a time. The tabs at the bottom move between them.
+At phone width, Home's list is the page. A row opens its item over the list, with a back bar. The menu button is at the bottom right. Search fills the screen. The Viewer fills the screen, and ← at the first item closes it.