create-egregore 0.21.6 → 0.22.0

package/runtime/pi/.claude/skills/view/SKILL.md

@@ -0,0 +1,438 @@
+---
+name: view
+description: "Generate a branded HTML artifact from Egregore data (quest, handoff, activity, board, network, or any document) and open it in the browser. Use for /view, 'render this', or 'show me visually'."
+---
+
+Generate a branded HTML artifact from Egregore data and open it in the browser.
+
+Works in both connected and local mode — resolves data from memory files, not the graph.
+
+## When to invoke
+
+User says: "show me visually", "render this", "view as artifact", "open in browser",
+"make this readable", "generate artifact", "show me [quest/handoff/plan]", "/view"
+
+Not this: terminal formatting → just format in markdown · dashboard → `/dashboard`
+
+Arguments: $ARGUMENTS (Optional: artifact type and/or name, or a file path)
+
+## Runtime source boundary
+
+Resolve deictic requests from the current conversation before organizational
+retrieval. When `this`, `that`, `it`, or `the above` unambiguously refers to
+the single artifact just created, accepted, or shown, reuse its full content
+already in context and stage it verbatim. If that content is collapsed or the
+prior receipt supplies only a canonical path, open that exact path once through
+`bin/search.sh open`; do not run `bin/search.sh query` to rediscover a known
+artifact.
+
+Resolve organizational sources from the attached authorized
+`EGREGORE_ORG_CONTEXT_V1` block first. Do not repeat its retrieval or reopen
+its already opened sources. When the requested source is absent, run one
+Runtime query and open the selected canonical file through
+`bin/search.sh open`; do not use raw `ls`, `find`, or graph traversal as an
+authorization bypass. Local rendering is the default. Publishing or replacing
+a stable hosted view requires an explicit `SHARE` request and checkpoint.
+Never publish from an ordinary view request.
+
+## Loom routing
+
+Claude Code: use this Loom routing section. Other harnesses continue with
+Rendering mode below.
+
+Skip this section when the prompt contains `LOOM-EXECUTOR`; execute the
+authorized render directly and never re-delegate.
+
+Explicit `--compose`, designed/flagship, or client-facing requests remain
+main-loop-only: render inline, then print
+`bash bin/loom.sh footer view --override` and mark telemetry as an override.
+For the deterministic renderer:
+
+1. Resolve the route: run `bash bin/loom.sh route view` and read the JSON line it prints. When `bin/loom.sh` is not
+   present (Loom is internal-only and does not ship in the OSS distribution),
+   skip route resolution and the footer entirely and follow the script route
+   below — it is the framework default and needs no Loom.
+2. **Script route (`"mode": "script"` — the framework default).** Judgment
+   stays in the main loop: resolve what the user means into a type and source
+   (the Resolution logic below). Then run the mechanics with no model in the
+   loop — one call, which stages the source through the Runtime read boundary,
+   serves repeat views from a content-addressed cache, renders, and opens:
+   `bash bin/view-render.sh <type> <memory/...-or-file> [-- --brief <path>]`.
+   Print its output verbatim, then `bash bin/loom.sh footer view`. Do not
+   spawn a subagent, re-open the source yourself, or re-run retrieval for the
+   render. If the script exits non-zero, report its error; only a composition
+   or interaction need justifies taking over inline.
+3. For an inline route, continue below in the main loop.
+4. For a delegate route (org override), delegate only when available and
+   permitted in this session; otherwise continue inline. When delegating,
+   spawn `loom-executor` at the returned tier with `LOOM-DECISION-ID`, `LOOM-EXECUTOR: Execute
+   .claude/skills/view/SKILL.md`, the user's exact arguments, and the attached
+   `EGREGORE_ORG_CONTEXT_V1` block verbatim; print its final output, then
+   `bash bin/loom.sh footer view`. On `LOW_CONFIDENCE:` take over inline.
+5. Emit telemetry best-effort from the driver:
+   `bash bin/telemetry.sh emit "command" '{"command":"view","routed":true}' 2>/dev/null &`.
+
+Loom transports the authorized context; it never grants new read or SHARE
+authority. The minion workflow is unrelated to this render route.
+
+## Rendering mode
+
+Use the packaged deterministic renderer by default, driven through
+`bin/view-render.sh` — rendering is mechanical, so no model belongs in that
+path. Run inline composition only when the user explicitly requests it. A
+normal “view/open/render this” uses the script route without duplicate
+retrieval. A repeat view of unchanged content reports
+`(served from render cache)` — that is expected, not staleness: the cache key
+is the content bytes, the renderer, and the arguments.
+
+## Supported artifact types
+
+- `quest` — renders quest markdown from `memory/quests/`
+- `handoff` — renders handoff markdown from `memory/handoffs/`
+- `activity` — renders live team activity dashboard (no file needed)
+- `board` — renders the typed live project-board surface (interactive editor with 5 tabs: Activity / Priority / Person / Timeline / Done). Publishing the stable hosted board is a separate explicit action.
+- `network` — renders people/relationship network (no file needed)
+- `document` — renders any markdown file with branded styling (auto-detected fallback)
+
+## Resolution logic
+
+The key job of `/view` is resolving what the user wants to see into a file path. This must work without a graph.
+
+### 1. Parse the arguments
+
+- `/view quest artifact-generation` → type=quest, name=artifact-generation
+- `/view handoff oss-security-audit` → type=handoff, name=oss-security-audit
+- `/view activity` → type=activity, no file needed
+- `/view board` → type=board, typed live surface; no source path resolution
+- `/view network` → type=network, no file needed
+- `/view artifact-generation` → no type specified, search all types
+- `/view memory/knowledge/decisions/some-decision.md` → direct file path
+- `show me the security audit visually` → extract keywords, search
+
+### 2. Resolve the file
+
+**Direct canonical file path**: If the argument names `memory/...`, open it
+through `bash bin/search.sh open "memory/..."` into a temporary render source.
+A denied or missing source stops resolution; never pass the raw canonical path
+to the renderer or fall through to an unchecked filesystem read. An explicit
+non-memory path inside the current repository may be rendered as a repository
+document, but it is never treated as organizational memory.
+
+**Quest, handoff, document, or auto-detected name**: Prefer the best matching
+canonical source and opened content already present in
+`EGREGORE_ORG_CONTEXT_V1`; stage that content as a temporary render source
+without reopening it. Otherwise run one ranked call, optionally including the
+requested type in the concept, then open only the selected result into the
+temporary render source:
+
+```bash
+bash bin/search.sh query "<artifact name and optional type>" -n 6 --compact --context-packet
+bash bin/search.sh open "<selected memory/... path>"
+```
+
+Claude Code: `--compact --context-packet` keeps the ranked evidence out of the
+visible transcript — the resolution query must never print result blocks
+before the render. Pass the selected source to the renderer script as its
+`memory/...` canonical path, never as an absolute filesystem path.
+
+Infer the renderer type from the selected canonical path. If several results
+are genuinely ambiguous, show the short choices rather than scanning the
+repository again.
+
+**Activity**: No file resolution needed — runs `bin/activity-data.sh` live.
+
+**Board / Network**: Use only the renderer's typed Runtime-backed live surface;
+do not pre-scan or pre-open memory files.
+
+**Auto-detect type** (no type specified): infer `quest` or `handoff` from the
+authorized result path; everything else is `document`.
+
+### 3. Generate and open
+
+**On the script route, `bin/view-render.sh` owns everything in this section**:
+it resolves the packaged renderer locally (checked-out
+`packages/egregore-artifacts` with dependencies first, then the instance's
+managed renderer, then an installed `egregore-artifacts` on PATH;
+never `npx`, never a registry fetch), stages complete `memory/...` documents
+through the existing authorized `Runtime.open_source` adapter (ordinary model
+evidence reads remain bounded), serves unchanged content from the content-addressed
+render cache, invokes the renderer exactly once with `--output`, and opens the
+browser. Call it once with the resolved type and source; do not re-implement
+these steps inline. The commands below describe what the script does and are
+the inline fallback only when the resolved route is `inline`.
+
+**Design trace (documents).** A `document` render should follow the design
+trace, not ship bare: auto-walk the UGI synthesis graph from the document's
+substance (five stage ids — objective · audience · register · palette ·
+grammar; option ids and auto-walk rules in
+`packages/design-system/generative-ui/skill/SKILL.md`), resolve the brief, and
+pass it to the renderer:
+
+```bash
+bash bin/node-run.sh --input-type=module -e "
+import { resolveBrief } from './packages/design-system/generative-ui/resolve-brief.js';
+import fs from 'node:fs';
+fs.mkdirSync('tmp', { recursive: true });
+fs.writeFileSync('tmp/view-brief-{slug}.json',
+  JSON.stringify(resolveBrief(['{objective}','{audience}','{register}','{palette}','{grammar}'])));
+"
+bash bin/view-render.sh document <memory/...-or-file> -- --brief tmp/view-brief-{slug}.json
+```
+
+Picking the five ids is judgment and stays in the main loop; the brief file
+rides into the render through `--` and participates in the cache key.
+
+Pick the five ids from the substance, one line of judgment each (e.g. a
+strategy prep doc → decide · operators · editorial · ledger · decisive; a
+public explainer → persuade · newcomer · marketing · ledger · quiet). For the
+palette, use `ledger`, the registry default pair (`sovereign`), unless the
+content has a stated reason for another registered pair; a palette with no
+registered pair is never a default pick. The brief drives palette + grammar
+treatment; the designed layout (nav · hero · anchored sections) renders
+regardless. If the checked-out generative-ui layer is unavailable, render
+without `--brief`; never fetch it or block on the trace.
+
+The deterministic renderer already owns its light/dark theme contract. Do not
+invoke or reread a separate visual-theme skill for an ordinary render. Apply
+the Dark Mode contract only while authoring composed HTML or changing renderer
+code.
+
+### Composition path (`--compose`) — band 5, main-loop only
+
+The template above is the **floor**. `--compose` is the **ceiling**: the design
+trace at full depth means COMPOSITION, not pass-through (D6 free-generative band
+— how the reference pages were made). The template renderer can never reach it;
+composition is the frontier model authoring the page from the substance. This
+path is what makes that reachable from the command instead of only by accident.
+
+This path fires only on explicit cues: `--compose`, "compose / make it
+presentable / client-facing / flagship / with the design trace / use the design
+trace / designed artifact / band 5". **When the user names "the design trace,"
+they mean this composed ceiling — never the floor.** Otherwise use the local
+deterministic renderer.
+
+**Technical documents compose too — in a different register.** A spec, RFC,
+protocol, architecture doc, API reference, evaluation report, or postmortem is
+flagship and gets the full chrome, but it does **not** get editorial voice. See
+step 4 below: the register decision comes before any content is written, and
+picking wrong is the single most common way a composed render lands badly.
+
+**Procedure (run inline — never delegate; see the compose note in Loom routing):**
+
+1. Read the source document in full. Then read what people have said they
+   like in generated interfaces and keep it as context: words to consider,
+   never a template to copy. `{task}` is a few words naming this work:
+
+   ```bash
+   bash bin/genui.sh taste --task '{task}' --form view
+   ```
+
+2. Start from the scaffold: `.claude/skills/view/compose-scaffold.html` (copy it;
+   it carries the chrome — fonts, sticky nav, theme toggle, contours — and a
+   documented component kit). You fill content; you do **not** rebuild the
+   chrome or invent colors.
+3. Walk the UGI graph for the register/palette/grammar (as above) and stamp the
+   manifest `register`/`grammar` + the footer trail. For the palette, use the
+   registry default pair (`sovereign`) unless the content has a stated reason
+   for another registered pair. The scaffold predates the registry: its theme
+   blocks are the `meridian` pair (`vellum`, `nocturne`) plus an older `loam`
+   block, and its header note to leave them in place no longer holds. Take the
+   chosen pair's two theme blocks from the first of these files that exists:
+   - `packages/design-system/dist/egregore-design.css` (the source repository)
+   - `packages/egregore-artifacts/lib/vendor/design-system/dist/egregore-design.css`
+   - `lib/vendor/design-system/dist/egregore-design.css` inside the installed
+     `egregore-artifacts` package that `bin/view-render.sh` runs
+
+   Replace all three scaffold blocks with them; match the `<html>` attributes,
+   the manifest `pair` and `resolvedTheme`, and the toggle's theme ids and
+   label to that pair; and point the scaffold's meridian-only names
+   (`--prussian*`, `--brass*`, `--teal`, `--rose`, `--contour`) at role tokens.
+   If none of the three files exists, keep the scaffold's `meridian` blocks and
+   say so in the report.
+4. **Decide the register FIRST — editorial or technical.** This governs every
+   sentence you then write, and it is not a style preference; it is what the
+   document *is*. Ask: does a reader come here to be *persuaded of a view*, or
+   to *look something up and implement it*?
+
+   | | **Editorial** | **Technical** |
+   |---|---|---|
+   | Documents | strategy · prep · briefing · explainer · analysis · narrative recap · pitch | spec · RFC · protocol · architecture · API reference · evaluation report · runbook · postmortem |
+   | Headings | **statement titles** — the section's *finding* as display copy ("Most of the zoom-out is already decided.") | **descriptive, numbered** — the section's *name* ("3.3 Toponym and cultivar collision") |
+   | Hero | two-tone `Lead. <em>accent phrase</em>` + italic standfirst | plain title + a `.meta` grid (version · date · author · depends-on) |
+   | Prose | argues, lands a point, carries voice | states, qualifies, cites; declarative and neutral |
+   | Opens with | the claim | Abstract, then Scope |
+   | Decisions | `.hl` / `.readout` — the thing to land | explicit `Decision:` blocks, individually citable |
+   | Tables | `.sumtable`, status matrices | numbered with `<caption>` ("Table 2 — …") so prose can reference them |
+   | Never | bury the finding in a neutral heading | editorialize a heading, or assert without the measurement behind it |
+
+   Signals for technical: numbered sections, a version field, "spec"/"protocol"/
+   "requirements" in the title, code blocks carrying invocations, tables of
+   measurements, a References section. **When the document is something someone
+   will implement from, choose technical.** Editorial voice on a spec reads as
+   unserious and buries the lookup value — that is the failure mode this table
+   exists to prevent.
+
+   Stamp the choice into the manifest `register` and the footer trail
+   (`editorial` / `technical`, with a matching grammar such as `decisive` or
+   `specification`).
+
+5. **Transform, don't mirror** — in the chosen register. Never reproduce the
+   markdown structure verbatim; pick a component per section from the kit by
+   what the content *is*:
+   - `.ledger` for Q→A pairs · `.tagcard` for named claims · `.claims` for
+     numbers/stats · `.panels`+`.verdict-band` for option sets · `.hl` for the
+     one thing to land · `.steps` for sequences · `.feat` for capability+status
+     rows · `.threads` for decision lists · `.gap` for negatives · `.sumtable`
+     with `.dot`s for a status matrix · `.readout` for the honest bottom line
+   - technical renders lean on captioned tables, `Decision:` blocks, numbered
+     rationale lists, and `.note`/`.note.caution` for limitations and hazards;
+     they use `.hl`/`.readout` sparingly and never as a substitute for a heading
+   - **Highlights: no side stripes.** Never draw a coloured bar down one side
+     of a box. In the scaffold, `.hl` is the quiet status panel (6% tone tint,
+     1px tone hairline, 12px radius) whose `.k` label carries the tone's shape:
+     ● for the plain `.hl`, ▲ and ■ for its warn and critical variants.
+     `.readout` is the key point: bigger type, no box. Typed renders take the
+     same treatments from the kit's recipe classes
+     (`packages/egregore-artifacts/lib/recipe.js`): `.eg-mark` for a marker
+     under the words, `.eg-margin` with an `.eg-label` for a label in the
+     margin, `.eg-quote` for a quote with a hanging opening mark, and
+     `.eg-panel` with a shaped `.eg-label` for status
+   - **transformation in technical register means structure, not voice** — split
+     prose into tables, number the rationale, surface the decisions; do not
+     rewrite the author's claims into slogans
+   - nav links: one per composed section, to its `id` anchor
+6. **Never inline a hex in content** — every theme-sensitive color is a
+   `var(--token)`, or the toggle breaks dark mode. The kit already obeys this.
+   Verify before opening: every `var(--x)` used must be defined in **both** of
+   the chosen pair's theme blocks (for `sovereign`: `[data-theme="ledger"]` and
+   `[data-theme="bedrock"]`), or dark mode breaks silently on that element.
+7. Write to `/tmp/egregore-artifacts/composed-{slug}.html` and open directly
+   (`open <path>`), then report the path + `Renderer: composed (band 5, inline)`.
+
+Composition is judgment, not a script — the scaffold is the vocabulary, the
+substance decides the sentence. When `--compose` is absent, use the fast
+template path below.
+
+For typed artifacts with a file:
+```bash
+bash bin/view-render.sh <type> <memory/...-or-file>
+```
+
+For auto-detected (just a file path):
+```bash
+bash bin/view-render.sh document <memory/...-or-file>
+```
+
+For activity (no file — live surfaces are never cached):
+```bash
+bash bin/view-render.sh activity
+```
+
+**For an explicitly requested publish:** local render/open is already complete.
+Authorize `SHARE` for the exact staged artifact and show a Publish / Cancel
+checkpoint containing the organization, destination, title, source, and
+whether a stable URL will be replaced. After approval, invoke the Runtime
+publication adapter once. `/view` does not inspect hosting configuration or
+manage publication transport itself. If no Runtime publication adapter is
+available, keep the local artifact and say publishing is unavailable rather
+than falling back to a legacy script. Notification consent remains separate.
+
+
+### 4. Report
+
+Report the exact HTML path returned by the renderer or written by composition;
+do not infer a filename from the examples below.
+
+```
+✓ Artifact opened in browser
+  File: /tmp/egregore-artifacts/{type}-{name}-{ts}.html
+```
+
+Only after an approved SHARE action returns a URL, append:
+```
+◆ {receipt.url}   (use the exact URL returned by the approved publication)
+```
+Read `org_slug` from `egregore.json`.
+
+## Fallback
+
+If the local renderer is unavailable, report that the instance renderer needs
+installation or repair. Do not install or fetch software implicitly.
+
+## Ambiguity handling
+
+If the name matches multiple files, ask with a structured question when available and permitted in this session; otherwise ask in plain text:
+```
+Found multiple matches for "security":
+1. handoffs/2026-03/31-cem-oss-security-audit.md
+2. quests/oss-security-review.md
+Which one?
+```
+
+If no matches found, **fall through to synthesis mode** (see below).
+
+## Synthesis mode
+
+When the input is a prompt or topic rather than a file name — or when file resolution finds nothing — synthesize an artifact from multiple sources.
+
+1. **Reuse authorized evidence** — start from `EGREGORE_ORG_CONTEXT_V1`. If it
+   is absent or insufficient, run Runtime Observe once through
+   `bin/search.sh query`; open only a selected returned canonical source through
+   `bin/search.sh open`. Never scan `memory/`. Read repository files only when
+   the user explicitly asked to synthesize codebase material.
+2. **Write a temporary markdown file** — synthesize only the authorized
+   evidence into `tmp/view-synthesized-{slug}.md`. When the
+   attached context already contains opened content, stage that content without
+   reopening its canonical source.
+3. **Render it** — `bash bin/view-render.sh document tmp/view-synthesized-{slug}.md`
+4. **Report** — same as normal: `✓ Artifact opened in browser`
+
+This is the default fallback — don't ask the user if they want synthesis. If `/view auth architecture` doesn't match a file, just do the research and render it.
+
+**When to synthesize vs. when to say "not found":**
+- Prompt is a topic/question ("auth architecture", "how does onboarding work") → synthesize
+- Prompt looks like a filename that should exist but doesn't ("my-missing-doc") → say not found
+- Use judgment — if the user clearly expects a specific file, don't synthesize a guess
+
+## Examples
+
+```
+> /view quest artifact-generation
+
+✓ Artifact opened in browser
+  File: /tmp/egregore-artifacts/quest-artifact-generation.html
+```
+
+```
+> show me the security audit visually
+
+Resolving "security audit"...
+  Found: memory/handoffs/2026-03/31-cem-oss-security-audit.md
+
+✓ Artifact opened in browser
+  File: /tmp/egregore-artifacts/handoff-31-cem-oss-security-audit.html
+```
+
+```
+> /view memory/knowledge/decisions/auth-redirect.md
+
+✓ Artifact opened in browser
+  File: /tmp/egregore-artifacts/document-auth-redirect.html
+```
+
+```
+> /view activity
+
+✓ Artifact opened in browser
+  File: /tmp/egregore-artifacts/activity-2026-04-06.html
+```
+
+```
+> /view auth architecture
+
+No file match — synthesizing from codebase...
+  Reading: api/main.py, api/auth.py, api/services/storage.py, ...
+
+✓ Artifact opened in browser
+  File: /tmp/egregore-artifacts/document-auth-architecture.html
+```

