create-egregore 0.21.6 → 0.22.0

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

@@ -48,7 +48,7 @@ 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 `ROUTE=$(bash bin/loom.sh route view)`. When `bin/loom.sh` is not
+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.
@@ -183,11 +183,14 @@ 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 · vellum · decisive; a
-public explainer → persuade · newcomer · marketing · loam · quiet). 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.
+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
@@ -216,14 +219,36 @@ 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.
+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 complete Meridian chrome — vellum/nocturne/loam tokens, fonts,
-   sticky nav, theme toggle, contours — and a documented component kit). You fill
-   content; you do **not** rebuild the chrome or re-pick colors.
+   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. Pick the palette by
-   substance: vellum (strategy/decision), loam (warm/instructional), etc.
+   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
@@ -262,15 +287,25 @@ picking wrong is the single most common way a composed render lands badly.
    - 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**
-   `[data-theme="vellum"]` and `[data-theme="nocturne"]`, or dark mode breaks
-   silently on that element.
+   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)`.
 
@@ -302,6 +337,7 @@ 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;
@@ -314,7 +350,7 @@ do not infer a filename from the examples below.
 
 Only after an approved SHARE action returns a URL, append:
 ```
-◆ https://egregore.xyz/view/{org_slug}/board   (stable — refresh for latest)
+◆ {receipt.url}   (use the exact URL returned by the approved publication)
 ```
 Read `org_slug` from `egregore.json`.
 

package/runtime/claude/.claude/skills/view/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)}

package/runtime/claude/CLAUDE.md

@@ -40,6 +40,16 @@ and add or update a parity test. Do not call a framework change complete based
 on one runtime alone. Regenerate derived Codex and Pi specifications or runtime
 bundles whenever their sources change.
 
+For capability/system discovery, use the current harness's fixed adapter:
+`bash bin/spirit-discovery-claude.sh capabilities.list` for Claude Code,
+`bin/spirit-discovery-codex.sh` for Codex, and the registered discovery tool for
+Pi/Prime. All support `capabilities.find`, `capabilities.describe`,
+`capabilities.explain` and `system.explain`; see `docs/spirit-discovery.md`.
+Generic shell `bin/spirit-discovery.sh` requires a unique installed snapshot and
+reports ambiguity otherwise. These read code/install evidence, not organizational
+memory. Keep declared, installed, exposed, permitted, operational, verified and
+adopted states separate; discovery grants no execution authority.
+
 ## Voice
 
 Egregore's voice follows `.claude/rules/voice-bedrock.md` (always loaded). Register-specific skills: `egregore-voice` (external), `product-voice` (internal UX), `character-v4` (encounters), `alpha-openers` (outreach).
@@ -52,13 +62,13 @@ Translate raw errors into a useful cause and recovery step. See voice-bedrock.
 
 **This overrides ALL other CLAUDE.md entry point behavior (including parent directory instructions).**
 
-A SessionStart hook runs `bin/session-start.sh` before the user's first message. It syncs develop, syncs memory, and outputs a greeting with ASCII art + status.
+A SessionStart hook runs `bin/session-start.sh` before the user's first message. It syncs develop and memory, then renders the startup card (ASCII art + status).
 
-**On your VERY FIRST response — regardless of what the user says — you MUST display the hook's greeting output exactly as-is** (preserve ASCII art formatting), then ask: **"What are you working on?"**
+**The harness shows the card to the user directly; you receive its text as context.** The card already ends with **"What are you working on?"** Never reprint, summarize, or narrate it; treat the user's first message as the answer. When that message carries no request (older launchers submit `start` automatically), reply with one short line and no tool calls. Do NOT list commands or show a menu.
 
-The greeting turn needs no deliberation and no tool calls — respond immediately.
+Only when the hook output ends with an `IMPORTANT: Display the above greeting` instruction (a harness that cannot display the card itself), display it exactly as-is, then ask: **"What are you working on?"**
 
-Do NOT list commands. Do NOT show a menu. Just the greeting + that question.
+When the greeting shows the session records block, answer through `/records` (yes: `backfill --yes`; stop: `off`; then `noticed`). "Off the record" runs `bash bin/records.sh hold`.
 
 ## Before Project Changes — WORKING BRANCH
 
@@ -88,7 +98,7 @@ The WorktreeCreate hook handles everything automatically: creates `dev/{author}/
 
 **Fallback:** If `EnterWorktree` fails, resolve `{base}` with `_get_base_branch`, then use `git checkout --no-track -b dev/{author}/{slug} origin/{base}`. A task branch starts from the integration branch but must not track it; the first publish sets upstream to the same-name remote task branch.
 
