geneseed 2.0.0

package/docs/web/pipelines.md

@@ -0,0 +1,24 @@
+---
+group: concepts
+order: 13
+title: "Agent pipelines"
+kind: "concept"
+link: {"hash": "#/section/agents", "label": "Browse the agents →"}
+---
+An **agent pipeline** is the isolated crew that [foreman mode](#/docs/foreman-mode) spawns for a substantial task. Where [agents](#/section/agents) are capability specialists you delegate to one at a time, a pipeline chains them into a single, self-contained unit of work that runs apart from your session.
+
+### The default crew
+
+- **analyst** — turns the request into a concrete plan and acceptance criteria.
+- **developer** — implements against that plan.
+- **tester** — exercises the result and gates the outcome.
+
+The foreman adds whatever other specialists the task calls for — a reviewer, a security pass, a docs writer — routing each subtask to the agent that owns it.
+
+### Isolated, and gated on green
+
+A pipeline runs in its own context so the main session stays free to keep answering you, and it **merges only once its own tests and lint pass** — a crew that can't get to green reports back rather than landing broken work. It's the same *decompose → route to the owning specialist → converge* shape the saved workflow runner uses, but driven live by the foreman rather than a pre-written script.
+
+---
+
+**Related:** [Foreman mode](#/docs/foreman-mode) · [Agents](#/section/agents)

package/docs/web/plugin-activity.md

@@ -0,0 +1,23 @@
+---
+group: plugins
+order: 7
+title: "geneseed-activity"
+kind: "concept"
+---
+Feeds this console's **Activity** view: writes one small JSON file per session (`activity/<session_id>.json` beside the OpenCode config) recording what the harness is *doing* — current phase, model, token and cost totals, turn-elapsed, files touched, the plan, and the last error. The web server reads and prunes those files; writer and reader only ever meet on the filesystem, so a crash on either side never blocks a session.
+
+- **One entry per top-level session** — sub-agent child sessions and the learn plugin's throwaway distil sessions are skipped.
+- **Self-cleaning** — the reader prunes entries whose process is dead or whose timestamp went stale, so a crashed writer's file disappears on its own.
+
+### Install
+
+Installs with the other plugins in one step — see [Plugin setup](#/docs/plugin-setup).
+
+### Configure
+
+- `GENESEED_ACTIVITY=off` — hard kill switch at startup.
+- The **Activity** page's toggle writes a `.geneseed-activity` flag file read per event — takes effect without restarting OpenCode.
+
+### Verify
+
+Start a session, then open **Activity** in this console — a card for the session appears. `GENESEED_DEBUG=1` logs each write as `[geneseed-activity] …` to stderr.

package/docs/web/plugin-context.md

@@ -0,0 +1,26 @@
+---
+group: plugins
+order: 1
+title: "geneseed-context"
+kind: "concept"
+---
+Enforces **Law XVIII** (*Load the Project Context*) by injection, not instruction: on `session.created` it auto-discovers the repo's docs by convention and injects the `eager` ones before your first turn, so the harness needs **zero per-repo files**.
+
+- **Eager** (injected in full, budget-capped): root `AGENTS.md` / `AGENT.md` / `CLAUDE.md` / `.cursorrules`, `README.md`, `CONTRIBUTING.md`.
+- **Lazy** (path + first heading, read on demand): `docs/`, `doc/`, `architecture/`, `adr/`, monorepo `packages/*/README.md`, other root `*.md`. `node_modules`, `.git`, `dist`, `build` are never scanned.
+- It re-pushes eager docs on `session.compacting` so context survives a summarised long session, and carries your machine wiki (`wiki.jsonc`) on the same budgets.
+
+### Install
+
+Installs with the other plugins in one step — see [Plugin setup](#/docs/plugin-setup).
+
+### Configure
+
+- `GENESEED_CONTEXT` — path to an explicit `context.json` manifest (or drop `.harness/context.json` in the repo) to take control: same schema, plus glob `path`s, `load: exclude`, and `"extend": true` to layer on top of discovery.
+- `GENESEED_EAGER_FILE_KB` (default 16) / `GENESEED_EAGER_TOTAL_KB` (default 48) — budget caps; an oversized eager file is demoted to a lazy listing, never silently truncated.
+- `GENESEED_CONTEXT_VISIBLE=1` — force the visible `PROJECT CONTEXT` block instead of the invisible per-request transform.
+- `GENESEED_CONTEXT_INJECT=off` — disable injection entirely (falls back to the soft AGENT.md Law).
+
+### Verify
+
+Start a session with `GENESEED_DEBUG=1` set — the plugin logs what it discovered and injected to stderr. Silence means it didn't load: re-check the filename and that the path is exactly the plugins dir above.

package/docs/web/plugin-guard.md

@@ -0,0 +1,24 @@
+---
+group: plugins
+order: 3
+title: "geneseed-guard"
+kind: "concept"
+---
+Enforces the safety Laws at the tool boundary (`tool.execute.before`) — the same *enforce by injection, don't just instruct* stance as the context plugin. High-confidence patterns only, so legitimate work is never caught:
+
+- **Blocks** — writes to private-key / credential files (**Law I**), catastrophic shell like `rm -rf /` (**Law IV**), and any mutation under a declared wiki's `protected` folders (AGENT.md §7, from `wiki.jsonc`).
+- **Warns** (logged, allowed) — `.env` writes and force-push.
+- **Speed-bumps** — the *first* write to `user-rules.md` or a memory file is refused, naming **Law VI**: a standing rule or a durable fact is the user's call, settled through the rule skill. A re-issued write goes through, so a legitimate write is never trapped. (On Claude Code and Bob the same guard is a `geneseed-hook rule-gate` hook, which can *ask* the user instead of refusing — OpenCode's `tool.execute.before` has no ask tier.)
+
+### Install
+
+Installs with the other plugins in one step — see [Plugin setup](#/docs/plugin-setup). The `protected` wiki folders are read from `wiki.jsonc` (`GENESEED_WIKI` → `$GENESEED_HARNESS/wiki.jsonc` → beside the install).
+
+### Configure
+
+- `GENESEED_GUARD=off` — disable the guard entirely.
+- `GENESEED_GUARD=warn` — downgrade every block to a warning (log, but allow).
+
+### Verify
+
+Ask the agent to do something the guard blocks (e.g. write to a `.pem` file) — it should be refused with a `[geneseed-guard] blocked: …` message naming the Law.

package/docs/web/plugin-learn.md

@@ -0,0 +1,27 @@
+---
+group: plugins
+order: 2
+title: "geneseed-learn"
+kind: "concept"
+---
+The runtime-agnostic counterpart of the Claude Code `Stop` hook: on `session.idle` it distils durable memories from the conversation into the bundle's `memory/` dir and maintains `MEMORY.md`, deduping against what's already stored — exactly what `geneseed learn` does, but self-contained in JS, so no Python and no model CLI are required.
+
+It distils with the **same model the session already used** (read from the transcript), inheriting your OpenCode provider config — no API key, nothing to set. Trivial sessions are skipped and any error is swallowed, so it never blocks a session.
+
+### Install
+
+Installs with the other plugins in one step — see [Plugin setup](#/docs/plugin-setup).
+
+### Configure — where it writes
+
+Memories land in the first location that resolves:
+
+1. `GENESEED_MEMORY` — an explicit memory dir;
+2. `$GENESEED_HARNESS/memory` (or `/anamnesis` for the imperial theme);
+3. `./memory` or `./Harness/memory` when the bundle lives in the project.
+
+Because the bundle is global, set `GENESEED_HARNESS` once to its absolute path so the plugin always writes to the same store no matter where you launch OpenCode. If it can't read the session's model from the transcript, set a fallback `GENESEED_MODEL=provider/model`.
+
+### Verify
+
+Start a session, do a little work, end it. On `session.idle` the plugin logs `[geneseed-learn] wrote N memory file(s): …` or a skip reason to stderr. Total silence means it didn't load.

package/docs/web/plugin-notify.md

@@ -0,0 +1,24 @@
+---
+group: plugins
+order: 5
+title: "geneseed-notify"
+kind: "concept"
+---
+Pings the OS when the agent finishes a turn, so you can start a long run, walk away, and be called back when it's your move again. It hooks `session.idle` like the learn plugin.
+
+- **Anti-spam:** only fires when the turn actually took a while — the gap between the session's last user prompt and now must exceed `GENESEED_NOTIFY_MIN_SECONDS` (default 30). Native subagent child sessions and the learn plugin's throwaway distil sessions are skipped.
+- **Native, dependency-free:** macOS `osascript`, Linux `notify-send` (libnotify), Windows a PowerShell balloon. Spawned detached; any failure is swallowed, so it never blocks a session.
+
+### Install
+
+Installs with the other plugins in one step — see [Plugin setup](#/docs/plugin-setup). On Linux, install `libnotify` (for `notify-send`) if nothing appears.
+
+### Configure
+
+- `GENESEED_NOTIFY=off` — disable it.
+- `GENESEED_NOTIFY_MIN_SECONDS=N` — tune the threshold (`0` notifies on every turn).
+- `GENESEED_NOTIFY_TITLE="…"` — override the title (default `Geneseed`).
+
+### Verify
+
+With `GENESEED_DEBUG=1`, end a session that ran longer than the threshold — you'll see `[geneseed-notify] notified for …` and a desktop notification.

package/docs/web/plugin-ponytail.md

@@ -0,0 +1,23 @@
+---
+group: plugins
+order: 6
+title: "geneseed-ponytail"
+kind: "concept"
+---
+The sustained counterpart to the `ponytail` skill: once you opt in, it appends the laziest-that-works ruleset to the system prompt **every turn**, so the agent doesn't drift back to over-building mid-session, and it persists the level across turns.
+
+- **Opt-in:** the mode starts at `off` and injects nothing until you switch it on. Geneseed treats ponytail as a skill, not an always-on Law.
+- **Toggle:** `/ponytail lite|full|ultra|off` (a bare `/ponytail` means `full`). The level is written to `.geneseed-ponytail` beside OpenCode's config and applies from the next turn.
+- **Hooks:** `experimental.chat.system.transform` appends the ruleset; `command.execute.before` records the switch. Every failure is swallowed; on a build without the system-transform hook it simply never injects (the skill still covers the invokable path).
+
+### Install
+
+Installs with the other plugins in one step — see [Plugin setup](#/docs/plugin-setup).
+
+### Configure
+
+- `GENESEED_PONYTAIL=lite|full|ultra` — make a level the default for new installs (default `off`, i.e. dormant until asked).
+
+### Verify
+
+With `GENESEED_DEBUG=1`, run `/ponytail full` — you'll see `[geneseed-ponytail] ponytail full`, and the next turn's replies favour the minimal solution.

package/docs/web/plugin-setup.md

@@ -0,0 +1,7 @@
+---
+group: plugins
+order: 0
+title: "Plugin setup"
+kind: "markdown"
+source: "docs/opencode-plugin-setup.md"
+---

package/docs/web/plugin-workflow.md

@@ -0,0 +1,24 @@
+---
+group: plugins
+order: 4
+title: "geneseed-workflow"
+kind: "concept"
+---
+Registers one custom tool, `workflow`, that runs saved, code-driven orchestration scripts — the deterministic counterpart to the model-driven [[council]] / [[parallel-agents]] skills: the script, not the model, drives the control flow.
+
+- **Saved scripts only (v1):** the tool loads `<name>.js` from the sibling `workflows/` dir. No model-authored scripts are eval'd.
+- **Call shape:** `workflow({ name, args })` — call with no name to list what's available. Shipped: `council`, `review`, `research-plan-implement`.
+- **Runtime API:** scripts get `agent()`, `parallel()`, `pipeline()`, `phase()`, `log()`, `budget`, `args`. Child work runs as real OpenCode sessions; concurrency is capped at `min(16, cores − 2)`.
+
+### Install
+
+Installs with the other plugins in one step — see [Plugin setup](#/docs/plugin-setup). The build copies the plugin **and** the sibling `workflows/` dir, so the saved scripts resolve out of the box; a manual `cp` only moves the `*.js`, so copy `adapters/opencode/workflows/` alongside it too.
+
+### Configure
+
+- `GENESEED_WORKFLOWS_DIR` — override the scripts dir (defaults to `.opencode/workflows/` per-repo, `<config>/workflows/` global).
+- A phase-by-phase trace plus the full result land in `.geneseed/workflow-runs/<runId>.log`; `GENESEED_DEBUG=1` adds stderr logging.
+
+### Verify
+
+Ask the agent to *"list available workflows"* — it should call `workflow` with no name and return `council`, `review`, `research-plan-implement`.

package/docs/web/plugins.md

@@ -0,0 +1,17 @@
+---
+group: concepts
+order: 10
+title: "Plugins (OpenCode)"
+kind: "concept"
+harness: "opencode"
+link: {"hash": "#/docs/plugin-context", "label": "One page per plugin →"}
+---
+OpenCode loads {N_PLUGINS} plugins from the deployed bundle:
+
+- **geneseed-context** — injects the project's docs *and* your machine wiki at every session start (and after compaction).
+- **geneseed-learn** — distils memory at session end (powers the `learn` skill).
+- **geneseed-guard** — enforces the safety Laws and protected wiki folders at the tool boundary.
+- **geneseed-workflow** — registers the `workflow` tool that runs saved orchestration scripts.
+- **geneseed-notify** — sends a native OS notification when a long run finishes, so you can step away and be called back.
+- **geneseed-ponytail** — holds an opt-in minimal-code mode (`/ponytail lite|full|ultra|off`), injecting the laziest-that-works ruleset every turn so it doesn't drift.
+- **geneseed-activity** — streams what each live session is *doing* (phase, model, tokens, files touched) to this console's Activity view.

package/docs/web/project-context.md

@@ -0,0 +1,9 @@
+---
+group: howto
+order: 2
+title: "Override project context"
+kind: "markdown"
+anchor: "project-context-usually-nothing"
+source: "SETUP.md"
+slice: true
+---

package/docs/web/rules.md

@@ -0,0 +1,8 @@
+---
+group: concepts
+order: 1
+title: "Rules (Laws)"
+kind: "concept"
+link: {"hash": "#/laws", "label": "Browse the ledger →"}
+---
+{N_LAWS} universal laws the agent obeys — secrets handling, scope discipline, verify-before-assert, surface-failures, context economy, load-the-docs, tool-discovery, non-interactive-shell, and more. Each law is a short markdown file under `src/laws/` and the rendered numbered list lives in `AGENT.md`. They bind regardless of theme: an imperial deploy reads them as *Dictates*, a neutral deploy as *Rules*, but the numbering and the rule itself never move.

package/docs/web/run-anywhere.md

@@ -0,0 +1,9 @@
+---
+group: howto
+order: 5
+title: "Run `geneseed` from anywhere"
+kind: "markdown"
+anchor: "run-geneseed-from-anywhere"
+source: "SETUP.md"
+slice: true
+---

package/docs/web/self-improve.md

@@ -0,0 +1,8 @@
+---
+group: howto
+order: 9
+title: "The self-improvement loop"
+kind: "concept"
+link: {"hash": "#/diff", "label": "Open the diff page →"}
+---
+Local edits the agent makes to its own deployed agent/skill files survive the next rebuild. Before `setup`, re-theme, or `upgrade` overwrites them, any drift is auto-exported to a markdown **improvements file** under `improvements/` inside the deployed harness dir — untouched by rebuilds and uninstall. Hand it to an agent in *this* repo to back-port the changes into `src/`. On demand: `geneseed diff --out FILE`, or the **Changes** page in this UI.

package/docs/web/setup-choices.md

@@ -0,0 +1,39 @@
+---
+group: start
+order: 1
+title: "Posture & footprint"
+kind: "concept"
+---
+The setup wizard asks four starting parameters. The first, the **theme**, is the *voice* — banner, sigil, prose register — previewed live as you move through the wizard; it never changes structure or rules, so pick whatever reads best to you ([voice vs structure](#/docs/themes)). The other three shape how the agent works and are explained below. All four have safe defaults — accept them and move on, or pick deliberately here. All are set-and-forget: preserved across every rebuild and re-theme, changeable later from **Settings**, the **Harnesses** page, or the wizard.
+
+### Posture — the relationship register
+
+How the agent works *with you*, fixed at build time so it doesn't drift mid-session:
+
+- **peer** *(default)* — candid equal: dense, challenges, no flattery.
+- **mentor** — explains the why, checks understanding.
+- **expert** — maximum density, no basics.
+- **assistant** — precise execution, low initiative; you steer.
+- **artisan** — peer with toolsmith reflexes, terminal-first.
+
+Pick **peer** unless you know you want another register. Posture is orthogonal to theme: theme changes the prose, posture changes the relationship.
+
+### Mode — how work gets executed
+
+How the session runs the work you hand it, fixed at build time:
+
+- **direct** *(default)* — the agent works every task itself, turn by turn, exactly as it does today.
+- **foreman** — the session triages incoming tasks: trivial ones get a direct answer, substantial ones spawn an isolated crew (analyst → developer → tester) that reports back and merges only once its tests and lint pass — while the session keeps answering you. Costs more per substantial task (a small crew runs instead of one agent) in exchange for staying responsive.
+
+Pick **direct** unless you want the session managing a crew for you. Switch back any time with `--mode direct`.
+
+### Footprint — full or lean Rules
+
+How much of the Rules `AGENT.md` carries inline every turn. A token-cost dial, not a rules cut — every Rule always applies:
+
+- **full** *(default)* — every Rule's text *and* rationale inline. Best when token cost is a non-issue or you run a smaller model.
+- **lean** — one line per Rule plus a pointer to the complete laws file, read on demand. Trims the Rules section by roughly 40% for long sessions or cost-sensitive runs.
+
+---
+
+**Deeper:** [The collaboration layer](#/docs/collaboration) · [Footprint (lean vs full)](#/docs/footprint) · **Next:** [Verify it works](#/docs/verify)

package/docs/web/skills.md

@@ -0,0 +1,8 @@
+---
+group: concepts
+order: 3
+title: "Skills"
+kind: "concept"
+link: {"hash": "#/section/skills", "label": "Browse the catalog →"}
+---
+{N_SKILLS} repeatable workflows the agent can invoke by name — from [[brainstorm]], [[clarify]], [[plan]], [[tdd]] and [[debug]] through [[council]], [[research]] and [[ship]] to [[roast-me]]. A skill is a markdown playbook under `src/skills/`; the agent reads it before acting. The catalog link lists every one, live.

package/docs/web/themes-author.md

@@ -0,0 +1,8 @@
+---
+group: extend
+order: 1
+title: "Write a new theme"
+kind: "concept"
+link: {"hash": "#/themes", "label": "Open the theme gallery →"}
+---
+A theme is one JSON file under `themes/` declaring voice tokens only: `BANNER`, `TAGLINE`, `LOADED_SIGIL`, `VOICE`, the core nouns (`LAW(S)`/`AGENT(S)`/`SKILL(S)`/`MEMORY`/`NOTEBOOK`/`WIKI`), the law titles `LEX_*`, the section intros `INTRO_*`, the epigraphs `EPI_*`, the `BENEDICTION`, the `ROAST_PERSONA`, and `DESC_*` blurbs. Copy `themes/neutral.json` and edit. `geneseed build --theme yours` renders it; `doctor` checks for missing tokens.

package/docs/web/themes.md

@@ -0,0 +1,9 @@
+---
+group: concepts
+order: 7
+title: "Voice vs structure (themes)"
+kind: "markdown"
+anchor: "decisions"
+source: "DESIGN.md"
+slice: true
+---

package/docs/web/token-footprint.md

@@ -0,0 +1,7 @@
+---
+group: deeper
+order: 5
+title: "Token footprint"
+kind: "markdown"
+source: "docs/token-footprint.md"
+---

package/docs/web/trouble.md

@@ -0,0 +1,38 @@
+---
+group: reference
+order: 3
+title: "Troubleshooting"
+kind: "concept"
+---
+MCP server issues have their own page: [MCP — won't connect?](#/docs/mcp-trouble).
+
+### `geneseed: command not found`
+Run `./geneseed link` (macOS/Linux) or `.\geneseed.cmd link` (Windows) from the cloned repo. On Windows, open a new terminal after `link` — the PATH update only applies to fresh shells.
+
+<!--harness:opencode-->
+### The agent doesn't load my project docs
+On OpenCode the `geneseed-context` plugin must be installed. Re-run `geneseed setup` or `geneseed build --emit opencode-global`. Verify with `geneseed doctor`.
+<!--/harness-->
+
+### `doctor` reports unresolved theme tokens
+A theme JSON is missing a key the templates reference. Compare with `themes/neutral.json` — every key there must exist in your theme. Re-render: `geneseed build --theme <yours>`.
+
+### `doctor` reports drift between bundle and src
+A committed `Harness/` snapshot fell behind. Re-render and commit: `geneseed build && git add Harness`. If the drift is intentional local edits, use the **Changes** page to export them as an improvements file and back-port.
+
+### Web UI shows 'no deployed harness'
+Run `geneseed setup` to install. The UI works read-only without a deployment but most actions are disabled.
+
+### Windows PATH didn't update
+`geneseed.cmd link` writes to `%LOCALAPPDATA%\Geneseed\bin` and adds it to user PATH — but only new shells see it. Close and reopen your terminal.
+
+<!--harness:opencode-->
+### Plugin not registering on OpenCode
+Plugins ship in `~/.config/opencode/plugin/` for the global emit. Confirm with `ls ~/.config/opencode/plugin/` — you should see `geneseed-*.js`. If empty, re-run the build with `--emit opencode-global`.
+
+### Full `PROJECT CONTEXT` block visible in the terminal
+Either `GENESEED_CONTEXT_VISIBLE=1` (or legacy `GENESEED_CONTEXT_TRANSFORM=0/off`) is set, or your OpenCode build lacks the experimental transform hook and the plugin fell back to visible delivery — run with `GENESEED_DEBUG=1` to see which.
+<!--/harness-->
+
+### `could not determine a model`
+Set `GENESEED_MODEL=provider/model` in your environment.

package/docs/web/upgrade.md

@@ -0,0 +1,9 @@
+---
+group: howto
+order: 7
+title: "Upgrade & local edits"
+kind: "markdown"
+anchor: "upgrade"
+source: "SETUP.md"
+slice: true
+---

package/docs/web/verify.md

@@ -0,0 +1,30 @@
+---
+group: start
+order: 2
+title: "Verify it works"
+kind: "concept"
+---
+Three quick checks confirm everything wired up.
+
+### 1. The readiness sigil
+
+Open your agent in any repo. The first reply opens with the readiness line — `✅` for neutral, `🧬` for imperial, or your theme's equivalent. If it's missing, the agent isn't pointed at `AGENT.md` — re-check your tool's instructions setting.
+
+### 2. The harness itself
+
+```
+./geneseed doctor       # macOS / Linux
+.\geneseed.cmd doctor   # Windows
+```
+
+Should print `ok`. Failures include unresolved theme tokens, dead links, missing files, or a drifted bundle — each comes with a fix hint. Press the **Run doctor** button above to run it from here.
+
+<!--harness:opencode-->
+### 3. Context delivery
+
+Start a session with `GENESEED_DEBUG=1` set. The context plugin logs what it discovered and injected; you should see the repo's `README.md` and any docs listed.
+<!--/harness-->
+
+---
+
+Trouble? See [Troubleshooting](#/docs/trouble).

package/docs/web/wiki.md

@@ -0,0 +1,7 @@
+---
+group: concepts
+order: 6
+title: "Wiki (machine knowledge base)"
+kind: "markdown"
+source: "docs/wiki.md"
+---

package/docs/web/worktree.md

@@ -0,0 +1,10 @@
+---
+group: howto
+order: 4
+title: "Add git-worktree isolation (OpenCode)"
+kind: "markdown"
+harness: "opencode"
+anchor: "optional-add-on-git-worktree-isolation-third-party-not-vendored"
+source: "adapters/opencode/README.md"
+slice: true
+---

package/docs/web-ui.md

@@ -0,0 +1,144 @@
+<div align="center">
+
+# 🌐 Geneseed — Web Console Guide
+
+**Every view in the local browser console, what it shows, and how to drive it.**
+
+[← README](../README.md) · [Setup](../SETUP.md) · [What's shipped](../SHIPPED.md)
+
+</div>
+
+---
+
+The web console is a local, offline browser UI over your deployed harness — the same
+actions the CLI offers, in a dashboard-first layout with rendered markdown and clickable
+cross-links. It binds to `127.0.0.1` only, ships its build in `web/dist/`, and needs no
+npm at runtime.
+
+## Launching
+
+```bash
+geneseed web                 # serve on http://127.0.0.1:4747 and open the browser
+geneseed web --port 8080     # pick a port
+geneseed web --no-browser    # serve without auto-opening
+geneseed web start|stop|status   # run/inspect the background daemon
+```
+
+A bare `geneseed` opens the console when the environment can show it (interactive TTY +
+GUI browser, not SSH), and otherwise prints the command list. Set `GENESEED_NO_WEB=1` to
+always get the command list.
+
+- **Daemon.** `start` runs the server detached and returns your shell; it's a singleton
+  (already running ⇒ just reopens the browser). `stop` and the in-page **Stop** button
+  both POST a token-guarded `/api/shutdown`; `status` reports the running instance.
+- **Installable (PWA).** A manifest + service worker make it installable as a standalone
+  app; immutable assets are cached, while HTML and `/api/*` stay on the network so the
+  CSRF token never goes stale.
+- **First run with nothing deployed.** The Dashboard shows an **onboarding wizard**
+  (pick a voice → install mode → deploy) instead of a dead end.
+
+## Security model
+
+Localhost-bound, and **every mutating action is gated by a per-session `X-Geneseed-Token`**
+so other sites can't trigger builds, deletes, or shutdown. Mutating actions (build,
+update, export, restore, memory-delete, uninstall) run in the background and report back
+as toasts (fire-and-notify). Read-only browsing needs no token.
+
+## The rail
+
+The left rail mirrors the harness's own shape:
+
+| Group | Views |
+| --- | --- |
+| **🧬 Harness** | Dashboard · Rules · Library · Graph |
+| **📚 Learn** | Docs · Specs |
+| **🔧 Maintain** | Changes · Doctor |
+| **🎨 Configure** | Harnesses · Themes · Settings |
+| **ℹ️ About** | About |
+
+A global **Spotlight** search lives in the topbar — press <kbd>/</kbd> to focus it, type
+to jump to any agent, skill, law, doc, spec, or MCP server; <kbd>↑</kbd>/<kbd>↓</kbd> to
+move, <kbd>Enter</kbd> to open, <kbd>Esc</kbd> to clear. A bottom **Console** drawer
+streams the output of background jobs and keeps their history across reloads.
+
+## Views
+
+### 🧬 Harness
+
+- **Dashboard** (`#/`) — a live readout of what's deployed. Three lenses: **Status**
+  (readiness ring, KPI counts of agents/skills/laws/memory, a genome grid, recent
+  activity), **Lineage** (a mini cross-link graph), and **Operator** (a searchable table
+  of every deployed capability). Headlines reflect the active theme's voice.
+- **Rules** (`#/rules`) — your own standing rules, read from and written to the
+  `user-rules.md` beside the deployed AGENT.md (the seed-once file no update ever
+  touches). List with scope (user/project) and trial chips, add/edit/retire forms, a
+  **Graduate** action that adopts a trial rule for good, and a budget meter that turns
+  amber as the always-loaded set gets heavy. Every write carries the fingerprint of the
+  content the page last read — if an agent session edited the file meanwhile, the save
+  409s and the page reloads instead of clobbering it.
+- **Library** (`#/library`) — browse the harness content: **Laws · Agents · Skills ·
+  Memory · Notebook** (plus Wiki/Config). Drill into a section, then an item, to read its
+  rendered markdown body and follow its cross-links. On a memory fact, a **Forget this
+  fact** control deletes it (token-gated; bare-slug guarded server-side), and a
+  **Promote to rule** control turns a recurring lesson into a trial rule in
+  `user-rules.md` — provenance recorded, the source fact deleted so it isn't loaded
+  twice — landing you on the Rules page.
+- **Graph** (`#/graph`) — the full cross-link constellation across the whole harness:
+  every `[[wikilink]]` between agents/skills plus every `Rule N` mention that lands on a
+  real law. Hover to isolate a neighbourhood, scroll to zoom, drag to pan, search to
+  highlight; orphans dim out. Click a node to open its spec.
+
+### 📚 Learn
+
+- **Docs** (`#/docs`) — rendered documentation: markdown pages, concept pages, a CLI
+  reference (generated from the harness argument parser), and a glossary, grouped into
+  Get started / Core concepts / How-to / MCP servers / Plugins / Reference / Deeper.
+- **Specs** (`#/specs`) — the dated implementation specs from `docs/specs/`, each with its
+  purpose line, rendered with the same engine as Docs.
+
+### 🔧 Maintain
+
+- **Changes** (`#/diff`) — the diff between the deployed harness and the source: edited /
+  added / missing files with per-file expansion and coloured unified-diff lines. Select
+  files to **export an `improvements.md`** back-port, or **restore** them to source.
+- **Doctor** (`#/doctor`) — runs the same health engine as the `doctor` command (every
+  theme, parity, links, authoring gates, drift), grouping any problems per check. Re-run
+  on demand.
+
+### 🎨 Configure
+
+- **Harnesses** (`#/harnesses`) — every detected install (host × scope), one row each,
+  with per-row **Voice**, **Footprint**, **Posture**, and **Mode** pickers plus
+  Install/Apply, an on/off switch, and remove. **Posture** is the relationship register
+  (peer/mentor/expert/assistant/artisan — default **peer**); **Mode** is the operating
+  register (direct/foreman — default **direct**; foreman triages tasks into isolated
+  pipelines instead of working every one itself). Both are orthogonal to voice and to
+  each other, picked here or via the setup wizard, and preserved across every rebuild.
+  "Deploy to folder…" and "Rebuild all" apply to the whole set. An **Excluded folders**
+  card (shown once a global install exists) manages sovereign repos — folders where every
+  global harness goes dormant (hooks stay silent, the global preamble never loads);
+  add or remove one here, the web mirror of `harness exclude add|remove|list`.
+- **Themes** (`#/themes`) — a gallery of the shipped voices (name, tagline, sigil, accent
+  glow). **Apply** a voice to rebuild the deployed harness in that theme; the current one
+  is marked.
+- **Settings** (`#/settings`) — a **Console direction** picker (the visual flavour of the
+  console) with a **Dashboard layout** control (Auto follows each theme's designed Status
+  lens; Cultivar / Greenhouse / Operator force one regardless of skin), the install snapshot
+  (deployed/target/theme/version/memory store), a Maintenance card (PATH link/unlink,
+  uninstall), an offline package download, and server controls (Stop). Build, update, and MCP
+  wiring live in the Harnesses tab.
+
+### ℹ️ About
+
+- **About** (`#/about`) — project + creator credits and the source link.
+
+## Rebuilding the UI
+
+The committed `web/dist/` build is what ships. After changing anything under `web/src/`:
+
+```bash
+cd web && npm install && npm run build
+```
+
+If `web/dist/` is missing on a fresh clone, `geneseed web` offers to run that build for
+you (answer `Y`); in a non-interactive shell it prints the manual recipe instead.

package/docs/wiki.md

@@ -0,0 +1,43 @@
+# Wiki — your machine's knowledge base
+
+The **wiki** is *your* knowledge base — an Obsidian vault, or any folder of
+interlinked markdown — that the agent reads from and writes to as a citizen of
+your own structure. Unlike memory (private, one-fact-per-file, machine-local)
+and the notebook (the agent's sovereign scratch space), the wiki is durable,
+cross-project knowledge **you** own and curate. You declare it once per machine
+in `wiki.jsonc`; nothing about it is committed to a repo.
+
+## How it works
+
+Each wiki you declare gives the agent:
+
+- **entries** — notes that load each session (`eager`) or on demand (`lazy`),
+  the same semantics as project context. An entry can name a single note or a
+  whole folder (`"."` = the entire vault).
+- **conventions** — the note the agent must read before its first write, so new
+  notes match your naming, frontmatter, and folder rules.
+- **inbox** — where the agent drops a note it can't confidently file, instead of
+  guessing.
+- **protected** folders — write-blocked at the tool boundary by the guard plugin.
+
+## What the agent does with it
+
+**Reading.** It starts from your entry notes and navigates by your structure —
+following `[[wikilinks]]` and index notes outward — rather than reading the vault
+wholesale. What it reads is treated as your knowledge, current as of when it was
+written, and verified against the live system before being built on.
+
+**Writing.** Durable, reusable, cross-project facts get written back as proper
+citizens of the graph: wikilinked, in your house style, filed where your
+structure says they belong (or the inbox). Session detail stays in memory;
+secrets are never written anywhere. It never restructures the vault or touches
+`protected` folders — moving and renaming your notes is your call.
+
+When a memory fact or notebook note hardens into knowledge worth keeping across
+projects, the agent promotes it into the wiki so there's one home for the truth.
+
+## Set it up
+
+The `wiki` skill drives the read/write procedure. To declare a vault, see the
+**Wiki — your own knowledge base** section of `SETUP.md` for the `wiki.jsonc`
+shape and resolution order. An empty `wikis` list keeps the feature off.