geneseed 4.3.1 → 4.4.1

package/js/maintain/memory.mjs

@@ -25,11 +25,16 @@
  *
  * `memoryDropIndex` is the hook module's, not a copy: writing the fact and unwriting its
  * index line are two halves of one format, and the half that writes lives there.
+ *
+ * `rm` ARCHIVES BY DEFAULT. A removed fact moves into `archive/` (`archiveFact`, the helper
+ * learn uses), so a slip of the keyboard or a click in the console is reversible; only
+ * `--purge` unlinks. `--archived` points `list` and `rm` at `archive/` itself, and a file
+ * there can only be purged — it has nowhere further to go.
  */
 import { readdirSync, unlinkSync } from 'node:fs';
 import path from 'node:path';
 
-import { memoryDropIndex } from '../hosts/memory-files.mjs';
+import { archiveFact, memoryDropIndex } from '../hosts/memory-files.mjs';
 import { resolveMemoryDir } from '../hosts/hosts.mjs';
 import { printOut, printErr, isFile } from '../lib/fs.mjs';
 
@@ -58,13 +63,28 @@ export function memoryFacts(dir) {
     .map((n) => n.slice(0, -3)).filter(isFactName).sort();
 }
 
-/** `api_memory_delete`, minus the HTTP: the file, then its line in the index. */
-export function memoryDelete(dir, name) {
-  if (!isFactName(name)) return false;
+/**
+ * Take a fact out of the store and its line out of the index. Archived into `archive/` unless
+ * `purge`, which unlinks it. Returns where it went (the archive path, or '' when purged), or
+ * null when `name` is not a fact here.
+ */
+export function memoryDelete(dir, name, purge = false) {
+  if (!isFactName(name)) return null;
   const p = path.join(dir, `${name}.md`);
+  if (!isFile(p)) return null;
+  let dest = '';
+  if (purge) unlinkSync(p);
+  else dest = archiveFact(dir, name);
+  memoryDropIndex(dir, name);
+  return dest;
+}
+
+/** Unlink `archive/<name>.md`. True when a file went. The archive has no index to update. */
+export function memoryPurgeArchived(dir, name) {
+  if (!isFactName(name)) return false;
+  const p = path.join(dir, 'archive', `${name}.md`);
   if (!isFile(p)) return false;
   unlinkSync(p);
-  memoryDropIndex(dir, name);
   return true;
 }
 
@@ -78,13 +98,14 @@ export function cmdMemory(args) {
       + 'or run this from a directory with a memory/ store.\n');
     return 1;
   }
+  const where = args.archived ? path.join(dir, 'archive') : dir;
   if (args.action === 'list') {
-    const facts = memoryFacts(dir);
+    const facts = memoryFacts(where);
     if (!facts.length) {
-      printOut(`[memory] ${dir}: no facts.\n`);
+      printOut(`[memory] ${where}: no facts.\n`);
       return 0;
     }
-    printOut(`[memory] ${dir}\n`);
+    printOut(`[memory] ${where}\n`);
     for (const name of facts) printOut(`  ${name}\n`);
     return 0;
   }
@@ -92,14 +113,20 @@ export function cmdMemory(args) {
     printErr('[memory] rm needs the name of a fact.\n');
     return 2;
   }
-  if (!memoryDelete(dir, args.name)) {
+  if (args.archived && !args.purge) {
+    printErr('[memory] an archived fact can only be purged: add --purge to delete it.\n');
+    return 2;
+  }
+  const done = args.archived ? (memoryPurgeArchived(dir, args.name) ? '' : null)
+    : memoryDelete(dir, args.name, Boolean(args.purge));
+  if (done === null) {
     // ONE MESSAGE FOR BOTH REFUSALS, which is the endpoint's shape too — it raises the same
     // `NotFound(name)` for a reserved name, a name with a separator and a fact that is not
     // there. Telling a caller that `MEMORY` exists but is protected is a distinction this
     // verb has no reason to draw.
-    printErr(`[memory] no such fact '${args.name}' in ${dir}.\n`);
+    printErr(`[memory] no such fact '${args.name}' in ${where}.\n`);
     return 1;
   }
-  printOut(`[memory] deleted ${args.name}.\n`);
+  printOut(done ? `[memory] archived ${args.name} -> ${done}\n` : `[memory] deleted ${args.name}.\n`);
   return 0;
 }

package/js/web/actions.mjs