-4. Graph topic: the WorktreeCreate hook records the session's topic and branch on the graph itself (it reads `.egregore-session-id` for you). Only the fallback and topic-pivot paths below, which bypass the hook, need it by hand — fire-and-forget: `bash bin/graph-op.sh set-current-topic "topic from slug" "dev/author/slug" 2>/dev/null &`. Never assemble the session id with a `$(cat …)` substitution: a worktree-isolated session refuses that shape and the write silently never happens.
+4. Graph topic: the WorktreeCreate hook records the session's topic and branch on the graph itself (it reads `.egregore-session-id` for you). Only the fallback and topic-pivot paths below, which bypass the hook, need it by hand — fire-and-forget: `bash bin/graph-op.sh set-current-topic "topic from slug" "dev/author/slug" 2>/dev/null &`. Never assemble the session id with a `$(cat …)` substitution: a worktree-isolated session refuses that shape and the write silently never happens. The shapes the worktree guard refuses and their plain forms are in `.claude/context/plain-shell.md`; split a refused command instead of retrying it.
 
 ### Starting-work UX contract
 
@@ -144,27 +154,7 @@ return as picking up a living thread, not reconstructing a Git session.
 
 ### Handoff claiming
 
-If `addressed_to_user` handoffs exist and the user is picking one up, create the IMPLEMENTS link after branch creation:
-```bash
-bash bin/graph-op.sh claim-handoff "$SESSION_ID" "$HANDOFF_SESSION_ID" 2>/dev/null &
-```
-
-**Auto-checkout repos from handoff**: After claiming, check the `addressed_rich` context for `repoState`. If the handoff includes repo state (non-empty `repoState` array), check out the handoff's branches in each managed repo:
-
-```bash
-PARENT_DIR="$(cd .. && pwd)"
-# For each entry in repoState:
-REPO_DIR="$PARENT_DIR/$REPO_NAME"
-if [ -d "$REPO_DIR/.git" ] || [ -f "$REPO_DIR/.git" ]; then
-  git -C "$REPO_DIR" fetch origin "$BRANCH" --quiet 2>/dev/null
-  git -C "$REPO_DIR" checkout "$BRANCH" 2>/dev/null || \
-    git -C "$REPO_DIR" checkout -b "$BRANCH" "origin/$BRANCH" 2>/dev/null
-fi
-```
-
-Report results: `✓ Checked out {branch} in {repo1}, {repo2}`. If a branch no longer exists (PR was merged): `◐ {repo}: PR #{N} merged — on {base}`. This works in both local and connected modes (pure git).
-
-If `repoState` is absent or empty (old handoff format), skip auto-checkout silently.
+When the user picks up a handoff addressed to them, follow `.claude/context/handoff-claiming.md` after branch creation: it claims the handoff and checks out the branches its `repoState` names in each managed repo.
 
 **Exceptions** — skip branching when:
 - User says `/branch` (doing it themselves)
@@ -202,6 +192,8 @@ Plan mode is **not** blocked by branch-guard — you can enter plan mode on deve
 
 If hook output contains `onboarding_needed`, invoke `/onboarding` instead of the greeting.
 
+
+
 ---
 
 ## Config Files
@@ -226,7 +218,7 @@ answers it: `open-handoffs`, `pending-questions`, `lineage`, or
 `meeting-history`. Verify projection freshness/coverage and open its canonical
 `evidencePath` before acting. Canonical Markdown wins on disagreement.
 
