Start here

OMP work continues through more than a transcript. A conversation can be reopened while its workspace has changed. A remembered preference can return after live context was cleared. A tangent can finish its first job yet remain available for another conversation. A tool can be enabled but denied for a particular call, or run without asking under a policy the visible mode alone does not explain. An extension can keep a selection across a session switch without having saved that selection anywhere.

These are not contradictions. They are different state and authority boundaries.

This workbook teaches one operating habit: name the target, identify the state and authority involved, and check the result at the layer where the effect should occur. That habit connects returning to yesterday’s work, retaining useful knowledge, coordinating another agent, understanding a tool decision, building a capability, and preparing material for review.

Read as one book

The five parts form a progression:

All 65 original catalogued source reading sections remain in full, alongside the complete new permissions part. The original code, exercises, failure cases, references, and evidence chapters remain part of this book. The retained Orientation chapters establish each source’s scope; the part introductions explain how that material fits together. Repeated warnings are not silently discarded: a warning about memory deletion, a warning about conversation reset, and a warning about widening tool permission protect different boundaries.

Read front to back for the complete progression, or choose a reading path for a concrete problem. The connection chapters bring the parts together without replacing their detailed contracts. The shared glossary explains terms that recur with different meanings.

Prerequisites and practice modes

You can read the entire book without an OMP installation, account, credentials, or provider access.

The combined example archive preserves the supplied directory structure and contains the Extension and Continuity examples, plus the Permissions case fixtures. Permissions practice uses Approval Desk, Dispatch Desk, and Boundary Desk. These three files are inert cases, not a live simulator or configuration to install. Memory’s practice material is in its chapters and interactive lab; Tan’s Lantern Library fixtures are printed in its chapters. There is no invented Memory or Tan download package.

A disposable directory is useful data separation, not an operating-system sandbox. Likewise, --no-extensions, an in-memory session, or a clean profile does not establish that every startup activity is offline. A read tier is a declaration, not a universal promise of read-only behavior or zero network activity. The source chapters explain the narrower controls they actually use.

Keep the input surface attached to the instruction

The original captions identify where an example belongs. Preserve that distinction when reading or copying it:

• Terminal shell: executable launches, configuration inspection, and fixture inspection, only under the stated prerequisites and owned scope.
• Main’s OMP composer: native slash commands and ordinary requests to Main.
• Focused Tan chat: plain-language messages to the verified agent, with steering and follow-up behavior determined by its current state.
• Model tool interface: schema-shaped arguments for a tool that actually exists in that session. A JSON argument object is not a terminal command.
• Extension or SDK code: source to inspect or load through its documented host, not text to paste into a conversation.
• Permissions case data: fictional declarations, arguments, responses, and shell-shaped strings to classify. Do not execute those strings, submit those fictional calls, or install the cases as settings.
• Workbook browser controls: navigation, disclosures, authored illustration or milestone selection, copying, and self-reported lesson ticks only.

Copying a snippet does not execute it. A slash command is not automatically a model-callable tool. A method documented for a command context is not made safe inside a tool by a type cast. Selecting an approval milestone in the browser does not approve any real OMP call.

Fiction is the default learning environment

Cedar, Lantern Library, Lantern Board, Cedar Library, Harbor Notes, Seed Desk, Review Desk, Field Notes, and the permissions part’s Cedar Seed Library are teaching fixtures, not a shared real project. Similar names do not establish shared files, sessions, or evidence. In particular, Tan’s Lantern Library and Continuity’s Lantern Board are separate stories, and the recorded Decision Desk checks used a separate Cedar Library fixture. The permissions recording tools are not the Seed Desk reservation extension, despite the seed-library theme.

Use the supplied fiction to predict outcomes, inspect complete records, and understand refusals. Source chapters retain optional real-use prompts and service-integration examples, but their inclusion is not a request to execute every snippet. Completing this unified reading route requires no real memory disclosure, authentication experiment, provider inference exercise, live upload, privileged-broker exercise, or destructive session operation. Do not use /drop, /memory clear, or /memory reset as workbook cleanup. Sharing remains a decision exercise, not an upload exercise. A permissions refusal is not a request to change personal settings or switch to yolo.

Some source checkpoints describe actual operations a reader might later perform. Leave those unchecked if you only read or simulated them. Understanding an operation and having verified it in a real session are different accomplishments.

Read evidence at its stated strength

The book distinguishes four kinds of statements:

• Recorded observation: a supplied report describes a completed check under named conditions.
• Source-backed behavior: the source workbook traces a contract to the implementation or types it received.
• Exercise or expected checkpoint: a result to test or reason about, not a newly observed result.
• Editorial connection: an explanation or operating recommendation derived from several chapters, not a new API guarantee.

The sources describe custom snapshots. Reports that name omp/18.0.7 do not establish parity with every release carrying that version. Memory’s Mnemopi settings are a recorded configuration snapshot, not a statement about your machine. The permissions source and new evidence are dated 30 August 2026; earlier reports remain historical.

Permissions retains two runs of existing focused tests—96 passes across four files, then 105 across two—plus a separate Main-executed private report of 46 fictional scenarios and an isolated configuration CLI observation. The 201 passing existing tests are not one newly rerun aggregate of the earlier books. Combining the manuscripts does not rerun their tests, inspect a reader’s databases or policies, or turn SDK, controller, RPC helper, recording-adapter, or terminal-emulator evidence into physical TUI proof.

Reading with a browser agent

The unified reading interface is window.ompWorkbook, version 1, with tutorial-only scope. Consult its live discover() and inspect() results and the browser contract for exact controls and availability; do not construct control IDs from labels. It cannot observe or control a real OMP process or resolve that process’s permission policy.

Unified lesson ticks use omp-workbook-checklist-v1 in browser storage. They record the reader’s report, not a test result. The separate Memory lab retains window.memoryTutorial and its own checklist storage on that lab page only. Its API is not an alias for the unified reading interface.

A navigation receipt reports a navigation request, not a successfully loaded destination. Inspect the destination document after navigation; a wait on the old document cannot follow it. For the complete distinction between tutorial observations and OMP evidence, read Match each claim to the layer that was checked.