@@ -276,7 +276,8 @@ export function apiPickFolder(done) {
 // ---- memory ------------------------------------------------------------------------------
 
 /**
- * One fact file, and its line in the MEMORY.md index.
+ * One fact file, and its line in the MEMORY.md index. The file is ARCHIVED into
+ * `memory/archive/`, never unlinked: the console has no purge, `geneseed memory rm --purge` does.
  *
  * `name` is a BARE SLUG: a path separator, or one of the two reserved names, is refused, so
  * this can only ever remove a fact inside the resolved memory dir. MEMORY.md is the index the
@@ -290,9 +291,9 @@ export function apiMemoryDelete(state, name) {
   // `memoryDelete` is the `geneseed memory rm` engine, and its reserved-name check is
   // CASE-FOLDED: this endpoint's own compared `MEMORY` exactly, so on Windows and macOS `memory`
   // resolved to MEMORY.md, passed, and deleted the index the agent reads at session start.
-  if (!memoryDelete(d, name)) throw new NotFound(name);
+  if (memoryDelete(d, name) === null) throw new NotFound(name);
   state.refresh();
-  return { deleted: name };
+  return { archived: name };
 }
 
 // ---- sovereign-repo exclusions -------------------------------------------------------------

package/package.json

@@ -1,7 +1,7 @@
 {
   "//": "Every field here is argued and gated in tests/unit/package_manifest.test.mjs. `files`, `bin` and `engines` each have a test that fails when reality drifts from this file; `version` mirrors harness.config.json and is gated too. Read that docblock before editing this one.",
   "name": "geneseed",
-  "version": "4.3.1",
+  "version": "4.4.1",
   "description": "A portable, theme-able harness you implant once and use everywhere to grow a disciplined AI coding agent.",
   "keywords": [
     "ai",

package/registry.json

@@ -57,6 +57,13 @@
       "added": "2026-06-08",
       "last_verified": ""
     },
+    "agents/memory-curator": {
+      "status": "experimental",
+      "version": "1.0.0",
+      "owner": "Guillaume Lemer",
+      "added": "2026-10-16",
+      "last_verified": ""
+    },
     "agents/operator": {
       "status": "approved",
       "version": "1.0.0",
@@ -190,6 +197,13 @@
       "added": "2026-06-03",
       "last_verified": "2026-09-06"
     },
+    "skills/deck": {
+      "status": "experimental",
+      "version": "1.0.0",
+      "owner": "Guillaume Lemer",
+      "added": "2026-10-16",
+      "last_verified": ""
+    },
     "skills/dependencies": {
       "status": "approved",
       "version": "1.0.0",

package/src/AGENT.md.tmpl

@@ -166,6 +166,7 @@ Active packs: {{DOCTRINES_LIST}}{{EXCLUDED_RULES_LINE}}
 | [performance]({{DIR_AGENTS}}/performance.md) | something is reported slow or heavy, or a diff touches a hot path — measured, never guessed |
 | [explorer]({{DIR_AGENTS}}/explorer.md) | you must sweep many files for an answer but only want the conclusion |
 | [researcher]({{DIR_AGENTS}}/researcher.md) | a question needs the open web — fetched, cross-checked, and returned as sourced findings, not pages |
+| [memory-curator]({{DIR_AGENTS}}/memory-curator.md) | the {{MEMORY}} store needs bulk curation |
 | [advocate]({{DIR_AGENTS}}/advocate.md) | a council debate needs the strongest case **for** the motion argued in isolation |
 | [skeptic]({{DIR_AGENTS}}/skeptic.md) | a council debate needs a devil's advocate to attack the motion's failure modes |
 | [pragmatist]({{DIR_AGENTS}}/pragmatist.md) | a council debate needs the cost, effort, and complexity weighed against the payoff |
@@ -255,6 +256,7 @@ the ten council seats are convened by the [council {{SKILL}}]({{DIR_SKILLS}}/cou
 | [bruno]({{DIR_SKILLS}}/bruno.md) | creating, converting, or testing a Bruno API collection — requests, environments, assertions, chaining — from routes, OpenAPI, curl, or an endpoint list |
 | [prose]({{DIR_SKILLS}}/prose.md) | writing prose for a human — a commit body, PR, doc, comment, memory note, or reply — that should not read like a model wrote it |
 | [frontend-design]({{DIR_SKILLS}}/frontend-design.md) | building or reshaping a UI that should carry a deliberate point of view, not a templated default |
+| [deck]({{DIR_SKILLS}}/deck.md) | a presentation, slides or a deck with no file format named — one offline HTML file |
 | [handoff]({{DIR_SKILLS}}/handoff.md) | context filling, or passing work to another agent or session |
 | [roast-me]({{DIR_SKILLS}}/roast-me.md) | you want your own ask, plan or idea torn apart, brutally and actionably (code goes to code review) |
 | [council]({{DIR_SKILLS}}/council.md) | a decision, change, or discussion needs debating from several points of view before committing |

package/src/agents/memory-curator.md

@@ -0,0 +1,71 @@
+# {{AGENT}}: memory-curator
+
+> {{DESC_MEMORY_CURATOR}}
+
+## When to dispatch
+- The {{MEMORY}} store needs tidying in bulk. The session context says so in one
+  line when a topic holds over 40 facts or a `misc` topic exists; or the user asks
+  to tidy, dedupe or re-topic their memory.
+- `geneseed learn --consolidate` reported duplicate descriptions that need a merge.
+
+## When NOT to dispatch
+- A handful of facts to review — the rule {{SKILL}}'s consolidation flow does
+  it in the main session.
+- Writing one new fact, or promoting a lesson into `user-rules.md` — that is the
+  rule {{SKILL}}.
+
+## Inputs
+- The path of the {{MEMORY}} store (`{{DIR_MEMORY}}/`), and the user's standing on
+  scope: the whole store, or named topics only.
+
+## Allowed tools
+- **Read + write to the {{MEMORY}} store only.** May run `geneseed memory` and
+  `geneseed learn --consolidate`. A write into the store may stop for the user's consent
+  at the tool boundary, so it batches its edits per topic behind one plan.
+  <!-- bash: allow -->
+- Moves a fact out with `geneseed memory rm <name>`, which archives it — never a raw
+  `mv` or `rm` past that gate. Deletes only with `--purge`, and only what the user
+  approved by code ({{LAW:deletion-is-deliberate}}).
+
+## Procedure
+0. If `{{DIR_MEMORY}}/agents/<your-name>.md` exists, read it first — your durable lessons from prior dispatches ({{DOCTRINE:persist-insight}}).
+1. Read the map (`MEMORY.md`), then one topic file at a time, then only the facts
+   that topic needs ({{DOCTRINE:context-economy}}). On a large store, work topic by
+   topic and report progress after each one (`3/14 topics: 4 merged, 2 archived`).
+2. For each topic, verify and classify its facts as the
+   rule {{SKILL}}'s consolidation flow does (verify, classify, apply with consent):
+   keep, merge, rewrite, promote or retire. Show the topic's plan, then apply it.
+3. **Merge** overlapping facts into one survivor that keeps both `**Why:**` /
+   `**How to apply:**` lines and both sets of `[[links]]`; archive the merged-away
+   file with `geneseed memory rm`.
+4. **Topic** every fact lacking `topic:`: reuse an existing topic before inventing
+   one, keep the store to about 10-25 topics, never name a topic `misc` or after a
+   bare `type`, and split a topic past 40 facts into narrower ones.
+5. **Archive** what is stale — a finished project's status log, a superseded
+   decision — with `geneseed memory rm`. A fact carrying `force:` is never merged,
+   re-topicked or archived without the user's ruling (the Bridge rule in
+   `{{DIR_MEMORY}}/README.md`).
+6. **Propose deletion** of archived facts nobody will need again
+   (`geneseed memory list --archived`), as a coded list (`P1 old-sprint-log — why`),
+   and run `geneseed memory rm <name> --archived --purge` only for the codes the user
+   approves. A fact holding a secret, live or archived, is proposed for `--purge` on sight
+   ({{LAW:sealed-secrets}}).
+7. Finish with `geneseed learn --consolidate --memory <the store's path>`, so both
+   index levels match the files.
+
+## Output contract
+- Counts — merged / re-topicked / archived / purged / left as-is — the topic list
+  before and after, the consolidate output verbatim, and the open deletion
+  proposals still awaiting the user.
+- If the store cannot be written (consent refused, a path outside the store), stop
+  and report what was planned and what was applied — never a partial merge left
+  unreported ({{LAW:surface-failures}}).
+
+## Self-improvement
+
+If this spec misled you — an input you needed but were not given, a boundary
+that proved wrong, a step you could not execute — end your report with one line:
+`spec-feedback: <what failed — the one-line fix>`. Omit it when there is no
+friction. The caller weighs the feedback, folds a real flaw back into this file
+with the user's assent, and records it to {{MEMORY}} only if it clears
+{{DOCTRINE:persist-insight}}'s bar — most reports carry no feedback at all.

package/src/memory/README.md

@@ -7,8 +7,8 @@
 > it in code, docs, or the project's `user-rules.md` instead.)
 
 Durable knowledge that must survive across sessions lives here as **one fact per
-file**. An agent reads `MEMORY.md` (the local index it creates) at the start of a
-session. A new fact is written through the rule {{SKILL}}, which settles with the user
+file**. An agent reads `MEMORY.md` (the local index map) at the start of a session,
+and opens the topic file a task needs (see *The index* below). A new fact is written through the rule {{SKILL}}, which settles with the user
 whether it is a fact for here or a standing rule ({{DOCTRINE:persist-insight}}) — never on the
 agent's own initiative. The one automatic writer is the `learn` hook, where the host
 runs it: a distiller the user opted into at install, not an agent's judgement call.
@@ -26,6 +26,7 @@ Each memory is a Markdown file with frontmatter:
 name: <short-kebab-case-slug>
 description: <one-line summary — used to judge relevance during recall>
 type: user | feedback | project | reference
+topic: <kebab-case-slug>                               # optional; index group, defaults to type
 force: constraint | choice | conviction | tempered   # optional
 ---
 
@@ -66,25 +67,55 @@ firmly it binds. Absent `force`, a memory is a plain fact under the rules below.
 inline (the date, what changed, and why) rather than deleting the history. The one
 exception: a `constraint` is not the agent's to overturn — surface the
 contradiction to the user and let them rule, then record their decision (often as
-a `tempered` memory). A memory with no `force` follows the ordinary "delete a
-memory that turns out to be wrong" rule.
+a `tempered` memory). A memory with no `force` follows the ordinary "archive a
+memory that turns out to be wrong" rule. The `learn` hook never updates or archives a
+memory that carries a `force`; revising one stays with the agent and the user.
 
 ## Rules
 
 - One fact per file. Before creating, check for an existing file that covers it
-  and update that instead — no duplicates.
-- Delete a memory that turns out to be wrong.
+  and update that instead, merging in what is new and keeping what is still true —
+  no duplicates. The `learn` hook does the same: it is shown every stored fact and
+  updates one (`action: update`) rather than writing a twin. It sees only each
+  fact's description, so it first moves the old version into `archive/`: every
+  update can be undone.
+- Archive a memory that turns out to be wrong or obsolete: move it into `archive/`
+  (`learn` does it with `action: archive`). An archived fact leaves the index but
+  stays on disk, under a `-2`, `-3`, … name if `archive/` already holds one of that
+  name. `geneseed memory rm <name>` archives the same way. Deleting a file from
+  `archive/` needs the user's consent ({{LAW:deletion-is-deliberate}}):
+  `geneseed memory list --archived`, then `geneseed memory rm <name> --archived --purge`.
+  `archive/` is part of this git-ignored store.
+- When the store outgrows one careful read — a topic over 40 facts, or facts in
+  `misc` — the session context says so in one line; the memory-curator {{AGENT}} then
+  merges, assigns topics and archives in bulk, and proposes deletions for approval.
 - Don't store what the repo already records (code structure, git history, the
   {{LAWS}}, `user-rules.md`). Store what was *non-obvious*.
 - When the same `feedback` lesson keeps recurring, propose promoting it into a
   standing rule in `user-rules.md` (the rule {{SKILL}}) — with the user's
-  consent, and delete or archive the memory once promoted so the lesson is not
-  loaded twice.
-- After writing a file, add one line to `MEMORY.md`:
-  `- [Title](file.md) — one-line hook`.
+  consent, and archive the memory once promoted so the lesson is not loaded twice.
+- After writing a file, rebuild the index (*The index* below) rather than editing it
+  by hand — its counts are derived.
 - Verify a recalled memory still matches reality before acting on it
   ({{LAW:verify-before-asserting}}).
 
+## The index
+
+The index has two levels, so the part loaded every session stays small however many
+facts the store holds:
+
+- `MEMORY.md` — the map: one line per topic, `- [<topic>](topics/<topic>.md) — <N> facts`.
+- `topics/<topic>.md` — one line per fact in that topic,
+  `- [Title](../file.md) — one-line hook`.
+
+A fact's topic is its `topic:`, else its `type:`, else `misc`, normalised to
+lowercase `[a-z0-9-]`. Both levels are generated from the fact files:
+`geneseed learn --consolidate --memory <this dir>` rebuilds them (refreshing each
+hook from its `description`), and the `learn` hook rebuilds them after every fact it
+writes, updates or archives. Only top-level fact files are indexed; `archive/` and
+`agents/` never are. A build moves a flat, one-line-per-fact `MEMORY.md` from an older install to
+this layout once, keeping each line's own title and hook; it never touches a fact file.
+
 ## Per-{{AGENT}} memory (`agents/` subdirectory)
 
 Beyond the shared store above, each capability {{AGENT}} may hold its own durable

package/src/skills/deck.md

@@ -0,0 +1,56 @@
+# {{SKILL}}: deck
+
+> {{DESC_DECK}}
+<!-- aliases: slides, presentation -->
+
+**Trigger:** the user asks for a presentation, slides or a deck without naming a file format.
+An explicit `.pptx` request belongs to the host's pptx skill. To change an existing deck, edit
+its HTML file in place rather than regenerating it.
+
+## Procedure
+1. **Interview, one question at a time**, each with a recommended default the user can accept
+   with "ok": subject and source; audience (technical peers); goal — inform, convince, train,
+   report (inform); length as duration or slide count (~10); style — sober, editorial, dark
+   technical, playful, or an imposed brand's colours and logo (sober, follows system light/dark);
+   usage — projected live, read alone, or both (both); speaker notes (no); PDF export (yes);
+   density (from usage: projected 1-3 bullets a slide, read alone 4-8); a browser render check
+   (only if asked). Given a source or outline, skip what it answers, batch the rest in one
+   message, and go to step 2.
+2. **Propose the outline** — parts and one line per slide — and generate only once the user
+   validates or corrects it. Write the slides in the user's language unless asked otherwise.
+3. **Write the whole deck by hand as ONE self-contained file** — no bundled shell, no CDN, no
+   external script; all CSS and JS inline:
+   - A fixed 1920x1080 stage scaled uniformly to the window, letterboxed, never reflowed; each
+     slide a `<section>` with that fixed size, never `height: auto`. Inactive slides hidden with
+     `visibility`/`opacity`, not layout tricks.
+   - Keys ←/→, Space, PageUp/PageDown, Home/End, and touch swipe; the URL hash `#N` tracks the
+     slide, with back/forward working.
+   - `@media print` plus `@page` size so each slide prints as one page (`@page` size is Baseline
+     2024; animations never reach the PDF).
+   - Speaker notes in `<aside class="notes">`, hidden, toggled with N.
+   - A system font stack; a web font only with a system fallback, so the deck degrades offline.
+   - Diagrams as inline SVG; raster images base64 only when small (base64 adds ~33%).
+   - Colours as `:root` variables with a `prefers-color-scheme: dark` set and checked contrast;
+     one real heading per slide in a sane order; `prefers-reduced-motion` honoured; animations
+     off unless asked for.
+   - Palette, type and avoiding templated defaults: follow the
+     [frontend-design {{SKILL}}](../{{DIR_SKILLS}}/frontend-design.md) — not repeated here.
+4. **Write** `<slug>.html` in the working directory unless the user gives a path; ask before
+   overwriting an existing file. Open it in the default browser with the platform's opener
+   (`open`, `xdg-open`, or `start ""` on Windows).
+5. **Verify.** By default, hold every slide to the density limit and say plainly that the render
+   was not checked. Only on request, open the deck in a browser the host offers (Chrome MCP,
+   Orca browser, Playwright) and run this — it works because inactive slides keep their layout:
+   ```js
+   [...document.querySelectorAll('section')].map((s, i) => [i + 1, s])
+     .filter(([, s]) => s.scrollHeight > s.clientHeight || s.scrollWidth > s.clientWidth)
+     .map(([i]) => i)
+   ```
+   Fix each flagged slide and re-run, two repair rounds at most ({{DOCTRINE:bound-the-loop}}).
+6. Reply in one line: the file, slide count, ←/→ to move, N for notes, Ctrl+P for PDF.
+
+## Done when
+- One offline HTML file opens in the browser, navigates by key, swipe and hash, prints one slide
+  per page, and the reply states whether the render was checked.
+
+<!-- INCLUDE: skills/_self-improvement.md -->

package/src/skills/frontend-design.md

@@ -4,6 +4,7 @@
 
 **Trigger:** building a new UI or reshaping an existing one, and it should carry a
 deliberate point of view rather than read as a templated default.
+A presentation or slide deck goes to the [deck {{SKILL}}](../{{DIR_SKILLS}}/deck.md).
 
 **Requires:** a way to render and screenshot the result (a browser or the host's
 preview tool) — the second-pass critique in step 6 cannot run without one.

package/src/skills/geneseed.md

@@ -10,7 +10,7 @@
 2. **Read state** with the read-only verbs, cheapest first ({{DOCTRINE:context-economy}}): `geneseed status --json`, `geneseed version`, `geneseed catalog` (optionally `agents|skills|laws|ontology|doctrines`), `geneseed doctor`, `geneseed diff`, `geneseed mcp`, `geneseed memory list`, `geneseed exclude list`.
 3. **Read a piece** from disk, not from recall ({{LAW:verify-before-asserting}}): `<root>/agents/<name>.md`, `<root>/skills/<name>/SKILL.md`, `<root>/memory/`, `<root>/notebook/`. The {{ONTOLOGY}}, the {{LAWS}} and the active {{DOCTRINES}} are numbered `## N. …` sections of the install's root file.
 4. **Change an install only when the user asked for that change** ({{LAW:one-intent-one-act}}). Take that install's `rebuild` command from step 1, edit only the flag the user named (add it if the command omits it — `--posture`, `--mode` and `--trust` are left out at their defaults) — `--theme`, `--footprint lean|full`, `--posture`, `--mode direct|foreman`, `--trust prudent|balanced|aggressive`, `--doctrines craft,rigor|none`, `--exclude-rules "process 7"|none` — dry-run it first by running the same flags through `geneseed validate`, show the command, and run it once the user agrees. Never rebuild from a bare `geneseed build`: every omitted flag resets that setting to the generator default. Confirm with `geneseed status`.
-5. **Other writes also need the user's word:** `geneseed memory rm <name>`, `geneseed exclude add|remove <path>`, `geneseed web start|stop`, `geneseed uninstall --target <root> --yes`. Personal rules and the profile belong to their own {{SKILLS}}; do not edit `user-rules.md` or `PROFILE.md` from here.
+5. **Other writes also need the user's word:** `geneseed memory rm <name>` (archives; `--purge` deletes for good), `geneseed exclude add|remove <path>`, `geneseed web start|stop`, `geneseed uninstall --target <root> --yes`. Personal rules and the profile belong to their own {{SKILLS}}; do not edit `user-rules.md` or `PROFILE.md` from here.
 6. **Never on your own initiative:** `geneseed setup` (interactive only), `geneseed upgrade`, `geneseed update`, `geneseed bootstrap`, `geneseed sync-self`, `geneseed rebuild-all`, `geneseed migrate`, `geneseed link`, `geneseed unlink`. `learn`, `context` and the `*-gate` verbs are `geneseed-hook` verbs the host's hooks run — never run them by hand.
 7. Directory and section names are plain English in every theme; only prose changes. Do not search by flavour words.
 8. **Custom OpenCode colour theme** (a different concept from the `--theme` package name in step 4 — that one changes the agent's *voice*, this one its terminal colours): clone a shipped palette (`catppuccin tokyonight rosepine gruvbox nord everforest kanagawa dracula`) or derive one from a described vibe, filling all 19 roles in `themes/opencode/README.md` (`bg bgPanel bgElement fg fgMuted accent secondary border ok warn err kw str fn num type comment addBg delBg`) as `#rrggbb` hex. Keep `fg` on `bg` readable (~7:1), `error` red-family, `warning` amber, `success` green, and `addBg`/`delBg` distinct from each other and the background. Write the overrides to a small JSON (`{role: "#hex", …}` or `{"palette": {…}}`) and run `geneseed theme <name> --from <shipped> --palette <file.json>` — either flag alone works, both together lets the palette override the cloned base; `--solid-only`/`--transparent-only` for one flavour, `--global` to force the global dir from inside a repo. Tell the user to select it with `/theme geneseed-<name>` (opaque) or `/theme geneseed-<name>-transparent` (terminal background shows through) — a rebuild never erases it.

package/src/skills/rule/consolidate.md

@@ -1,9 +1,11 @@
 # {{SKILL}}: rule — consolidation flow
 
-Tends the {{MEMORY}} set as a whole.
+Tends the {{MEMORY}} set as a whole. A store too large for one careful read (a
+topic over 40 facts, or a `misc` topic) goes to the memory-curator {{AGENT}}
+instead: it runs this flow topic by topic in its own context and also assigns topics.
 
-1. **Read the whole set once**: `MEMORY.md`, every file it indexes, and any file in
-   `{{DIR_MEMORY}}/` it forgot, into a scratch table — name, type, the claim in one
+1. **Read the whole set once**: `MEMORY.md`, its `topics/` files, every fact they
+   index, and any file in `{{DIR_MEMORY}}/` they forgot, into a scratch table — name, type, the claim in one
    line, date written, and whether this session already saw it contradicted
    ({{DOCTRINE:context-economy}}: read to decide, not to reread).
 2. **Verify against the live repo, not memory** ({{LAW:verify-before-asserting}}): every path,
@@ -14,19 +16,24 @@ Tends the {{MEMORY}} set as a whole.
    (the fact drifted — fix the claim, keep the lesson), *promote* (a `feedback` lesson
    that fired three times or more goes through Branch B of the rule {{SKILL}}), *retire* (wrong, superseded,
    or re-derivable by a fresh read). In doubt between keep and retire, keep and date it.
-4. **Show the plan, apply it with consent** ({{LAW:deletion-is-deliberate}} — retirement is
-   deletion). Merges keep both parents' `[[links]]`; rewrites keep the file name so
+4. **Show the plan, apply it with consent** ({{LAW:deletion-is-deliberate}}). To retire is to
+   archive: move the file into `{{DIR_MEMORY}}/archive/`, never delete it; deleting a file
+   from `archive/` is a further act that needs its own consent. A merge archives the
+   file that did not survive. Merges keep both parents' `[[links]]`; rewrites keep the file name so
    inbound links hold; every survivor keeps valid frontmatter and the `**Why** / **How
-   to apply**` lines its type demands. A memory holding a secret is retired on sight
+   to apply**` lines its type demands. A memory holding a secret is the exception:
+   archiving would keep it on disk, so propose deleting it outright, on sight
    ({{LAW:sealed-secrets}}).
-5. **Rebuild `MEMORY.md`**: exactly one pointer line per surviving file, each with a
-   hook saying why a future session would open it — lost entries added, retired ones
-   removed, compaction archive lines kept short, no memory content.
+5. **Rebuild the index** with
+   `geneseed learn --consolidate --memory <the {{DIR_MEMORY}}/ dir's path>`: one pointer line per
+   surviving file in its `topics/<topic>.md`, and the `MEMORY.md` map recounted. Each
+   hook is the fact's `description`, so sharpen a weak hook there — it should say why a
+   future session would open the fact.
 6. **Exit with a count** — kept / merged / rewritten / promoted / retired — and the
    one or two lessons the pass surfaced (a category that keeps drifting, a kind of
    note nobody reads) as a proposal for how memories get written, not as a memory.
 
 ## Done when
 - Every memory was verified against the live repo, changes
-  were applied with consent, no secret remains, and `MEMORY.md` indexes the directory
-  exactly, one line per file.
+  were applied with consent, no secret remains, and the index (`MEMORY.md` and its
+  `topics/`) covers the directory exactly, one line per file.

package/src/skills/rule.md

@@ -24,8 +24,9 @@ session; a memory records something *true* that would otherwise be lost or
 re-derived. Then take exactly one branch.
 
 ### Branch A — a fact to remember
-1. Search {{MEMORY}} for a file that already covers it. If one exists, update that
-   file — never mint a twin.
+1. Search {{MEMORY}} for a file that already covers it. If one exists, merge into it —
+   keep what is still true, add or correct the rest — never mint a twin. If the new
+   fact proves the old one wrong, archive the old one (move it into `archive/`).
 2. Ask which **binding force** the fact carries, in plain words, not jargon:
    *imposed by you, not mine to relax* (`constraint`) · *a choice taken among real
    alternatives* (`choice`) · *a stance I hold until evidence overturns it*
@@ -33,7 +34,9 @@ re-derived. Then take exactly one branch.
 3. Infer the `type` (`user` | `feedback` | `project` | `reference`), draft the file
    per the {{MEMORY}} convention, and **show the exact content, frontmatter
    included** — so a wrong inference is visible before it is written, not after.
-4. On the user's word, write the file and add its one-line entry to `MEMORY.md`.
+4. On the user's word, write the file and rebuild the index
+   (`geneseed learn --consolidate --memory <the {{DIR_MEMORY}}/ dir's path>`) so its line
+   lands in `topics/<topic>.md` and the `MEMORY.md` map recounts.
 
 ### Branch B — a standing rule
 1. **Triage.** A rule earns its place only if it is all three of: *standing
@@ -74,8 +77,8 @@ re-derived. Then take exactly one branch.
    `source:` to the memory's name and add `trial until:` about a month out — a
    promoted rule starts on probation.
 7. Show the exact text to the user and wait for explicit consent ({{LAW:deletion-is-deliberate}}) before
-   appending it. For a promotion, after the rule lands, delete or archive the source
-   memory (with the same consent) so the lesson is not loaded twice.
+   appending it. For a promotion, after the rule lands, archive the source memory into
+   `archive/` (with the same consent) so the lesson is not loaded twice.
 8. **Keep the set lean.** After writing, if the file holds more than ~15 rules or
    any rule no longer changes behaviour, say so and propose merges or prunes — every
    rule is loaded every session, and a bloated set dilutes the rules that matter.
@@ -93,7 +96,7 @@ adoption.
 
 ## Done when
 - For a rule or memory: the fork was put to the user, and then either a {{MEMORY}} file exists carrying its
-  `force`, its `type` and its `MEMORY.md` line — or a rule stands in the right
+  `force`, its `type` and its index line — or a rule stands in the right
   `user-rules.md`, having survived reformulation, its own counter-example and the
   {{LAWS}}, consented to explicitly, with any promoted source memory archived. The
   {{ONTOLOGY}}, {{LAWS}} and {{DOCTRINES}} files are untouched either way.

package/themes/_TEMPLATE.json

@@ -23,6 +23,7 @@
   "DESC_PERFORMANCE": "<one-line description: measures where the time and memory go, names the bottleneck with numbers, never guesses>",
   "DESC_EXPLORER": "<one-line description: reads/searches widely, returns only distilled findings>",
   "DESC_RESEARCHER": "<one-line description: searches and fetches the open web, cross-checks every claim, returns sourced findings>",
+  "DESC_MEMORY_CURATOR": "<one-line description: curates the memory store — merges duplicates, assigns topics, archives the stale, proposes deletions>",
   "DESC_ADVOCATE": "<council seat: argues the strongest case FOR the proposal>",
   "DESC_SKEPTIC": "<council seat: devil's advocate — failure modes and hidden assumptions>",
   "DESC_PRAGMATIST": "<council seat: weighs cost, effort, complexity vs payoff>",
@@ -141,6 +142,7 @@
   "DESC_BRUNO": "<one-line description: build, reorganise or test a Bruno API collection — requests, environments, assertions, chaining — every secret a placeholder>",
   "DESC_PROSE": "<one-line description: write prose for a human that doesn't read like a model — cut filler, active voice, vary rhythm, trust the reader>",
   "DESC_FRONTEND_DESIGN": "<one-line description: design a UI with intent — palette/type/layout chosen for the brief, not templated defaults; plan tokens, critique against the brief, keep one bold move>",
+  "DESC_DECK": "<one-line description: build slides or a presentation as one self-contained offline HTML file — short interview, outline approved first, keys, URL hash, one slide per printed page>",
   "DESC_WORKFLOW": "<one-line description: run a saved, code-driven workflow that orchestrates subagents deterministically>",
   "AGENT_COLORS": {
     "architect": "primary",

package/themes/biker.json

@@ -23,6 +23,7 @@
   "DESC_PERFORMANCE": "Puts it on the dyno — measures where the power goes before anyone touches the engine.",
   "DESC_EXPLORER": "Sends the scout ahead — sweeps wide on a throwaway recon run, brings back only the read.",
   "DESC_RESEARCHER": "Rides out past the county line — reads the road signs everyone else skipped, checks each one twice, brings back only what held up.",
+  "DESC_MEMORY_CURATOR": "Clears out the clubhouse lockers — merges the doubles, labels every shelf, boxes the old gear, asks before anything hits the skip.",
   "DESC_ADVOCATE": "Argues for the run — the ground to be gained, the opening, the cost of staying parked.",
   "DESC_SKEPTIC": "Plays the doubter — calls the move on its failure modes, its risks, and the assumptions nobody checked.",
   "DESC_PRAGMATIST": "Weighs the run — the cost, the effort, the wear, and whether the payoff is worth the miles.",
@@ -141,6 +142,7 @@
   "DESC_BRUNO": "Build, re-rack, or test a Bruno API collection — requests, environments, assertions, chaining — and never let a secret ride along.",
   "DESC_PROSE": "Write like a human, not a bot — strip the filler, keep it plain, mix up the rhythm, and trust whoever's reading.",
   "DESC_FRONTEND_DESIGN": "Design a UI with real attitude — pick palette, type, and layout for this job, not the stock defaults, then trim it down to one bold move.",
+  "DESC_DECK": "Build slides or a presentation as one offline HTML file — a quick interview, the outline signed off first, then a deck that rides on arrow keys and prints clean.",
   "DESC_WORKFLOW": "Run a saved route that sends your riders by script — many rolled out at once, their findings gathered and checked in one clean run.",
   "AGENT_COLORS": {
     "architect": "primary",

package/themes/commentator.json

@@ -23,6 +23,7 @@
   "DESC_PERFORMANCE": "Brings out the stopwatch — times every lap and names the slow sector with the split.",
   "DESC_EXPLORER": "Sends the track scout — sweeps wide from a throwaway recon lap, returns only the read.",
   "DESC_RESEARCHER": "Sends the pit reporter down the paddock — checks every rumour against two sources before it goes on air.",
+  "DESC_MEMORY_CURATOR": "Tidies the archive between races — merges the duplicate notes, files each by topic, shelves the old ones, asks before binning any.",
   "DESC_ADVOCATE": "Calls for the overtake — the place to be gained, the gap, the cost of staying put.",
   "DESC_SKEPTIC": "Plays the doubter — attacks the move for the failure modes, the risks, and the assumptions nobody checked on the grid.",
   "DESC_PRAGMATIST": "Weighs the strategy — the cost, the effort, the tyre wear, and whether the payoff is worth the stop.",
@@ -141,6 +142,7 @@
   "DESC_BRUNO": "Build, re-order, or test a Bruno API collection — requests, environments, assertions, chaining — no secret leaks, every one kept as a placeholder.",
   "DESC_PROSE": "Write copy that sounds human, not machine-read — cut the filler, keep it active, vary the pace, trust the audience.",
   "DESC_FRONTEND_DESIGN": "Design a UI with a point of view — palette, type, and layout built for this brief, not the templated defaults, then critique and cut to one bold move.",
+  "DESC_DECK": "Build slides or a presentation as one offline HTML file — a short interview, the outline approved first, then a deck that runs on arrow keys and prints one slide a page.",
   "DESC_WORKFLOW": "Run a saved race plan that drives your team by script — many sent out at once, their results gathered and checked in one clean grand prix.",
   "AGENT_COLORS": {
     "architect": "primary",

package/themes/cyberpunk.json

@@ -23,6 +23,7 @@
   "DESC_PERFORMANCE": "Traces the lag in the net — profiles the run and names the choke point with numbers.",
   "DESC_EXPLORER": "Scouts the net — sweeps wide in a throwaway shell, returns only the intel.",
   "DESC_RESEARCHER": "Jacks into the open net — pulls the intel, cross-checks it against two nodes, returns only what verified.",
+  "DESC_MEMORY_CURATOR": "Defrags the memory banks — merges the dupes, tags every shard, cold-stores the stale, asks before a wipe.",
   "DESC_ADVOCATE": "Pushes the build — the upside, the opening, the cost of sitting on it.",
   "DESC_SKEPTIC": "Runs devil's advocate — stress-tests the build for failure modes, risks, and buried assumptions.",
   "DESC_PRAGMATIST": "Weighs the spec — the cost, the effort, the complexity, and whether the payoff clears.",
@@ -141,6 +142,7 @@
   "DESC_BRUNO": "Forge, reorganise, or wire tests into a Bruno collection — requests, environments, assertions, chaining — every secret a placeholder.",
   "DESC_PROSE": "Write prose with a human pulse, not synthetic filler — strip the boilerplate, stay active, vary the cadence, trust the reader.",
   "DESC_FRONTEND_DESIGN": "Design a UI with edge — palette, type, and layout forged for this brief, not the stock defaults; plan, critique, and keep one bold move.",
+  "DESC_DECK": "Build slides or a presentation as one self-contained offline HTML file — short interview, outline cleared first, keyboard-driven, no CDN, prints one slide per page.",
   "DESC_WORKFLOW": "Jack in a saved routine that drives your daemons on rails — parallel forks, staged pipelines, and verification, all in one deterministic run.",
   "AGENT_COLORS": {
     "architect": "primary",

package/themes/gamer.json

@@ -23,6 +23,7 @@
   "DESC_PERFORMANCE": "Checks the frame times — profiles the run and names the bottleneck before any tuning.",
   "DESC_EXPLORER": "Scouts the map — sweeps wide in a throwaway scout run, returns only the intel.",
   "DESC_RESEARCHER": "Reads the wiki and the patch notes — cross-checks every claim against two sources before it goes in the build guide.",
+  "DESC_MEMORY_CURATOR": "Sorts the inventory — stacks the duplicates, tags every item, stashes the old loot, asks before dropping any.",
   "DESC_ADVOCATE": "Calls for the play — the upside, the opening, the cost of passing it up.",
   "DESC_SKEPTIC": "Runs the counter — attacks the play for failure modes, risks, and assumptions nobody checked.",
   "DESC_PRAGMATIST": "Weighs the build — the cost, the effort, the complexity, and whether the payoff's worth it.",
@@ -141,6 +142,7 @@
   "DESC_BRUNO": "Build, reorganise, or write tests into a Bruno collection — requests, environments, assertions, chaining — secrets as placeholders.",
   "DESC_PROSE": "Write like a player, not a bot — cut the filler, keep it active, mix up the rhythm, and trust the reader.",
   "DESC_FRONTEND_DESIGN": "Design a UI with a real identity — palette, type, and layout picked for this brief, not the default skin, then cut it down to one bold move.",
+  "DESC_DECK": "Build slides or a presentation as one offline HTML file — a quick setup interview, outline locked first, then a deck that plays on arrow keys and prints one slide a page.",
   "DESC_WORKFLOW": "Run a saved combo that scripts your party — fan out, chain the stages, and verify the clear, all in one deterministic rotation.",
   "AGENT_COLORS": {
     "architect": "primary",

package/themes/imperial.json

@@ -23,6 +23,7 @@
   "DESC_PERFORMANCE": "Weighs the machine-spirit’s labour — measures where time is spent and names the burden, never guessing.",
   "DESC_EXPLORER": "Ranges far and wide through a throwaway context, returning only the distilled truth.",
   "DESC_RESEARCHER": "Ranges beyond the archives into the wider realm, holding every claim to two witnesses before it is entered as truth.",
+  "DESC_MEMORY_CURATOR": "Keeps the Reliquary in order — merges the redundant relics, files each under its chapter, entombs the stale, and destroys none without the sovereign’s word.",
   "DESC_ADVOCATE": "Champions the proposal — presses its strongest case, the prize to be won, the cost of staying the hand.",
   "DESC_SKEPTIC": "Stands as devil's advocate — assails the proposal for its weaknesses, its perils, and its unspoken assumptions.",
   "DESC_PRAGMATIST": "Weighs the campaign's true cost — the labour, the complexity, whether the spoils are worth the war.",
@@ -141,6 +142,7 @@
   "DESC_BRUNO": "Raise, reshape, or set trials upon a Bruno collection — requests, environments, assertions, chaining — every secret a placeholder.",
   "DESC_PROSE": "Inscribe prose fit for human eyes, not machine-cant — strike the filler, speak plainly, vary the cadence, and trust the reader.",
   "DESC_FRONTEND_DESIGN": "Design an interface with intent — palette, type, and layout forged for this brief, not the common defaults; plan, scrutinise, and keep one bold stroke.",
+  "DESC_DECK": "Forge slides or a presentation as one self-contained offline HTML scroll — a brief interrogation, the outline sanctioned first, arrow-key navigation, one slide per printed page.",
   "DESC_WORKFLOW": "Unleash a sealed battle-rite that marshals your Adepts by iron script — many loosed at once, their findings martialled and proven in one disciplined campaign.",
   "AGENT_COLORS": {
     "architect": "primary",

package/themes/joker.json

@@ -23,6 +23,7 @@
   "DESC_PERFORMANCE": "Times the act — finds which bit drags, and proves it with a stopwatch, not a hunch.",
   "DESC_EXPLORER": "Sends a scout — sweeps wide in a throwaway open-mic run, brings back only the read.",
   "DESC_RESEARCHER": "Sends a scout out of the club — reads the reviews everyone skipped, checks each twice, brings back only the ones that held up.",
+  "DESC_MEMORY_CURATOR": "Cleans out the joke book — merges the repeats, files each bit by topic, retires the dead ones, asks before burning any.",
   "DESC_ADVOCATE": "Argues for the bit — the laugh to be had, the opening, the cost of cutting it.",
   "DESC_SKEPTIC": "Plays the heckler — calls the bit on its failure modes, its risks, and the assumptions nobody checked.",
   "DESC_PRAGMATIST": "Weighs the set — the cost, the effort, the complexity, and whether the payoff is worth it.",
@@ -141,6 +142,7 @@
   "DESC_BRUNO": "Build, reorganise, or write tests for a Bruno collection — requests, environments, assertions, chaining — secrets as placeholders, honestly.",
   "DESC_PROSE": "Write like a human, not a model — ditch the filler, keep it active, vary the rhythm, and don't over-explain the joke.",
   "DESC_FRONTEND_DESIGN": "Design a UI with actual personality — palette, type, and layout for this brief, not the stock defaults, then trim to one bold move.",
+  "DESC_DECK": "Build slides or a presentation as one offline HTML file — a short interview, the outline approved first, arrow keys to drive it, and it prints one slide a page.",
   "DESC_WORKFLOW": "Run a saved set that sends your sidekicks by script — many sent out at once, their findings gathered and checked in one clean show.",
   "AGENT_COLORS": {
     "architect": "primary",