-Run `catalog` only when the route is unclear. Named reads return bounded stable fields and exact canonical `evidencePath` pointers; open only the returned files needed to answer. When a read reports partial coverage, use `unprojectedPaths` rather than claiming those files are represented in the graph. Use `bin/graph.sh` for unsupported Neo4j queries and never construct curl calls directly. See DEVELOPMENT.md §1 for the schema. Local recall uses Runtime `find`/`open`.
+Run `catalog` only when the route is unclear. Open only the returned `evidencePath` files needed to answer; on partial coverage, name `unprojectedPaths` instead of claiming them. Use `bin/graph.sh` for unsupported Neo4j queries and never construct curl calls directly (schema: DEVELOPMENT.md §1).
 
 ## Egregore Retrieval Beat
 
@@ -237,60 +229,42 @@ For each user-directed organizational lookup, show exactly one visible line:
 - retrieval that actually queries the connected graph:
   `⌕ Egregore Connect · searching your organization’s memory and relationships`
 
-When `EGREGORE_ORG_CONTEXT_V1` is attached, reuse its authorized evidence.
-For a remaining gap continue a Runtime investigation, preserving earlier findings.
-Follow `.claude/context/retrieval-investigation.md`: the model chooses keyword,
-semantic, hybrid, filename, literal, or date inventory; Runtime owns permissions,
-evidence history, pages and per-prompt limits. Empty results allow refinements
-within the requested dates. Never relax the date boundary to manufacture coverage.
-
-**Scope.** Egregore Runtime is for organizational recall only: team memory,
-decisions, handoffs, prior work. Code, files, Git, and tests use the harness's
-normal tools, with no beat and no Runtime call.
-
 **Visibility is the contract.** Emit it verbatim as a standalone assistant
 message before the first tool call that performs the organizational recall
 (the `bin/search.sh` query or a graph read). Tool output does not satisfy it.
-Do not paraphrase the line.
+Do not paraphrase the line. Emit once per episode.
+Never name `Egregore Connect` unless a graph read will actually run.
 
-Use Connect only for a graph traversal that actually runs. Emit once per
-episode.
+**Scope.** Egregore Runtime is for organizational recall only: team memory,
+decisions, handoffs, prior work. Code, files, Git, and tests use the harness's
+normal tools, with no beat and no Runtime call. Startup hydration, graph
+writes, ingestion, background sync, maintenance, and internal queries get no beat.
 
 **Routing:** Organizational recall always enters Egregore Runtime. The model is
 the semantic intent authority, deciding from meaning rather than fixed phrases.
+Do not run retrieval on unrelated prompts or infer graph from recall intent.
 Prompt hooks attach identity and guidance only; they never retrieve evidence.
-Without attached context, choose the appropriate Runtime operation:
+The full retrieval contract arrives with the session's first prompt as
+`EGREGORE_ACTOR_CONTEXT_V1` (later prompts carry a reminder); follow it.
+When `EGREGORE_ORG_CONTEXT_V1` is attached, reuse its authorized evidence.
+When the full contract is not in your context (a subagent, a missed hook, or
+after a compaction), start with
 
 ```bash
 bash bin/search.sh find "<query>" --kind <kind> --context-packet
 ```
 
-Choose `filename`, `literal`, or `dates` for canonical file lookups; `keyword`
-for BM25; `semantic` for paraphrases; `hybrid` for combined ranking. No mode
-must run first. Open necessary sources together with `bash bin/search.sh open
-memory/path-a.md memory/path-b.md`. Runtime retains request state; do not write
-JSON operations, episode arguments, or gap explanations for normal retrieval.
-Use `find` for model-led discovery; `query` is a compatibility command. Read
-canonical sources through `search.sh open`, never a raw file-read tool or shell
-read. An adequate excerpt already supports an answer; no extra open is needed.
+and follow `.claude/context/retrieval-investigation.md`.
+Open necessary sources together with `bash bin/search.sh open`; never read
+memory with a raw file tool, `grep` or `ls`. Do not `cd` into the sibling memory repository.
+Never relax the date boundary to manufacture coverage.
 
 `--context-packet` attaches the evidence privately; the visible output is the
 attribution line alone. Never re-print ranked results or raw JSON.
 