package/runtime/pi/.codex/hooks.json

@@ -14,6 +14,17 @@
       }
     ],
     "PreToolUse": [
+      {
+        "matcher": "Bash|exec_command|shell_command|shell|write_stdin|apply_patch|Edit|Write|Read|view_image",
+        "hooks": [
+          {
+            "type": "command",
+            "command": "h=\"$(git rev-parse --show-toplevel)/bin/boundary-hook.sh\"; if [ -f \"$h\" ]; then exec bash \"$h\" codex; fi; echo 'Environment isolation: boundary guard missing (bin/boundary-hook.sh) — run /update, then restart the session. Every action is blocked until the guard is back.' >&2; exit 2",
+            "timeout": 10,
+            "statusMessage": "Checking Egregore instance boundary"
+          }
+        ]
+      },
       {
         "matcher": "Bash|exec_command|apply_patch|Edit|Write",
         "hooks": [

package/runtime/pi/.codex/skills/dark-mode/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: dark-mode
-description: 'Use when authoring or modifying browser-rendered visual output: HTML, CSS, React SSR, artifact templates, markdown renderers, design tokens, themes, or composed pages. Do not invoke for an ordinary /view render—the checked-in renderer already owns its theme contract. The load-bearing rule is that theme-sensitive colors must be emitted as `var(--token)`, never resolved inline hex.'
+description: 'Use when authoring or modifying browser-rendered visual output: HTML, CSS, React SSR, artifact templates, markdown renderers, design tokens, themes, or composed pages. Do not invoke for an ordinary /view render—the checked-in renderer already owns its theme contract. The load-bearing rule is that theme-sensitive colors must be emitted as `var(--token)`, never resolved inline hex; the colors themselves come from the design system registry.'
 ---
 
 <!-- generated-by: bin/codex-sync-skills.sh -->

package/runtime/pi/.codex/skills/records/SKILL.md

@@ -0,0 +1,29 @@
+---
+name: records
+description: 'View or change your session records, hold the current session, redact a past record, record past sessions from this machine, and close or file the open items records carry.'
+---
+
+<!-- generated-by: bin/codex-sync-skills.sh -->
+
+# Egregore records Adapter
+
+This adapter runs the canonical Egregore workflow for `records`. Its one
+maintained body is `.claude/skills/records/SKILL.md`; read that file completely and follow it here.
+
+Use the project shell and filesystem directly. Do not invoke Claude Code
+commands. Translate interactive choices to structured Codex question tooling
+when it is available; otherwise render compact numbered choices with an
+`Other:` option and wait for the user.
+
+1. Read `.claude/skills/records/SKILL.md` for the workflow details.
+2. Run the referenced `bin/` scripts directly from Codex.
+3. Treat graph and publish steps as best-effort unless that workflow explicitly
+   says they are required.
+4. For every external notification, follow
+   `.claude/context/notification-consent.md`: plan without sending, then show
+   a separate exact Send / Edit / Cancel checkpoint. Never infer notification
+   consent from the workflow request or a batch approval.
+5. Keep local-mode behavior filesystem-first and avoid graph or notification
+   calls when `egregore.json` declares `"mode": "local"`.
+6. Never call the deprecated `egregore-handoff` CLI for Egregore project
+   handoffs.

package/runtime/pi/.codex/skills/summon/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: summon
-description: 'Design and launch a persistent agent (a spirit) that runs on a schedule or watches for conditions, via adaptive questioning that produces a reviewable spec before launch.'
+description: 'Reuse, design, and launch Egregore spirits. Review available recipes and current host permissions, then start authorized on-demand work or design a scheduled process for an available scheduler.'
 ---
 
 <!-- generated-by: bin/codex-sync-skills.sh -->

package/runtime/pi/.codex/skills/view/assets/compose-scaffold.html

@@ -6,7 +6,7 @@
   How to use: copy this file, then
     1. fill <title>, the manifest `register`/`grammar`, nav brand + links,
        the hero (series / h1 / standfirst / chips), and the footer.
-    2. replace the <!-- COMPONENTS: … --> region with composed sections built
+    2. replace the COMPONENTS comment region with composed sections built
        from the component kit below — do NOT mirror the markdown; transform
        the substance into the grammar (statement titles, panels, cards, …).
     3. every theme-sensitive color MUST be a var(--token). Never inline hex
@@ -24,9 +24,9 @@
 <script type="application/json" id="egregore-design-manifest">{"system":"egregore-design-convention","version":"0.3.0","lineage":"meridian","pair":"meridian","mode":"auto","resolvedTheme":"vellum","target":"browser","register":"__REGISTER__","grammar":"__GRAMMAR__","composed":true}</script>
 <style>
 :root{--serif:"Fraunces",Georgia,serif;--sans:"Hanken Grotesk",system-ui,sans-serif;--mono:"IBM Plex Mono",ui-monospace,monospace;--ease:cubic-bezier(.22,.61,.36,1)}
-[data-theme="vellum"]{--paper:#eceef2;--paper-2:#e2e6ec;--card:#f8fafc;--ink:#15212e;--ink-soft:#4d5a68;--ink-faint:#8492a0;--line:#cbd4de;--line-soft:#dde3ea;--prussian:#2c4a6b;--prussian-bright:#3f74ad;--brass:#9a7521;--brass-bright:#c0962f;--teal:#1d7a6e;--rose:#a8493e;--t1:#9a7521;--t1-bg:#f3ead0;--t2:#1d7a6e;--t2-bg:#ddefea;--t3:#a8493e;--t3-bg:#f4ddd7;--contour:#bcc6d2;--shadow:0 1px 2px rgba(21,33,46,.06),0 12px 34px -18px rgba(21,33,46,.34)}
-[data-theme="nocturne"]{--paper:#0e151d;--paper-2:#131c26;--card:#18222e;--ink:#e7ecf2;--ink-soft:#aab6c2;--ink-faint:#76838f;--line:#2a3744;--line-soft:#202b36;--prussian:#5b8cc0;--prussian-bright:#7aa9d8;--brass:#d8b25a;--brass-bright:#e7c878;--teal:#3fb0a0;--rose:#d2796b;--t1:#d8b25a;--t1-bg:#2c2616;--t2:#3fb0a0;--t2-bg:#152b29;--t3:#d2796b;--t3-bg:#2c1c18;--contour:#283543;--shadow:0 1px 2px rgba(0,0,0,.4),0 18px 40px -20px rgba(0,0,0,.7)}
-[data-theme="loam"]{--paper:#f0ece2;--paper-2:#e7e1d3;--card:#faf7f0;--ink:#241d12;--ink-soft:#5c4f3a;--ink-faint:#8f8168;--line:#d3c9b4;--line-soft:#e2dac8;--prussian:#5a6b3a;--brass:#9a6b21;--teal:#3a7a5c;--rose:#a85a3e;--t1:#9a6b21;--t1-bg:#efe2c8;--t2:#3a7a5c;--t2-bg:#dcebe0;--t3:#a85a3e;--t3-bg:#f2ded4;--contour:#c8bca0;--shadow:0 1px 2px rgba(36,29,18,.06),0 12px 34px -18px rgba(36,29,18,.3)}
+[data-theme="vellum"]{--paper:#eceef2;--paper-2:#e2e6ec;--card:#f8fafc;--ink:#15212e;--ink-soft:#4d5a68;--ink-faint:#8492a0;--line:#cbd4de;--line-soft:#dde3ea;--prussian:#2c4a6b;--prussian-bright:#3f74ad;--brass:#9a7521;--brass-bright:#c0962f;--teal:#1d7a6e;--rose:#a8493e;--t1:#9a7521;--t1-bg:#f3ead0;--t2:#1d7a6e;--t2-bg:#ddefea;--t3:#a8493e;--t3-bg:#f4ddd7;--ok:#1d7a6e;--ok-bg:#ddefea;--note:#3a6b96;--note-bg:#ddeaf6;--warn:#8c680b;--warn-bg:#f3ead0;--critical:#a8493e;--critical-bg:#f4ddd7;--neutral:#667381;--neutral-bg:#e4e8ed;--contour:#bcc6d2;--shadow:0 1px 2px rgba(21,33,46,.06),0 12px 34px -18px rgba(21,33,46,.34)}
+[data-theme="nocturne"]{--paper:#0e151d;--paper-2:#131c26;--card:#18222e;--ink:#e7ecf2;--ink-soft:#aab6c2;--ink-faint:#76838f;--line:#2a3744;--line-soft:#202b36;--prussian:#5b8cc0;--prussian-bright:#7aa9d8;--brass:#d8b25a;--brass-bright:#e7c878;--teal:#3fb0a0;--rose:#d2796b;--t1:#d8b25a;--t1-bg:#2c2616;--t2:#3fb0a0;--t2-bg:#152b29;--t3:#d2796b;--t3-bg:#2c1c18;--ok:#3fb0a0;--ok-bg:#152b29;--note:#6fa6d4;--note-bg:#1a2834;--warn:#d8b25a;--warn-bg:#2c2616;--critical:#d2796b;--critical-bg:#2c1c18;--neutral:#8694a2;--neutral-bg:#21262b;--contour:#283543;--shadow:0 1px 2px rgba(0,0,0,.4),0 18px 40px -20px rgba(0,0,0,.7)}
+[data-theme="loam"]{--paper:#f0ece2;--paper-2:#e7e1d3;--card:#faf7f0;--ink:#241d12;--ink-soft:#5c4f3a;--ink-faint:#8f8168;--line:#d3c9b4;--line-soft:#e2dac8;--prussian:#5a6b3a;--brass:#9a6b21;--teal:#3a7a5c;--rose:#a85a3e;--t1:#9a6b21;--t1-bg:#efe2c8;--t2:#3a7a5c;--t2-bg:#dcebe0;--t3:#a85a3e;--t3-bg:#f2ded4;--ok:#3a5a40;--ok-bg:#e7eee2;--note:#3d6a78;--note-bg:#d9ecf2;--warn:#8e6900;--warn-bg:#f3e9cf;--critical:#a4543b;--critical-bg:#f0ddd2;--neutral:#746a5a;--neutral-bg:#eae6dd;--contour:#c8bca0;--shadow:0 1px 2px rgba(36,29,18,.06),0 12px 34px -18px rgba(36,29,18,.3)}
 
 /* ── base ── */
 *{box-sizing:border-box;margin:0;padding:0}
@@ -113,12 +113,17 @@ h2{font-family:var(--serif);font-weight:430;font-size:clamp(1.9rem,3.4vw,2.6rem)
 .verdict-band{background:var(--t2-bg);border:1px solid var(--t2);border-radius:12px;padding:16px 22px;font:500 .82rem/1.7 var(--mono);color:var(--ink)}
 .verdict-band b{color:var(--t2)}
 
-/* ── highlight callout ── */
-.hl{background:var(--t2-bg);border:1px solid var(--t2);border-radius:14px;padding:22px 26px;margin:18px 0}
-.hl.brass{background:var(--t1-bg);border-color:var(--t1)} .hl.rose{background:var(--t3-bg);border-color:var(--t3)}
-.hl .k{font:600 .66rem/1 var(--mono);letter-spacing:1.5px;text-transform:uppercase;color:var(--t2)}
-.hl.brass .k{color:var(--t1)} .hl.rose .k{color:var(--t3)}
-.hl h3{font-family:var(--serif);font-weight:500;font-size:1.3rem;margin:8px 0 10px}
+/* ── highlight: the one thing to land, as a quiet status panel (no side stripe) ──
+   6% tone tint, a 1px tone hairline all round, 12px radius. The tone comes from
+   the role tokens and the .k label carries its shape, so it reads in greyscale:
+   .hl = ok ● (decided) · .hl.brass = warn ▲ (owed, the ask) · .hl.rose = critical ■ (risk) */
+.hl{--tone:var(--ok);background:color-mix(in oklab,var(--tone) 6%,var(--card));border:1px solid color-mix(in oklab,var(--tone) 30%,transparent);border-radius:12px;padding:16px 20px 18px;margin:18px 0}
+.hl.brass{--tone:var(--warn)} .hl.rose{--tone:var(--critical)}
+.hl .k{display:inline-flex;align-items:center;gap:8px;font:500 .69rem/1 var(--mono);letter-spacing:.12em;text-transform:uppercase;color:var(--tone)}
+.hl .k::before{content:"";width:8px;height:8px;background:currentColor;border-radius:50%;flex:none}
+.hl.brass .k::before{border-radius:0;width:9px;clip-path:polygon(50% 0,100% 100%,0 100%)}
+.hl.rose .k::before{border-radius:1px}
+.hl h3{font-family:var(--serif);font-weight:500;font-size:1.3rem;margin:10px 0 8px}
 .hl p{font-size:.96rem} .hl .num{font-family:var(--serif);font-style:italic;color:var(--ink)}
 
 /* ── Q/A ledger ── */
@@ -163,9 +168,10 @@ h2{font-family:var(--serif);font-weight:430;font-size:clamp(1.9rem,3.4vw,2.6rem)
 .dot{display:inline-block;width:18px;height:18px;line-height:18px;border-radius:50%;font-size:.72rem;font-weight:700}
 .dot.ok{background:var(--t2-bg);color:var(--t2)} .dot.half{background:var(--t1-bg);color:var(--t1)} .dot.no{background:var(--t3-bg);color:var(--t3)} .dot.neu{background:var(--paper-2);color:var(--ink-faint)}
 
-/* ── accent-left readout ── */
-.readout{background:var(--card);border:1px solid var(--line);border-left:3px solid var(--t1);border-radius:4px;padding:20px 24px;margin:28px 0;font-size:1rem;color:var(--ink-soft)}
-.readout b{color:var(--ink)}
+/* ── readout: the bottom line as a key point — bigger type, no box ── */
+.readout{margin:28px 0;max-width:62ch;font-size:1.15em;line-height:1.5;font-weight:500;color:var(--ink)}
+.readout b{color:var(--ink);font-weight:650}
+.readout p{color:inherit;margin:0 0 .5em} .readout p:last-child{margin-bottom:0}
 
 /* ── footer ── */
 footer{padding:64px 0 90px;font:400 .74rem/1.8 var(--mono);color:var(--ink-faint)}