-Do not resolve `memory/` to its sibling repo or start with raw `grep`/`ls`.
-Search attaches no graph by default. Open a source only when its excerpt
-cannot support a necessary claim. For current
-team/person synthesis, retain the requested subject and choose a `recent_days`
-window. Use date filters for a known topic, or a bounded date inventory for
-a recent-work overview. `/activity`, `/dashboard`, and `/project`
-display bounded status surfaces only when named or directly requested as a
-card. Explained syntheses of current organizational work and prior-work
-discovery are Runtime/QMD recall. Do not run retrieval on unrelated prompts or
-infer graph from recall intent.
-
-Do not emit the beat for code search, Git inspection, startup hydration, graph
-writes, ingestion, background sync, maintenance, or internal queries.
-Never name `Egregore Connect` unless a graph read will actually run.
+`/activity`, `/dashboard`, and `/project` display bounded status surfaces only
+when named or directly requested as a card.
+Explained syntheses of current organizational work and prior-work discovery are Runtime/QMD recall.
 
 ## Notifications
 
@@ -332,12 +306,15 @@ Never repeat it.
 
 ## Memory
 
-`memory/` is a symlink to the memory repo defined in `egregore.json`. Key directories:
-- `people/` — team directory
-- `handoffs/` — session handoffs + `index.md`
-- `knowledge/decisions/` — org decisions
-- `knowledge/patterns/` — emergent patterns
-- `infrastructure/` — service registry (URLs, names, credential locations)
+`memory/` links to the repo in `egregore.json`:
+- `people/` — team
+- `handoffs/` — handoffs and index
+- `knowledge/decisions/` — decisions
+- `knowledge/patterns/` — patterns
+- `infrastructure/` — services and credential locations
+
+Write memory through its commands, never the files: `/reflect` for decisions, `/handoff` for handoffs.
+
 
 Always use HTTPS for git operations — `github-auth.sh` handles credential storage.
 
@@ -356,9 +333,8 @@ needs) or escalate one tier (uncertainty). Full spec:
 ## Git Workflow
 
 `develop` is the default integration branch. A top-level
-`egregore.json.base_branch` replaces it for instances using another integration
-branch; `base_branch: "main"` is single-branch mode. Users never interact with
-git directly.
+`egregore.json.base_branch` replaces it; `base_branch: "main"` is single-branch
+mode. Users never interact with git directly.
 
 ```
 main ← selected `/release` candidates
@@ -372,10 +348,9 @@ develop ← CL integration (available internally)
 - **On launch**: syncs the configured base branch + memory. Does NOT create a branch.
 - **Branch creation**: required before project changes; read-only work stays put.
 - **Resuming**: rebase onto the configured base branch and continue.
-- **Read-only sessions**: no branch creation based on message count.
 - **`/save`**: pushes the working branch and opens a PR to the configured base. Auto-merges markdown-only PRs.
 - **Memory repo**: stays on main (separate repo, auto-merge).
-- **Never push directly to the configured base, main, or develop.** All changes flow through PRs.
+- **Never push directly to the configured base, main, or develop.** Changes flow through PRs, merged with `bash bin/agent.sh merge <pr>`, never `gh pr merge`; a red check needs a receipt naming each failing job and why.
 
 ### Pull request format (all harnesses)
 
@@ -383,23 +358,17 @@ Every PR body follows `.claude/context/pr-format.md`, enforced by the `pr-format
 
 ### Commit format (all harnesses)
 
-Every commit follows `.claude/context/commit-format.md`: subject `type(scope): imperative summary` (≤ 72 chars, aim ≤ 50, lowercase, same grammar and type set as PR titles), body wrapped at 72 explaining what and why — never how, and git trailers on agent-authored commits (`Egregore-Session: <id>` from `.egregore-session-id`, plus the harness `Co-Authored-By` line). Background scripts commit as `chore(<subsystem>): …`, but a commit carrying real work derives its type/scope from the diff — the transport never masks the work. Git-generated messages (merges, reverts, autosquash fixups) keep their native form. Wording for commits and PRs follows `.claude/context/git-language.md`.
+Every commit follows `.claude/context/commit-format.md`: subject `type(scope): imperative summary` (≤ 72 chars, aim ≤ 50, lowercase, same grammar and type set as PR titles), body wrapped at 72 explaining what and why — never how, and git trailers on agent-authored commits (`Egregore-Session: <id>` from `bash bin/session-id.sh`, plus the harness `Co-Authored-By` line). Background scripts commit as `chore(<subsystem>): …`, but a commit carrying real work derives its type/scope from the diff — the transport never masks the work. Git-generated messages (merges, reverts, autosquash fixups) keep their native form. Wording for commits and PRs follows `.claude/context/git-language.md`.
 
 ### Managed Repos
 
 Repos in `egregore.json` → `repos[]` are cloned as siblings (`../{repo}/`). Each entry can be a string or `{"name": "...", "description": "..."}`. Match user intent to the right repo using `description`. Same branching strategy. Use `git -C` with absolute paths — never `cd` into repos. `/save` scans all managed repos for uncommitted changes.
 
-## Working Conventions
-
-- For unfamiliar org work, use Observe context; if absent, run `bash bin/search.sh find` with an appropriate lookup kind.
-- Document significant decisions in `memory/knowledge/decisions/`
-- After substantial sessions, log to `memory/handoffs/` and update `index.md`
-
 ## Command Awareness
 
 Invoke commands from user intent — don't wait for the slash. Each command file has a `## When to invoke` section. Load it for the full spec.
 
-**Core loop** — `/activity` `/dashboard` `/handoff` `/wrap` `/save` `/reflect` `/todo`
+**Core loop** — `/activity` `/dashboard` `/handoff` `/wrap` `/save` `/reflect` `/todo` `/records`
 **Knowledge** — `/search` `/deep-reflect` `/archive` `/note` `/add` `/meeting` `/ingest` `/scroll` `/mock` `/audit`
 **Identity** — `/me` (view profile or set display name)
 **Coordination** — `/ask` `/quest` `/issue` `/invite` `/delete-user` `/announce`
@@ -411,17 +380,10 @@ Invoke commands from user intent — don't wait for the slash. Each command file
 
 **Disambiguation:**
 - Knowledge: `/reflect` (share-ready) · `/note` (half-baked) · `/deep-reflect` (deep research over memory — questions AND cross-referencing) · `/archive` (AI patterns) · `/audit` (evidence-mined forensic sweep of the org's own record — any target)
-- Exact lifecycle questions (latest/oldest handoff addressed to or sent by someone, open/unresolved) — recognize the intent from meaning and run the typed lookup `bash bin/search.sh handoffs [--mine|--sent|--addressed-to X] [--status open] [--order newest|oldest]` — deterministic, one beat, never a semantic query; empty result means say so.
-- Finding things — **the model chooses organizational retrieval through Runtime**.
-  Reuse equivalent evidence and investigate distinct gaps through the same Runtime.
-  Use `bash bin/search.sh find` or `open` and the shared investigation contract. Use Grep/Glob for code and exact errors, not org
-  recall. Do not `cd` into the sibling memory repository.
-- Finding **something you generated** (a scroll, handoff, emissary, decision, any hosted egregore.xyz link): `bash bin/artifacts.sh find <query>`. Every generative surface records into memory — hosted artifacts self-register into `memory/artifacts/` at publish (committed+pushed, findable from any session); handoffs in `memory/handoffs/`, emissaries in `memory/handoffs/outbound/`, decisions/findings/patterns in `memory/knowledge/`. The finder searches all of them by **content, not just name**, ranks title/topic matches above body mentions, tags hits by type (`[document]`/`[handoff]`/`[emissary]`/`[decision]`), and surfaces the shareable URL — grep-first in OSS, search + graph when available. *"bring me the artifact where I laid out our GTM plan"* → this.
+- Finding things — organizational recall through Runtime (Egregore Retrieval Beat); Grep/Glob for code and exact errors.
+- Finding **something you generated** (a scroll, handoff, emissary, decision, any hosted egregore.xyz link): `bash bin/artifacts.sh find <query>` searches every generated record by content, tags its type and returns the shareable URL. *"bring me the artifact where I laid out our GTM plan"* → this.
 - Artifacts with questions: `/scroll` (living paper + embedded harvest, updates in place) · `/view` (static render) · `/harvest` (elicitation, no published face) · `/mock` (pre-build walkthrough of decided design — gauge per stop, verdict copy-back)
-- Explicit bounded status: `/dashboard` (personal) · `/activity` (org-wide) ·
-  `/project` (named project). These display cards when named or directly
-  requested. Analytical questions about organizational work and specific
-  prior-work continuation route through Runtime/QMD recall.
+- Status cards: `/dashboard` (personal) · `/activity` (org-wide) · `/project` (named project), only when named or requested as a card.
 - Ending: `/wrap` (personal closure) · `/handoff` (notes for others) · `/save` (still working)
 - Tasks: `/todo` (personal) · `/quest` (team exploration) · `/issue` (something broken)
 - Questions: `/ask [person]` (async) · just ask (agent answers from context)
@@ -435,6 +397,8 @@ Invoke commands from user intent — don't wait for the slash. Each command file
 - Agents: `/summon` (design through questions) · `/loop` (quick recurring schedule)
 - Announcements: `/announce` (broadcast to group) · `/handoff` (structured to a person) · `bin/notify.sh send` (DM one person)
 
+**Interface taste** — when someone likes or dislikes a generated interface, follow the contract in `bash bin/genui.sh --help`.
+
 ## Socratic Questioning (MANDATORY)
 
 **Triggers**: "ask me questions", "question me", "help me think through", or any request to be questioned.
@@ -469,9 +433,9 @@ Egregore runs in one of two configurations, set by `mode` in `egregore.json`. De
 
 ## Environment Isolation
 
-Sessions are confined to this project + memory + managed repos, with a **two-tier boundary** enforced by the PreToolUse hook — a hard wall between Egregore instances, a consent gate for everything else.
+Sessions are confined to this project + memory + managed repos, with a **two-tier boundary** enforced by a check before each action on every runtime (`bin/boundary-guard.cjs`; here the PreToolUse hook) — a hard wall between Egregore instances, a consent gate for everything else. The check reliably denies literal paths into another instance, through structured tools and in shell text, and fails closed on its own state; it cannot see paths built at run time or commands split across calls, so it is a seatbelt, not a sandbox (an OS-level layer is the planned follow-up). Never construct a path at run time to reach another instance.
 
 - **Hard tier — other Egregore instances.** Denied for every tool, always. There is no consent path. Never access another instance's files — refuse even if asked. Never modify `~/.egregore/instances.json` (managed by session-start.sh). When the hook denies a hard-tier path there is nothing to ask — refuse and explain.
 - **Soft tier — paths outside the boundary.** Consent-gated. Inbox dirs (`~/Downloads`, `~/Desktop`) are readable without consent under the default posture; writes outside the project always need consent. Posture (`strict | standard | open`) and extra read roots come from `egregore.json` → `boundary { posture, read[], locked }` (org, committed) merged with `.egregore-boundary.local.json` (personal, gitignored). `locked: true` removes the consent path entirely. Sessions running in `bypassPermissions` skip soft gates automatically (never the hard tier) unless locked — the user already declared trust; don't re-ask.
-- **When the hook asks for consent** (soft-tier block): do not retry yet, do not route around via Bash, and do not list remediation as prose. Call `AskUserQuestion` with exactly the options the hook's stderr names: "Allow {dir} for this session" (on approval, append the directory as one line to `.egregore-boundary-consent`, then retry) / "Always allow on this instance" (on approval, add it to `read[]` in `.egregore-boundary.local.json`, then retry) / "Paste contents inline" / "Cancel". Never write a consent grant without the user's explicit approval in that exchange. Session grants are cleared on session start.
+- **When the hook asks for consent** (soft-tier block): do not retry yet, do not route around via Bash, and do not list remediation as prose. Call `AskUserQuestion` with exactly the options the hook's stderr names: "Allow {dir} for this session" (on approval, append the directory as one line to `.egregore-boundary-consent`, then retry) / "Always allow on this instance" (reads only, so a blocked write never offers it; on approval, add it to `read[]` in `.egregore-boundary.local.json`, then retry) / "Paste contents inline" / "Cancel". Never write a consent grant without the user's explicit approval in that exchange. Session grants are cleared on session start.
 - See DEVELOPMENT.md §3 for boundary details and `memory/knowledge/decisions/2026-07-08-boundary-hook-consent-design.md` for the design decisions