@esneiderbravo/speclaw 0.1.0 → 0.1.2

package/README.md

@@ -1,6 +1,6 @@
 <div align="center">
 
-<img src="brand/speclaw-banner.svg" width="820" alt="speclaw — where specs become law">
+<img src="https://raw.githubusercontent.com/esneiderbravo/speclaw/main/brand/speclaw-banner.png" width="820" alt="speclaw — where specs become law">
 
 <br/>
 
@@ -37,17 +37,21 @@ One command. No cloud, no LLM, no API keys — <b>everything runs on your machin
 
 ## ◆ Quick start
 
+In your project root:
+
+```bash
+npx @esneiderbravo/speclaw init
+```
+
 <p align="center">
-  <img src="brand/terminal-quickstart.svg" width="800" alt="npx @esneiderbravo/speclaw init">
+  <img src="https://raw.githubusercontent.com/esneiderbravo/speclaw/main/brand/terminal-quickstart.png" width="800" alt="npx @esneiderbravo/speclaw init">
 </p>
 
-<p align="center">Copy &amp; run in your project root: <code>npx @esneiderbravo/speclaw init</code></p>
-
 `init` will:
 
 1. **Ask which agents you use** (Claude Code, Cursor, Codex, …) — and configure
    only those. Add more later; nothing is forced on you.
-2. Write the **foundation** (constitution + standards) and the **spec workflow**.
+2. Write the **foundation** (constitution + standards) and the **lawbook workflow**.
 3. **Index your code** with a live progress bar and a summary of what it found.
 4. Register the speclaw **MCP server** in each chosen agent's config.
 5. Print a prompt to paste into your agent so it fills the constitution with your
@@ -60,7 +64,7 @@ Works with `npm`, `pnpm` (`pnpm dlx @esneiderbravo/speclaw init`), and `yarn`.
 ## ◆ It looks like this
 
 <p align="center">
-  <img src="brand/terminal-init.svg" width="800" alt="speclaw init — terminal output">
+  <img src="https://raw.githubusercontent.com/esneiderbravo/speclaw/main/brand/terminal-init.png" width="800" alt="speclaw init — terminal output">
 </p>
 
 <p align="center"><i>Teal steps, green checks, a live progress bar — themed with the speclaw palette.</i></p>
@@ -71,12 +75,12 @@ Works with `npm`, `pnpm` (`pnpm dlx @esneiderbravo/speclaw init`), and `yarn`.
 
 | Module | What it does |
 | :-- | :-- |
-| **Foundation** | The project's constitution: `LAWS.md` binding a set of granular standards under `docs/standards/` (base, architecture, backend, frontend, testing, documentation, conventions, spec-workflow), plus strict `CLAUDE.md` / `AGENTS.md` agent contracts — filled from your real codebase. |
+| **Foundation** | The project's constitution: `LAWS.md` binding a set of granular standards under `docs/standards/` (base, architecture, backend, frontend, testing, documentation, conventions, lawbook), plus strict `CLAUDE.md` / `AGENTS.md` agent contracts — filled from your real codebase. |
 | **Compass** | speclaw's own local code graph. Parses your code (tree-sitter) into nodes + edges plus a local vector store, so an agent finds and understands code with a fraction of the tokens a grep/read loop would cost. No LLM, 100% local, lives in `.speclaw/` (gitignored). |
-| **Spec** | speclaw's own spec-driven workflow: `draft → build → sync → archive` (and `explore`), backed by `spec_*` engine tools. No external CLI. |
+| **Lawbook** | speclaw's own spec-driven workflow: `draft → build → sync → archive` (and `explore`), backed by `lawbook_*` engine tools. No external CLI. |
 | **Tools** | Opt-in packs of skills and subagents (currently the dev-agents) that agents use for specific tasks. |
 
-Compass is inspired by [CodeGraph](https://github.com/colbymchenry/codegraph) and the Spec module by [OpenSpec](https://github.com/Fission-AI/openspec) — both MIT. speclaw reimplements the ideas as its own code and gives full credit; see [ATTRIBUTION.md](ATTRIBUTION.md).
+Compass is inspired by [CodeGraph](https://github.com/colbymchenry/codegraph) and the Lawbook module by [OpenSpec](https://github.com/Fission-AI/openspec) — both MIT. speclaw reimplements the ideas as its own code and gives full credit; see [ATTRIBUTION.md](ATTRIBUTION.md).
 
 <br/>
 
@@ -85,20 +89,20 @@ Compass is inspired by [CodeGraph](https://github.com/colbymchenry/codegraph) an
 speclaw meets you where you are. Everything works through the **CLI** — so no one
 is blocked by MCP setup — and the same capabilities are exposed as **MCP tools**
 for a smoother, integrated experience once configured. An agent without MCP can
-still use Compass and the spec engine by calling the CLI from its shell.
+still use Compass and the lawbook engine by calling the CLI from its shell.
 
 <p align="center"><b>CLI</b> — the installer &amp; operator, runs anywhere <code>node</code> does</p>
-<p align="center"><img src="brand/terminal-cli.svg" width="800" alt="speclaw CLI commands"></p>
+<p align="center"><img src="https://raw.githubusercontent.com/esneiderbravo/speclaw/main/brand/terminal-cli.png" width="800" alt="speclaw CLI commands"></p>
 
 <p align="center"><b>MCP</b> — the integrated agent surface, auto-registered by <code>init</code></p>
-<p align="center"><img src="brand/terminal-mcp.svg" width="800" alt="speclaw MCP tools"></p>
+<p align="center"><img src="https://raw.githubusercontent.com/esneiderbravo/speclaw/main/brand/terminal-mcp.png" width="800" alt="speclaw MCP tools"></p>
 
 <br/>
 
 ## ◆ What lands in your project
 
 <p align="center">
-  <img src="brand/terminal-tree.svg" width="800" alt="what speclaw writes into your project">
+  <img src="https://raw.githubusercontent.com/esneiderbravo/speclaw/main/brand/terminal-tree.png" width="800" alt="what speclaw writes into your project">
 </p>
 
 <br/>
@@ -110,7 +114,7 @@ still use Compass and the spec engine by calling the CLI from its shell.
 > of AI coding agents isn't lack of capability — it's working without the project's
 > tacit knowledge: the rules the team actually lives by. speclaw makes that
 > knowledge explicit, executable, and binding, and gives agents a local map
-> (Compass) and a disciplined workflow (Spec) to act on it — without burning tokens.
+> (Compass) and a disciplined workflow (Lawbook) to act on it — without burning tokens.
 
 <br/>
 

package/dist/cli/commands/init.js

@@ -2,12 +2,12 @@ import fs from "node:fs";
 import path from "node:path";
 import * as clack from "@clack/prompts";
 import { scaffold } from "../../modules/foundation/scaffold.js";
-import { specInit } from "../../modules/spec/engine.js";
+import { specInit } from "../../modules/lawbook/engine.js";
 import { buildIndex } from "../../modules/compass/indexer.js";
 import { AGENTS, agentById } from "../../shared/agents.js";
 import { loadPacks } from "../../modules/tools/packs.js";
 import { list } from "../lib/args.js";
-import { ui, c, banner, renderProgress, clearProgress, box } from "../lib/ui.js";
+import { ui, c, banner, renderProgress, clearProgress } from "../lib/ui.js";
 const PACK_LABELS = {
     agents: "dev-agents (backend · frontend · product)",
 };
@@ -82,11 +82,11 @@ export async function runInit(flags) {
     ui.step(`Setting up ${c.bold(c.cyan(projectName))}`);
     scaffold(cwd, profile, packs, agents);
     ui.ok(`Foundation ${c.muted("— LAWS.md + 8 standards + CLAUDE.md/AGENTS.md")}`);
-    ui.ok(`Spec workflow ${c.muted("— draft · build · sync · archive · explore")}`);
+    ui.ok(`Lawbook workflow ${c.muted("— draft · build · sync · archive · explore")}`);
     for (const p of packs)
         ui.ok(`${PACK_LABELS[p] ?? p + " pack"}`);
     specInit(cwd);
-    ui.ok(`Spec workspace ${c.muted("— spec/")}`);
+    ui.ok(`Lawbook workspace ${c.muted("— lawbook/")}`);
     ui.step("Configuring agents");
     for (const id of agents)
         ui.ok(`${agentById(id).label} ${c.muted("— symlinks + MCP")}`);
@@ -100,19 +100,18 @@ export async function runInit(flags) {
             c.bold(c.cream(String(stats.edges))) + c.muted(" edges · ") +
             c.bold(c.cream(String(stats.embeddings))) + c.muted(" embeddings"));
     }
-    // 3. Handoff prompt for the chosen agent
+    // 3. Handoff prompt for the chosen agent — printed as a single flush-left
+    // line so it copy-pastes cleanly (no borders, no wrapping artifacts).
     const primary = agentById(agents[0]);
     ui.step("You're set — one last step");
-    ui.info(`Paste this into ${c.cyan(primary.label)} to build your constitution:`);
     ui.plain();
-    box([
-        "Complete speclaw's foundation: analyze this repo and fill",
-        "LAWS.md and docs/standards/* with the real architecture,",
-        "quality gates and conventions. Use init_project to start.",
-    ], "prompt");
+    ui.info(`Copy this and paste it into ${c.cyan(primary.label)}:`);
     ui.plain();
-    ui.info(`The dev-agents read those standards for your stack — filling them well`);
-    ui.info(`makes them stack-aware.`);
+    console.log(c.cream("Complete speclaw's foundation: analyze this repo and fill LAWS.md and " +
+        "docs/standards/* with its real architecture, quality gates and conventions. " +
+        "Start with init_project."));
+    ui.plain();
+    ui.info(`The dev-agents read those standards for your stack — filling them well makes them stack-aware.`);
     ui.plain();
     ui.info(`Add an agent:   ${ui.code("speclaw agent add cursor")}`);
     ui.info(`Refresh index:  ${ui.code("speclaw index")}`);

package/dist/cli/commands/{spec.js → lawbook.js}

@@ -1,4 +1,4 @@
-import { specInit, specValidate, specSync, specArchive, specList } from "../../modules/spec/engine.js";
+import { specInit, specValidate, specSync, specArchive, specList } from "../../modules/lawbook/engine.js";
 import { ui } from "../lib/ui.js";
 function today() {
     // The MCP path passes the date in; the CLL runs on a real machine, so read it here.
@@ -17,14 +17,14 @@ export async function runSpec(flags) {
         switch (sub) {
             case "init": {
                 const r = specInit(cwd);
-                ui.ok(r.alreadyExisted ? "spec/ already present" : `spec/ created (${r.created.length} entries)`);
+                ui.ok(r.alreadyExisted ? "lawbook/ already present" : `lawbook/ created (${r.created.length} entries)`);
                 return;
             }
             case "list": {
                 const r = specList(cwd);
                 if (!r.initialized)
-                    return ui.warn("No spec/ — run `speclaw spec init`.");
-                ui.heading("Spec workspace");
+                    return ui.warn("No lawbook/ — run `speclaw lawbook init`.");
+                ui.heading("Lawbook workspace");
                 ui.info(`active changes: ${r.activeChanges.join(", ") || "none"}`);
                 ui.info(`archived: ${r.archivedChanges.join(", ") || "none"}`);
                 ui.info(`capabilities: ${r.capabilities.join(", ") || "none"}`);
@@ -52,7 +52,7 @@ export async function runSpec(flags) {
                 return;
             }
             default:
-                ui.err("Usage: speclaw spec <init|list|validate|sync|archive> [change]");
+                ui.err("Usage: speclaw lawbook <init|list|validate|sync|archive> [change]");
                 process.exit(1);
         }
     }

package/dist/cli/commands/visualize.js

@@ -0,0 +1,43 @@
+import { spawn } from "node:child_process";
+import { visualize } from "../../modules/compass/visualize.js";
+import { ui, c } from "../lib/ui.js";
+/** Open a file in the OS default application (browser for .html). */
+function openInBrowser(file) {
+    const cmd = process.platform === "darwin" ? "open" : process.platform === "win32" ? "start" : "xdg-open";
+    try {
+        spawn(cmd, [file], { stdio: "ignore", detached: true, shell: process.platform === "win32" }).unref();
+    }
+    catch {
+        /* best-effort */
+    }
+}
+/**
+ * Build an interactive HTML visualization of the Compass graph into
+ * .speclaw/graph.html and open it.
+ *
+ * @param flags - `_[0]` optionally focuses on a node; `--depth`, `--limit`, `--no-open`.
+ */
+export async function runVisualize(flags) {
+    const cwd = process.cwd();
+    const focus = flags._[0];
+    try {
+        const r = visualize(cwd, {
+            focus,
+            depth: flags.depth ? Number(flags.depth) : undefined,
+            limit: flags.limit ? Number(flags.limit) : undefined,
+        });
+        ui.step("Compass graph");
+        ui.ok(c.bold(c.cream(String(r.shown))) + c.muted(" nodes · ") +
+            c.bold(c.cream(String(r.links))) + c.muted(" edges") +
+            (focus ? c.muted(` · focused on ${focus}`) : c.muted(` · top of ${r.total}`)));
+        ui.info(`→ ${ui.code(".speclaw/graph.html")}`);
+        if (!flags["no-open"]) {
+            openInBrowser(r.path);
+            ui.info("Opening in your browser…");
+        }
+    }
+    catch (err) {
+        ui.err(err.message);
+        process.exit(1);
+    }
+}

package/dist/cli/index.js

@@ -18,13 +18,14 @@ Compass (code intelligence — the same surface agents use via MCP)
   recall "<query>"         Find code by meaning (semantic)
   impact <node>            Blast radius: everything that (transitively) calls it
   trace <from> <to>        A call path between two nodes
+  visualize [node]         Interactive HTML graph → .speclaw/graph.html
 
-Spec workflow
-  spec init                Create the spec/ workspace
-  spec list                Active/archived changes and capabilities
-  spec validate <change>   Validate a change's artifacts
-  spec sync <change>       Promote delta specs to canonical
-  spec archive <change>    Finalize and archive a change
+Lawbook (spec-driven workflow)
+  lawbook init             Create the lawbook/ workspace
+  lawbook list             Active/archived changes and capabilities
+  lawbook validate <c>     Validate a change's artifacts
+  lawbook sync <c>         Promote delta specs to canonical
+  lawbook archive <c>      Finalize and archive a change
 
 Other
   doctor                   Verify the installation
@@ -61,8 +62,10 @@ async function main() {
         case "impact":
         case "trace":
             return (await import("./commands/query.js")).runQuery(cmd, flags);
-        case "spec":
-            return (await import("./commands/spec.js")).runSpec(flags);
+        case "visualize":
+            return (await import("./commands/visualize.js")).runVisualize(flags);
+        case "lawbook":
+            return (await import("./commands/lawbook.js")).runSpec(flags);
         case "doctor":
             return (await import("./commands/doctor.js")).runDoctor(flags);
         default:

package/dist/modules/compass/register.js

@@ -3,6 +3,7 @@ import { text } from "../../shared/mcp.js";
 import { buildIndex } from "./indexer.js";
 import { explore, search, recall, impact, trace } from "./query.js";
 import { startWatch, stopWatch, watchStatus } from "./watcher.js";
+import { visualize } from "./visualize.js";
 // ─── Compass: speclaw's own code-intelligence engine (no external deps) ───
 // A local graph of the codebase (nodes = definitions, edges = calls/imports)
 // plus a local vector store for semantic recall. Lives in .speclaw/ (gitignored).
@@ -57,6 +58,15 @@ export function registerCompass(server) {
             maxDepth: z.number().optional().describe("Max hops to search (default 8)"),
         },
     }, async ({ projectPath, from, to, maxDepth }) => text(trace(projectPath, from, to, maxDepth ?? 8)));
+    server.registerTool("compass_visualize", {
+        description: "Generate an interactive, offline HTML visualization of the code graph into .speclaw/graph.html (gitignored). Nodes are definitions, edges are calls; drag/zoom/hover to explore. Pass a node to focus on its neighborhood, else the most-connected nodes are shown. Requires compass_index.",
+        inputSchema: {
+            projectPath: z.string().describe("Absolute path to the project"),
+            node: z.string().optional().describe("Focus on this node's neighborhood (optional)"),
+            depth: z.number().optional().describe("BFS depth around the focus node (default 2)"),
+            limit: z.number().optional().describe("Max nodes for the whole-graph view (default 300)"),
+        },
+    }, async ({ projectPath, node, depth, limit }) => text(visualize(projectPath, { focus: node, depth, limit })));
     server.registerTool("compass_watch", {
         description: "Keep the Compass index fresh automatically: start/stop a file watcher that incrementally re-indexes on change (debounced). action=start|stop|status. Optional — the index is also refreshed on demand by compass_index.",
         inputSchema: {

package/dist/modules/compass/visualize.js

@@ -0,0 +1,203 @@
+import fs from "node:fs";
+import path from "node:path";
+import { openDb, indexExists } from "./db.js";
+/**
+ * Build the graph payload from the Compass index: nodes (definitions) and the
+ * resolved call links between them. With a focus node, returns its neighborhood
+ * (BFS both directions); otherwise the most-connected nodes up to `limit`.
+ *
+ * @throws If no index exists yet (run `compass_index` first).
+ */
+export function graphData(projectPath, opts = {}) {
+    if (!indexExists(projectPath)) {
+        throw new Error("No index found. Run the compass_index tool (or `speclaw index`) first.");
+    }
+    const { focus, depth = 2, limit = 300 } = opts;
+    const db = openDb(projectPath);
+    try {
+        const allNodes = db
+            .prepare(`SELECT n.id, n.name, n.kind, f.path AS file, n.start_line AS line
+         FROM nodes n JOIN files f ON f.id = n.file_id`)
+            .all();
+        const allEdges = db
+            .prepare(`SELECT src_node_id AS s, dst_node_id AS t FROM edges
+         WHERE kind = 'call' AND dst_node_id IS NOT NULL AND src_node_id IS NOT NULL`)
+            .all();
+        // adjacency (undirected) + degree
+        const adj = new Map();
+        const deg = new Map();
+        for (const e of allEdges) {
+            if (e.s === e.t)
+                continue;
+            (adj.get(e.s) ?? adj.set(e.s, new Set()).get(e.s)).add(e.t);
+            (adj.get(e.t) ?? adj.set(e.t, new Set()).get(e.t)).add(e.s);
+            deg.set(e.s, (deg.get(e.s) ?? 0) + 1);
+            deg.set(e.t, (deg.get(e.t) ?? 0) + 1);
+        }
+        let included;
+        if (focus) {
+            const starts = allNodes.filter((n) => n.name === focus).map((n) => n.id);
+            included = new Set(starts);
+            let frontier = starts;
+            for (let d = 0; d < depth && frontier.length; d++) {
+                const next = [];
+                for (const id of frontier) {
+                    for (const nb of adj.get(id) ?? []) {
+                        if (!included.has(nb)) {
+                            included.add(nb);
+                            next.push(nb);
+                        }
+                    }
+                }
+                frontier = next;
+            }
+        }
+        else {
+            included = new Set([...allNodes]
+                .sort((a, b) => (deg.get(b.id) ?? 0) - (deg.get(a.id) ?? 0))
+                .slice(0, limit)
+                .map((n) => n.id));
+        }
+        const nodes = allNodes
+            .filter((n) => included.has(n.id))
+            .map((n) => ({ ...n, deg: deg.get(n.id) ?? 0 }));
+        const links = allEdges.filter((e) => included.has(e.s) && included.has(e.t));
+        return { nodes, links, total: allNodes.length, focus: focus ?? null };
+    }
+    finally {
+        db.close();
+    }
+}
+/** Write the interactive graph to <projectPath>/.speclaw/graph.html and return its path. */
+export function visualize(projectPath, opts = {}) {
+    const data = graphData(projectPath, opts);
+    const dir = path.join(projectPath, ".speclaw");
+    fs.mkdirSync(dir, { recursive: true });
+    const out = path.join(dir, "graph.html");
+    fs.writeFileSync(out, renderHtml(data));
+    return { path: out, shown: data.nodes.length, links: data.links.length, total: data.total };
+}
+/** Render a self-contained, offline HTML page with an inline force-directed renderer. */
+export function renderHtml(data) {
+    const payload = JSON.stringify(data);
+    return `<!doctype html>
+<html lang="en"><head>
+<meta charset="utf-8"><meta name="viewport" content="width=device-width, initial-scale=1">
+<title>speclaw · Compass graph</title>
+<style>
+  :root { --cy:#17C1C1; --cr:#F4F1EA; --mu:#6E7B80; --bg:#0B0F10; }
+  * { box-sizing:border-box; }
+  html,body { margin:0; height:100%; background:var(--bg); color:var(--cr);
+    font-family:'SF Mono','JetBrains Mono',Menlo,Consolas,monospace; overflow:hidden; }
+  canvas { display:block; cursor:grab; }
+  canvas:active { cursor:grabbing; }
+  .panel { position:fixed; top:16px; left:16px; padding:12px 14px; border-radius:10px;
+    background:rgba(12,17,19,.82); border:1px solid #232A2D; font-size:12px; line-height:1.5; }
+  .panel b { color:var(--cr); } .panel .sub { color:var(--mu); }
+  .legend { position:fixed; bottom:16px; left:16px; font-size:11px; color:var(--mu);
+    background:rgba(12,17,19,.82); border:1px solid #232A2D; border-radius:10px; padding:10px 12px; }
+  .legend span { display:inline-flex; align-items:center; margin-right:12px; }
+  .legend i { width:9px; height:9px; border-radius:50%; display:inline-block; margin-right:5px; }
+  .tip { position:fixed; padding:6px 9px; border-radius:7px; background:#0E1517; border:1px solid #17C1C1;
+    color:var(--cr); font-size:12px; pointer-events:none; opacity:0; transition:opacity .1s; white-space:nowrap; }
+  .brand { color:var(--cy); font-weight:700; }
+</style></head><body>
+<canvas id="c"></canvas>
+<div class="panel">
+  <div><span class="brand">speclaw</span> · Compass graph</div>
+  <div class="sub" id="meta"></div>
+  <div class="sub">drag to pan · wheel to zoom · drag a node · hover to inspect</div>
+</div>
+<div class="legend" id="legend"></div>
+<div class="tip" id="tip"></div>
+<script>
+const DATA = ${payload};
+const KIND_COLORS = { function:'#17C1C1', method:'#3FB950', class:'#E3B341',
+  interface:'#8B989E', type:'#8B989E', enum:'#8B989E' };
+const colorOf = k => KIND_COLORS[k] || '#6E7B80';
+
+const cv = document.getElementById('c'), ctx = cv.getContext('2d');
+const tip = document.getElementById('tip');
+document.getElementById('meta').textContent =
+  DATA.nodes.length + ' nodes · ' + DATA.links.length + ' edges' +
+  (DATA.focus ? ' · focus: ' + DATA.focus : ' · top ' + DATA.nodes.length + ' of ' + DATA.total);
+{
+  const kinds = [...new Set(DATA.nodes.map(n=>n.kind))];
+  document.getElementById('legend').innerHTML = kinds.map(k =>
+    '<span><i style="background:'+colorOf(k)+'"></i>'+k+'</span>').join('');
+}
+
+const idx = new Map(DATA.nodes.map((n,i)=>[n.id,i]));
+const N = DATA.nodes.map(n => ({...n, x:(Math.random()-.5)*800, y:(Math.random()-.5)*600, vx:0, vy:0,
+  r: 4 + Math.min(10, Math.sqrt(n.deg||0)*2) }));
+const L = DATA.links.map(l => ({s:idx.get(l.s), t:idx.get(l.t)})).filter(l=>l.s!=null&&l.t!=null);
+const neigh = N.map(()=>new Set());
+L.forEach(l => { neigh[l.s].add(l.t); neigh[l.t].add(l.s); });
+
+let scale=1, ox=0, oy=0, W=0, H=0, DPR=Math.min(2,devicePixelRatio||1);
+function resize(){ W=innerWidth; H=innerHeight; cv.width=W*DPR; cv.height=H*DPR; cv.style.width=W+'px'; cv.style.height=H+'px'; ctx.setTransform(DPR,0,0,DPR,0,0); }
+addEventListener('resize', resize); resize(); ox=W/2; oy=H/2;
+
+// force simulation
+function tick(){
+  for(let i=0;i<N.length;i++){ const a=N[i];
+    for(let j=i+1;j<N.length;j++){ const b=N[j];
+      let dx=a.x-b.x, dy=a.y-b.y, d2=dx*dx+dy*dy||0.01, d=Math.sqrt(d2);
+      const f=Math.min(2200/d2, 40); const ux=dx/d, uy=dy/d;
+      a.vx+=ux*f; a.vy+=uy*f; b.vx-=ux*f; b.vy-=uy*f;
+    }
+    a.vx += -a.x*0.0016; a.vy += -a.y*0.0016; // gravity to center
+  }
+  for(const l of L){ const a=N[l.s], b=N[l.t];
+    let dx=b.x-a.x, dy=b.y-a.y, d=Math.sqrt(dx*dx+dy*dy)||0.01;
+    const f=(d-90)*0.02, ux=dx/d, uy=dy/d;
+    a.vx+=ux*f; a.vy+=uy*f; b.vx-=ux*f; b.vy-=uy*f;
+  }
+  for(const n of N){ if(n===dragging) continue; n.vx*=0.82; n.vy*=0.82; n.x+=n.vx; n.y+=n.vy; }
+}
+function toScreen(n){ return { x: n.x*scale+ox, y: n.y*scale+oy }; }
+
+let hover=-1;
+function draw(){
+  ctx.clearRect(0,0,W,H);
+  const hoverSet = hover>=0 ? neigh[hover] : null;
+  ctx.lineWidth = 1;
+  for(const l of L){ const a=toScreen(N[l.s]), b=toScreen(N[l.t]);
+    const on = hover>=0 && (l.s===hover||l.t===hover);
+    ctx.strokeStyle = on ? 'rgba(23,193,193,.7)' : 'rgba(110,123,128,.16)';
+    ctx.beginPath(); ctx.moveTo(a.x,a.y); ctx.lineTo(b.x,b.y); ctx.stroke();
+  }
+  for(let i=0;i<N.length;i++){ const n=N[i], p=toScreen(n);
+    const dim = hover>=0 && i!==hover && !(hoverSet&&hoverSet.has(i));
+    ctx.globalAlpha = dim ? 0.28 : 1;
+    ctx.beginPath(); ctx.arc(p.x,p.y,n.r*Math.sqrt(scale),0,7); ctx.fillStyle=colorOf(n.kind); ctx.fill();
+    if((n.r>7 || i===hover || (hoverSet&&hoverSet.has(i))) && scale>0.5){
+      ctx.globalAlpha = dim?0.4:0.9; ctx.fillStyle='#F4F1EA'; ctx.font='11px monospace';
+      ctx.fillText(n.name, p.x+n.r+3, p.y+3);
+    }
+  }
+  ctx.globalAlpha=1;
+}
+function loop(){ tick(); draw(); requestAnimationFrame(loop); } loop();
+
+// interaction
+let dragging=null, panning=false, lastX=0, lastY=0;
+function pick(mx,my){ let best=-1, bd=1e9;
+  for(let i=0;i<N.length;i++){ const p=toScreen(N[i]); const d=Math.hypot(p.x-mx,p.y-my);
+    if(d < N[i].r*Math.sqrt(scale)+6 && d<bd){ bd=d; best=i; } } return best; }
+cv.addEventListener('mousedown', e=>{ const i=pick(e.clientX,e.clientY);
+  if(i>=0) dragging=N[i]; else { panning=true; } lastX=e.clientX; lastY=e.clientY; });
+addEventListener('mousemove', e=>{
+  if(dragging){ dragging.x += (e.clientX-lastX)/scale; dragging.y += (e.clientY-lastY)/scale; dragging.vx=dragging.vy=0; }
+  else if(panning){ ox+=e.clientX-lastX; oy+=e.clientY-lastY; }
+  lastX=e.clientX; lastY=e.clientY;
+  const i=pick(e.clientX,e.clientY); hover=i;
+  if(i>=0){ const n=N[i]; tip.style.opacity=1; tip.style.left=(e.clientX+12)+'px'; tip.style.top=(e.clientY+12)+'px';
+    tip.innerHTML='<b>'+n.name+'</b> <span style="color:#6E7B80">'+n.kind+' · '+n.file+':'+n.line+'</span>'; }
+  else tip.style.opacity=0;
+});
+addEventListener('mouseup', ()=>{ dragging=null; panning=false; });
+cv.addEventListener('wheel', e=>{ e.preventDefault(); const f=e.deltaY<0?1.1:0.9;
+  const mx=e.clientX, my=e.clientY; ox=mx-(mx-ox)*f; oy=my-(my-oy)*f; scale*=f; }, {passive:false});
+</script></body></html>`;
+}

package/dist/modules/foundation/assets/AGENTS.template.md

@@ -19,9 +19,9 @@ Claude-specific notes: [`CLAUDE.md`](CLAUDE.md). The law: [`LAWS.md`](LAWS.md).
 2. **Use Compass before file scanning** — the `compass_explore` /
    `compass_search` / `compass_recall` tools (run `compass_index` first if the
    graph is missing). Cheat sheet: [`docs/compass.md`](docs/compass.md).
-3. **Follow the spec workflow** for every non-trivial change; archive
+3. **Follow the lawbook workflow** for every non-trivial change; archive
    within the same PR. Rules:
-   [`docs/standards/spec-workflow.md`](docs/standards/spec-workflow.md).
+   [`docs/standards/lawbook.md`](docs/standards/lawbook.md).
 4. **Run the quality gates yourself** before declaring anything done — see
    [`docs/standards/testing-standards.md`](docs/standards/testing-standards.md):
    - Tests: `{{test_commands}}`
@@ -45,7 +45,7 @@ Claude-specific notes: [`CLAUDE.md`](CLAUDE.md). The law: [`LAWS.md`](LAWS.md).
 | [`docs/standards/testing-standards.md`](docs/standards/testing-standards.md) | Quality gates, testing rules |
 | [`docs/standards/documentation.md`](docs/standards/documentation.md) | Docstring/API-comment convention per language |
 | [`docs/standards/conventions.md`](docs/standards/conventions.md) | Branches, PRs, tracker, versioning |
-| [`docs/standards/spec-workflow.md`](docs/standards/spec-workflow.md) | Spec-driven workflow, archiving |
+| [`docs/standards/lawbook.md`](docs/standards/lawbook.md) | Spec-driven workflow, archiving |
 | [`docs/compass.md`](docs/compass.md) | Compass usage |
 
 ## Directory map for agents
@@ -57,5 +57,5 @@ Claude-specific notes: [`CLAUDE.md`](CLAUDE.md). The law: [`LAWS.md`](LAWS.md).
 | `AGENTS.md` / `CLAUDE.md` | Agent entry points (this contract) |
 | `ai-specs/` | Canonical skills, commands, rules, agents |
 | `.claude/` `.cursor/` `.codex/` `.agents/` | IDE mirrors (symlinks into `ai-specs/`) |
-| `spec/` | Spec-driven workflow: specs, changes, archive |
+| `lawbook/` | Spec-driven workflow: specs, changes, archive |
 | `.mcp.json` | MCP wiring (speclaw) |

package/dist/modules/foundation/assets/CLAUDE.template.md

@@ -21,7 +21,7 @@ governs the area you're touching **before** touching it:
 | Tests / gates | [`docs/standards/testing-standards.md`](docs/standards/testing-standards.md) |
 | Docstrings / API comments | [`docs/standards/documentation.md`](docs/standards/documentation.md) |
 | Branches / PRs / tickets | [`docs/standards/conventions.md`](docs/standards/conventions.md) |
-| Any non-trivial change | [`docs/standards/spec-workflow.md`](docs/standards/spec-workflow.md) |
+| Any non-trivial change | [`docs/standards/lawbook.md`](docs/standards/lawbook.md) |
 
 When any instruction conflicts with a standard, **the standard wins** — and if
 you believe it is wrong, propose an amendment via a spec change; never silently
@@ -39,8 +39,8 @@ only when the graph doesn't cover what you need.
 
 No non-trivial change lands without a spec change (propose → implement →
 verify → archive). The rules are in
-[`docs/standards/spec-workflow.md`](docs/standards/spec-workflow.md);
-the workflow skills live in `ai-specs/skills/` and the `/spec` commands wrap
+[`docs/standards/lawbook.md`](docs/standards/lawbook.md);
+the workflow skills live in `ai-specs/skills/` and the `/lawbook` commands wrap
 them. A change is not done until it is archived — archiving belongs in the PR.
 
 ## Rule 3 — Quality gates are non-negotiable

package/dist/modules/foundation/assets/LAWS.template.md

@@ -21,7 +21,7 @@
 | Testing | [`docs/standards/testing-standards.md`](docs/standards/testing-standards.md) | Quality gates, what must be tested, verification |
 | Documentation | [`docs/standards/documentation.md`](docs/standards/documentation.md) | Docstring/API-comment convention per language |
 | Conventions | [`docs/standards/conventions.md`](docs/standards/conventions.md) | Branches, PRs, tracker, versioning |
-| Spec | [`docs/standards/spec-workflow.md`](docs/standards/spec-workflow.md) | Spec-driven workflow, mandatory task steps, archiving |
+| Lawbook | [`docs/standards/lawbook.md`](docs/standards/lawbook.md) | Spec-driven workflow, mandatory task steps, archiving |
 | Compass | [`docs/compass.md`](docs/compass.md) | Using the code knowledge graph before grep |
 
 ## Binding rules
@@ -30,8 +30,8 @@
    the map. Agents open the standard that governs the code they're changing.
 2. **The standards are enforced, not advisory.** A violation is a blocking
    finding in review.
-3. **Amendments go through the spec workflow.** A standard is changed like code — via a
-   reviewed change (see the spec-workflow law). An agent may propose an amendment;
+3. **Amendments go through the lawbook workflow.** A standard is changed like code — via a
+   reviewed change (see the lawbook law). An agent may propose an amendment;
    it may never silently ignore a standard.
 4. **Entry points reference the law.** [`CLAUDE.md`](CLAUDE.md) and
    [`AGENTS.md`](AGENTS.md) point every agent here first.

package/dist/modules/foundation/assets/docs/standards/{spec-workflow.template.md → lawbook.template.md}

@@ -1,4 +1,4 @@
-# Spec Workflow — {{project_name}}
+# Lawbook — {{project_name}}
 
 The process law of the project — see [`../../LAWS.md`](../../LAWS.md). This
 repo is spec-driven through speclaw's **spec** module (no external CLI; the
@@ -9,18 +9,18 @@ mechanical steps are speclaw MCP tools).
 No non-trivial change lands without a spec change:
 
 1. **explore** — think an idea through before committing (writes nothing).
-2. **draft** — create `spec/changes/<name>/`: `proposal.md`, delta specs under
+2. **draft** — create `lawbook/changes/<name>/`: `proposal.md`, delta specs under
    `specs/<capability>/spec.md`, optional `design.md`, and `tasks.md`.
 3. **build** — implement the tasks in order, keeping code and spec in
    agreement.
 4. **sync** — promote the change's delta specs into the canonical
-   `spec/specs/` (`spec_sync`).
-5. **archive** — finalize: sync + move the change to `spec/changes/archive/`
-   (`spec_archive`), **within the same PR** — never a post-merge chore.
+   `lawbook/specs/` (`lawbook_sync`).
+5. **archive** — finalize: sync + move the change to `lawbook/changes/archive/`
+   (`lawbook_archive`), **within the same PR** — never a post-merge chore.
 
 ## Mandatory task steps
 
-`tasks.md` MUST include the steps defined in `spec/config.yaml` and the
+`tasks.md` MUST include the steps defined in `lawbook/config.yaml` and the
 `spec-tasks-mandatory-steps` rule: feature branch first, tests reviewed and
 run, manual verification executed by the agent, docs updated, archive within
 the PR. The agent performs the manual testing itself — never delegates it.
@@ -32,11 +32,11 @@ the PR. The agent performs the manual testing itself — never delegates it.
 - Scenario headers use exactly `#### Scenario:`.
 - Acceptance criteria are testable without production integrations.
 - The implemented code must match what the delta spec promises. Validate with
-  the `spec_validate` tool before syncing or archiving.
+  the `lawbook_validate` tool before syncing or archiving.
 
 ## Archiving discipline
 
-Always archive with the `archive` command / `spec_archive` tool, never a manual
+Always archive with the `archive` command / `lawbook_archive` tool, never a manual
 `mv` — the tool performs the spec promotion and validation a manual move skips.
 
 ## Amendments to the law

package/dist/modules/foundation/assets/docs/standards/testing-standards.template.md

@@ -30,5 +30,5 @@ suppressing a linter or deleting a test.
 - When a change affects runtime behavior and it's feasible, verify it works by
   exercising the endpoint/UI — don't assume green CI covers everything.
 - The mandatory spec task steps
-  ([`spec-workflow.md`](spec-workflow.md)) define which manual checks
+  ([`lawbook.md`](lawbook.md)) define which manual checks
   the agent must execute itself.

package/dist/modules/foundation/doctor.js

@@ -4,7 +4,7 @@ import { AGENTS, detectConfiguredAgents } from "../../shared/agents.js";
 /**
  * Run the speclaw installation health checks against a project: ai-specs and
  * LAWS.md presence, agent contracts, the docs/standards set, per-agent IDE
- * symlink health, the spec/ workflow, the Compass index, and .mcp.json wiring.
+ * symlink health, the lawbook/ workflow, the Compass index, and .mcp.json wiring.
  *
  * @param projectPath - Absolute path to the project root.
  * @returns One {@link Check} per verified item, each carrying a remediation hint.
@@ -39,7 +39,7 @@ export function doctor(projectPath) {
         "testing-standards",
         "documentation",
         "conventions",
-        "spec-workflow",
+        "lawbook",
     ];
     const missingStandards = standards.filter((s) => !has(path.join("docs/standards", `${s}.md`)));
     checks.push({
@@ -85,11 +85,11 @@ export function doctor(projectPath) {
         }
     }
     checks.push({
-        name: "spec workflow",
-        ok: has("spec"),
-        detail: has("spec")
-            ? "spec/ present"
-            : "missing — run the `spec_init` tool",
+        name: "lawbook workflow",
+        ok: has("lawbook"),
+        detail: has("lawbook")
+            ? "lawbook/ present"
+            : "missing — run the `lawbook_init` tool",
     });
     checks.push({
         name: "Compass index",

package/dist/modules/foundation/register.js

@@ -43,7 +43,7 @@ export function registerFoundation(server) {
                 "4. If the 'workflow' pack is selected, ask the user for their tracker's ticket prefix and team working language.",
                 "5. Draft any custom_laws (extra binding rules for LAWS.md) from conventions you observed that the standard set doesn't cover.",
                 "6. Call the 'scaffold' tool with { projectPath, profile, packs }.",
-                "7. Follow the nextSteps returned by scaffold: complete the HTML-comment sections still left in docs/standards/*, then run the spec_init and compass_index tools (both built into speclaw — no external installs).",
+                "7. Follow the nextSteps returned by scaffold: complete the HTML-comment sections still left in docs/standards/*, then run the lawbook_init and compass_index tools (both built into speclaw — no external installs).",
             ],
             profileFields: Object.fromEntries(Object.entries(profileShape).map(([key, schema]) => [key, schema.description ?? ""])),
             packs,
@@ -70,7 +70,7 @@ export function registerFoundation(server) {
         return text(report);
     });
     server.registerTool("doctor", {
-        description: "Verify a speclaw installation: ai-specs presence, the foundation (LAWS.md + standards + agent contracts), IDE symlinks health, the spec/ workflow, the Compass index, and .mcp.json wiring. Returns a checklist with remediation hints.",
+        description: "Verify a speclaw installation: ai-specs presence, the foundation (LAWS.md + standards + agent contracts), IDE symlinks health, the lawbook/ workflow, the Compass index, and .mcp.json wiring. Returns a checklist with remediation hints.",
         inputSchema: { projectPath: z.string().describe("Absolute path to the project") },
     }, async ({ projectPath }) => {
         const checks = doctor(projectPath);

package/dist/modules/foundation/scaffold.js

@@ -4,7 +4,7 @@ import { assetsDir } from "../../shared/paths.js";
 import { render } from "../../shared/render.js";
 import { emptyReport, ensureGitignore } from "../../shared/install.js";
 import { configureAgent } from "../../shared/agents.js";
-import { installWorkflow } from "../spec/register.js";
+import { installWorkflow } from "../lawbook/register.js";
 import { installPack, loadPacks } from "../tools/packs.js";
 const ASSETS = assetsDir(import.meta.url);
 // Every {{var}} the foundation templates may reference. Ones the agent didn't
@@ -90,7 +90,7 @@ export function scaffold(projectPath, profile, packNames, agents = []) {
     for (const id of agents)
         configureAgent(projectPath, id, report); // only the chosen agents
     report.nextSteps = [
-        "Run the `spec_init` tool to set up the spec-driven workflow (creates spec/). No external CLI needed — it's built into speclaw.",
+        "Run the `lawbook_init` tool to set up the spec-driven workflow (creates lawbook/). No external CLI needed — it's built into speclaw.",
         "Run the `compass_index` tool to build the local code graph (.speclaw/). No install, no LLM — it's built into speclaw. Re-run it after significant edits.",
         "Analyze the repo's real entrypoints and core flows, then fill in the 'Project-specific starting points' section of docs/compass.md (or pass compass_hints in the profile) so agents know where to start querying.",
         "Fill in the per-standard sections left as HTML comments in docs/standards/* (architecture module table, backend/frontend layer tables, versioning) by analyzing the real repo. These are the granular laws CLAUDE.md, AGENTS.md and the dev agents reference.",

package/dist/modules/{spec → lawbook}/assets/commands/archive.md

@@ -5,6 +5,6 @@ description: Finalize a completed change — sync specs into canonical, then arc
 Archive the completed change: $ARGUMENTS
 
 Follow the `archive` skill: confirm every task is done and gates are green,
-run `spec_validate`, then `spec_archive` with today's date (YYYY-MM-DD). It
-syncs the specs and moves the change to `spec/changes/archive/`. Never move
+run `lawbook_validate`, then `lawbook_archive` with today's date (YYYY-MM-DD). It
+syncs the specs and moves the change to `lawbook/changes/archive/`. Never move
 the folder by hand.

package/dist/modules/{spec → lawbook}/assets/commands/draft.md

@@ -2,11 +2,11 @@
 description: Draft a new spec-driven change (proposal, delta specs, tasks) before coding.
 ---
 
-Draft a new change under `spec/changes/<name>/` for: $ARGUMENTS
+Draft a new change under `lawbook/changes/<name>/` for: $ARGUMENTS
 
-Follow the `draft` skill: ensure `spec/` exists (`spec_init`), investigate the
+Follow the `draft` skill: ensure `lawbook/` exists (`lawbook_init`), investigate the
 code with `compass_explore`/`compass_recall`, read the governing
 `docs/standards/`, then write `proposal.md`, `specs/<capability>/spec.md`
 (normative `SHALL`/`MUST` + `#### Scenario:`), optional `design.md`, and
-`tasks.md` (with the mandatory steps from `spec/config.yaml`). Finish by
-running `spec_validate` and fixing every issue.
+`tasks.md` (with the mandatory steps from `lawbook/config.yaml`). Finish by
+running `lawbook_validate` and fixing every issue.

package/dist/modules/{spec → lawbook}/assets/commands/explore.md

@@ -7,4 +7,4 @@ Explore: $ARGUMENTS
 Follow the `explore` skill: use `compass_recall`/`compass_explore` to understand
 the code, ask sharp questions, check the relevant `docs/standards/`, weigh
 approaches with trade-offs, and give a recommendation. Write nothing to
-`spec/`; when the direction is clear, offer to `draft` the change.
+`lawbook/`; when the direction is clear, offer to `draft` the change.

package/dist/modules/{spec → lawbook}/assets/commands/sync.md

@@ -4,6 +4,6 @@ description: Promote a change's delta specs into the canonical specs, without ar
 
 Sync the change's specs into canonical: $ARGUMENTS
 
-Follow the `sync` skill: validate the change (`spec_validate`), then run
-`spec_sync` to promote each delta spec into `spec/specs/`. Report what was
+Follow the `sync` skill: validate the change (`lawbook_validate`), then run
+`lawbook_sync` to promote each delta spec into `lawbook/specs/`. Report what was
 promoted; leave the change active.

package/dist/modules/{spec → lawbook}/assets/rules/spec-tasks-mandatory-steps.md

@@ -1,15 +1,15 @@
 ---
-description: Enforce the mandatory steps from spec/config.yaml when creating tasks.md, and ensure the agent executes all manual verification itself.
+description: Enforce the mandatory steps from lawbook/config.yaml when creating tasks.md, and ensure the agent executes all manual verification itself.
 alwaysApply: true
 ---
 
 # Spec Tasks: Mandatory Steps
 
-When creating or updating a `tasks.md` inside a `spec/changes/<name>/`, you MUST:
+When creating or updating a `tasks.md` inside a `lawbook/changes/<name>/`, you MUST:
 
-## 1. Read spec/config.yaml first
+## 1. Read lawbook/config.yaml first
 
-Before writing tasks, read `spec/config.yaml` for the project's mandatory task
+Before writing tasks, read `lawbook/config.yaml` for the project's mandatory task
 steps, branch convention, and testing/documentation requirements.
 
 ## 2. Include the mandatory steps, in order
@@ -22,7 +22,7 @@ steps, branch convention, and testing/documentation requirements.
 - Perform manual verification of the behavior — **the agent executes this
   itself, never the user.**
 - Update the technical documentation the change touches.
-- Archive the change within the same PR (the `archive` command / `spec_archive`
+- Archive the change within the same PR (the `archive` command / `lawbook_archive`
   tool).
 
 ## 3. Manual verification — the agent must execute it
@@ -33,5 +33,5 @@ not complete until the agent has verified it.
 
 ## 4. Archiving is part of the change
 
-A change is not done until it is archived with `spec_archive` (never a manual
+A change is not done until it is archived with `lawbook_archive` (never a manual
 `mv`). The archive lands in the same PR that implements the change.

package/dist/modules/{spec → lawbook}/assets/skills/archive/SKILL.md

@@ -1,22 +1,22 @@
 ---
 name: archive
-description: Finalize a completed change — sync its specs into canonical, then move it to the archive. Use when a change is done and merged-ready: "archive the change", "finalize X", "close out the change". Part of speclaw's spec module (draft → build → sync → archive). Archiving belongs in the same PR that implements the change.
+description: Finalize a completed change — sync its specs into canonical, then move it to the archive. Use when a change is done and merged-ready: "archive the change", "finalize X", "close out the change". Part of speclaw's lawbook module (draft → build → sync → archive). Archiving belongs in the same PR that implements the change.
 ---
 
 # archive — Finalize and archive a change
 
 Close out a completed change: its delta specs become canonical and the change
-folder moves to `spec/changes/archive/`. This is part of the PR that
+folder moves to `lawbook/changes/archive/`. This is part of the PR that
 implements the change, not a post-merge chore.
 
 ## Steps
 
 1. Confirm the change is truly done: every task in `tasks.md` checked, quality
    gates green, behavior verified.
-2. Run `spec_validate` for the change; resolve any issues first.
-3. Run the `spec_archive` tool with the change name and today's date
-   (`YYYY-MM-DD`). It syncs the delta specs into `spec/specs/` and then moves
-   `spec/changes/<name>/` to `spec/changes/archive/<date>-<name>/`.
+2. Run `lawbook_validate` for the change; resolve any issues first.
+3. Run the `lawbook_archive` tool with the change name and today's date
+   (`YYYY-MM-DD`). It syncs the delta specs into `lawbook/specs/` and then moves
+   `lawbook/changes/<name>/` to `lawbook/changes/archive/<date>-<name>/`.
 4. Report the archive path and the promoted specs. Never move the folder by
-   hand — always use `spec_archive`, which performs the sync and validation a
+   hand — always use `lawbook_archive`, which performs the sync and validation a
    manual move would skip.

package/dist/modules/{spec → lawbook}/assets/skills/build/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: build
-description: Implement the tasks of a drafted change, following its spec and the project's standards. Use when the user wants to start or continue implementing a change: "build X", "implement the change", "work through the tasks", "continue X". Part of speclaw's spec module (draft → build → sync → archive).
+description: Implement the tasks of a drafted change, following its spec and the project's standards. Use when the user wants to start or continue implementing a change: "build X", "implement the change", "work through the tasks", "continue X". Part of speclaw's lawbook module (draft → build → sync → archive).
 ---
 
 # build — Implement a change
@@ -10,8 +10,8 @@ in lockstep.
 
 ## Step 0 — Load the change
 
-- Read `spec/changes/<name>/proposal.md`, `tasks.md`, and the delta specs under
-  `specs/`. If unsure which change, run `spec_list`.
+- Read `lawbook/changes/<name>/proposal.md`, `tasks.md`, and the delta specs under
+  `specs/`. If unsure which change, run `lawbook_list`.
 - Read the governing standards in `docs/standards/` for the areas you'll touch.
 
 ## Step 1 — Branch first

package/dist/modules/{spec → lawbook}/assets/skills/draft/SKILL.md

@@ -1,17 +1,17 @@
 ---
 name: draft
-description: Draft a new spec-driven change — proposal, delta specs, and tasks — before writing any code. Use when the user wants to start, plan, or propose a new feature, fix, or refactor: "draft a change for X", "propose X", "let's plan X", "spec out X", "new change". Part of speclaw's spec module (draft → build → sync → archive).
+description: Draft a new spec-driven change — proposal, delta specs, and tasks — before writing any code. Use when the user wants to start, plan, or propose a new feature, fix, or refactor: "draft a change for X", "propose X", "let's plan X", "spec out X", "new change". Part of speclaw's lawbook module (draft → build → sync → archive).
 ---
 
 # draft — Draft a new change
 
-Turn a request into a complete, reviewable change under `spec/changes/<name>/`
+Turn a request into a complete, reviewable change under `lawbook/changes/<name>/`
 before any implementation. This is speclaw's own spec-driven workflow — no
 external CLI; the mechanical steps are speclaw MCP tools.
 
 ## Step 0 — Ensure the workspace exists
 
-If `spec/` is missing, run the `spec_init` tool once to create it.
+If `lawbook/` is missing, run the `lawbook_init` tool once to create it.
 
 ## Step 1 — Understand the request and the code
 
@@ -25,11 +25,11 @@ If `spec/` is missing, run the `spec_init` tool once to create it.
 ## Step 2 — Pick a change name
 
 Kebab-case, action-oriented (e.g. `add-login`, `fix-shift-overlap`). This is
-the folder under `spec/changes/`.
+the folder under `lawbook/changes/`.
 
 ## Step 3 — Write the artifacts
 
-Create under `spec/changes/<name>/`:
+Create under `lawbook/changes/<name>/`:
 
 - **proposal.md** — the why, the what, non-goals, and whether migrations are
   needed. Reference the tracker ticket ({{ticket_prefix}}-N) if there is one.
@@ -49,13 +49,13 @@ Create under `spec/changes/<name>/`:
 - **design.md** (optional) — for non-trivial changes: approach, alternatives,
   trade-offs.
 - **tasks.md** — ordered, checkable steps. MUST include the mandatory steps
-  from `spec/config.yaml` (feature branch first; tests reviewed and run;
+  from `lawbook/config.yaml` (feature branch first; tests reviewed and run;
   manual verification executed by the agent; docs updated; archive within the
   PR).
 
 ## Step 4 — Validate
 
-Run the `spec_validate` tool for the change and fix every issue it reports
+Run the `lawbook_validate` tool for the change and fix every issue it reports
 (missing artifacts, non-normative specs, missing scenarios) before handing off
 to implementation.
 

package/dist/modules/{spec → lawbook}/assets/skills/explore/SKILL.md

@@ -1,12 +1,12 @@
 ---
 name: explore
-description: Enter explore mode — a thinking partner for investigating an idea, a problem, or the codebase before or during a change. Use when the user wants to think something through, understand how something works, or clarify requirements before committing to a spec: "help me think through X", "how does X work", "explore X", "I'm not sure how to approach X". Part of speclaw's spec module.
+description: Enter explore mode — a thinking partner for investigating an idea, a problem, or the codebase before or during a change. Use when the user wants to think something through, understand how something works, or clarify requirements before committing to a spec: "help me think through X", "how does X work", "explore X", "I'm not sure how to approach X". Part of speclaw's lawbook module.
 ---
 
 # explore — Think it through
 
 A low-commitment mode for investigating ideas and the codebase before (or
-during) a change. Nothing is written to `spec/` here — the output is shared
+during) a change. Nothing is written to `lawbook/` here — the output is shared
 understanding and a recommended direction.
 
 ## How to explore

package/dist/modules/lawbook/assets/skills/sync/SKILL.md

@@ -0,0 +1,21 @@
+---
+name: sync
+description: Promote a change's delta specs into the canonical specs, without archiving. Use when the user wants to update the source-of-truth specs from a change: "sync the specs", "update the canonical specs", "promote the specs". Part of speclaw's lawbook module (draft → build → sync → archive).
+---
+
+# sync — Promote delta specs to canonical
+
+Update the project's canonical specifications (`lawbook/specs/`) with a change's
+delta specs, without archiving the change. Use this when the specs should
+become the source of truth but the change isn't finished (e.g. multi-PR work).
+
+## Steps
+
+1. Confirm which change to sync (run `lawbook_list` if unsure).
+2. Run `lawbook_validate` for the change; do not sync a change whose specs are
+   invalid.
+3. Run the `lawbook_sync` tool for the change. It copies each
+   `lawbook/changes/<name>/specs/<capability>/spec.md` over the canonical
+   `lawbook/specs/<capability>/spec.md` and reports what it promoted.
+4. Report the promoted files to the user. The change stays active — `archive`
+   it when it's fully done.

package/dist/modules/{spec → lawbook}/engine.js

@@ -4,20 +4,20 @@ import path from "node:path";
 // (proposals, delta specs, changes, archive) but implemented from scratch and
 // deliberately simpler: a change's specs/ holds the full intended spec for each
 // affected capability, and sync promotes those into the canonical specs/.
-const SPEC_DIR = "spec";
+const SPEC_DIR = "lawbook";
 function specRoot(projectPath) {
     return path.join(projectPath, SPEC_DIR);
 }
 /**
- * Report whether the spec workspace (spec/) has been initialized for a project.
+ * Report whether the lawbook workspace (lawbook/) has been initialized for a project.
  *
  * @param projectPath - Absolute path to the project root.
- * @returns True if the spec/ directory exists.
+ * @returns True if the lawbook/ directory exists.
  */
 export function specExists(projectPath) {
     return fs.existsSync(specRoot(projectPath));
 }
-const CONFIG_YAML = `# speclaw spec module configuration
+const CONFIG_YAML = `# speclaw lawbook module configuration
 # The spec-driven workflow: draft -> build -> sync -> archive (explore anytime).
 
 # Mandatory steps every change's tasks.md must include, in order.
@@ -27,14 +27,14 @@ mandatory_task_steps:
   - "Run the quality gates and verify they pass (see docs/standards/testing-standards.md)."
   - "Perform manual verification of the behavior — the agent executes this itself, never the user."
   - "Update the technical documentation touched by the change."
-  - "Archive the change within the same PR (spec:archive)."
+  - "Archive the change within the same PR (lawbook:archive)."
 
 # A change is required for new behavior, endpoints, schema changes, or UI flows;
 # one-line fixes need not have one.
 `;
-const README_MD = `# spec/ — the spec-driven workflow (speclaw)
+const README_MD = `# lawbook/ — the spec-driven workflow (speclaw)
 
-This directory is managed by speclaw's **spec** module.
+This directory is managed by speclaw's **lawbook** module.
 
 - \`specs/\` — the canonical specifications (the current source of truth).
 - \`changes/<name>/\` — an in-flight change: \`proposal.md\`, \`tasks.md\`,
@@ -44,11 +44,11 @@ This directory is managed by speclaw's **spec** module.
 
 ## Workflow
 
-1. \`spec:draft\` — describe the change; generates proposal, delta specs, tasks.
-2. \`spec:build\` — implement the tasks.
-3. \`spec:sync\` — promote the change's delta specs into \`specs/\`.
-4. \`spec:archive\` — sync + move the change to \`changes/archive/\`.
-5. \`spec:explore\` — think through an idea before or during a change.
+1. \`lawbook:draft\` — describe the change; generates proposal, delta specs, tasks.
+2. \`lawbook:build\` — implement the tasks.
+3. \`lawbook:sync\` — promote the change's delta specs into \`specs/\`.
+4. \`lawbook:archive\` — sync + move the change to \`changes/archive/\`.
+5. \`lawbook:explore\` — think through an idea before or during a change.
 `;
 /**
  * Initialize the spec/ workspace, creating the specs/, changes/, and archive
@@ -107,7 +107,7 @@ function deltaSpecFiles(changeDir) {
  * header, and a "#### Scenario:" acceptance criterion.
  *
  * @param projectPath - Absolute path to the project root.
- * @param change - Change name (folder under spec/changes/).
+ * @param change - Change name (folder under lawbook/changes/).
  * @returns The validation verdict and the list of issues to fix; never throws
  *   for a missing change — it is reported as an issue with `valid: false`.
  */
@@ -115,7 +115,7 @@ export function specValidate(projectPath, change) {
     const changeDir = path.join(specRoot(projectPath), "changes", change);
     const issues = [];
     if (!fs.existsSync(changeDir)) {
-        return { change, valid: false, issues: [`change "${change}" not found under spec/changes/`], deltaSpecs: [] };
+        return { change, valid: false, issues: [`change "${change}" not found under lawbook/changes/`], deltaSpecs: [] };
     }
     if (!fs.existsSync(path.join(changeDir, "proposal.md")))
         issues.push("missing proposal.md");
@@ -145,7 +145,7 @@ export function specValidate(projectPath, change) {
  * file for each affected capability.
  *
  * @param projectPath - Absolute path to the project root.
- * @param change - Change name (folder under spec/changes/).
+ * @param change - Change name (folder under lawbook/changes/).
  * @returns The change name and the list of promoted spec paths.
  * @throws If the change directory does not exist.
  */
@@ -168,7 +168,7 @@ export function specSync(projectPath, change) {
                 const dest = path.join(root, "specs", rel);
                 fs.mkdirSync(path.dirname(dest), { recursive: true });
                 fs.copyFileSync(full, dest);
-                promoted.push(path.join("spec/specs", rel));
+                promoted.push(path.join("lawbook/specs", rel));
             }
         }
     };
@@ -180,7 +180,7 @@ export function specSync(projectPath, change) {
  * it to changes/archive/<date>-<name>/.
  *
  * @param projectPath - Absolute path to the project root.
- * @param change - Change name (folder under spec/changes/).
+ * @param change - Change name (folder under lawbook/changes/).
  * @param date - Archive date prefix, formatted YYYY-MM-DD.
  * @returns The promoted specs and the archive destination path.
  * @throws If the change does not exist, or the archive target already exists.

package/dist/modules/{spec → lawbook}/register.js

@@ -13,40 +13,40 @@ const ASSETS = assetsDir(import.meta.url);
 export function installWorkflow(projectPath, vars, report) {
     const aiSpecs = path.join(projectPath, "ai-specs");
     copyRendered(path.join(ASSETS, "skills"), path.join(aiSpecs, "skills"), vars, report);
-    copyRendered(path.join(ASSETS, "commands"), path.join(aiSpecs, "commands", "spec"), vars, report);
+    copyRendered(path.join(ASSETS, "commands"), path.join(aiSpecs, "commands", "lawbook"), vars, report);
     copyRendered(path.join(ASSETS, "rules"), path.join(aiSpecs, "rules"), vars, report);
 }
 // ─── The spec module: speclaw's own spec-driven workflow (no external OpenSpec) ───
 // Mechanical operations behind the draft/build/sync/archive/explore commands.
 /** Register the spec workflow MCP tools (init, list, validate, sync, archive). */
 export function registerSpec(server) {
-    server.registerTool("spec_init", {
-        description: "Initialize speclaw's spec-driven workflow in a project: creates spec/ (specs/, changes/, changes/archive/, config.yaml, README). Idempotent — never overwrites existing files.",
+    server.registerTool("lawbook_init", {
+        description: "Initialize speclaw's spec-driven workflow in a project: creates lawbook/ (specs/, changes/, changes/archive/, config.yaml, README). Idempotent — never overwrites existing files.",
         inputSchema: { projectPath: z.string().describe("Absolute path to the project") },
     }, async ({ projectPath }) => text(specInit(projectPath)));
-    server.registerTool("spec_list", {
+    server.registerTool("lawbook_list", {
         description: "List the spec workspace: active changes, archived changes, and canonical capabilities under spec/.",
         inputSchema: { projectPath: z.string().describe("Absolute path to the project") },
     }, async ({ projectPath }) => text(specList(projectPath)));
-    server.registerTool("spec_validate", {
+    server.registerTool("lawbook_validate", {
         description: "Validate a change's artifacts: proposal.md and tasks.md present, and delta specs use normative language (SHALL/MUST), '### Requirement:' headers, and '#### Scenario:' acceptance criteria. Returns the issues to fix. Used by the draft/build commands before proceeding.",
         inputSchema: {
             projectPath: z.string().describe("Absolute path to the project"),
-            change: z.string().describe("Change name (folder under spec/changes/)"),
+            change: z.string().describe("Change name (folder under lawbook/changes/)"),
         },
     }, async ({ projectPath, change }) => text(specValidate(projectPath, change)));
-    server.registerTool("spec_sync", {
-        description: "Promote a change's delta specs into the canonical spec/specs/ (per capability), without archiving. Backs the `sync` command.",
+    server.registerTool("lawbook_sync", {
+        description: "Promote a change's delta specs into the canonical lawbook/specs/ (per capability), without archiving. Backs the `sync` command.",
         inputSchema: {
             projectPath: z.string().describe("Absolute path to the project"),
-            change: z.string().describe("Change name (folder under spec/changes/)"),
+            change: z.string().describe("Change name (folder under lawbook/changes/)"),
         },
     }, async ({ projectPath, change }) => text(specSync(projectPath, change)));
-    server.registerTool("spec_archive", {
-        description: "Finalize a change: sync its delta specs into spec/specs/, then move it to spec/changes/archive/<date>-<name>/. Backs the `archive` command. Pass today's date as YYYY-MM-DD.",
+    server.registerTool("lawbook_archive", {
+        description: "Finalize a change: sync its delta specs into lawbook/specs/, then move it to lawbook/changes/archive/<date>-<name>/. Backs the `archive` command. Pass today's date as YYYY-MM-DD.",
         inputSchema: {
             projectPath: z.string().describe("Absolute path to the project"),
-            change: z.string().describe("Change name (folder under spec/changes/)"),
+            change: z.string().describe("Change name (folder under lawbook/changes/)"),
             date: z.string().regex(/^\d{4}-\d{2}-\d{2}$/).describe("Today's date, YYYY-MM-DD"),
         },
     }, async ({ projectPath, change, date }) => text(specArchive(projectPath, change, date)));

package/dist/modules/tools/assets/packs/agents/backend-developer.md

@@ -22,7 +22,7 @@ Output path:
 - [`docs/standards/backend-standards.md`](../../docs/standards/backend-standards.md) — layers, docstrings, typing, tests, migrations
 - [`docs/standards/architecture.md`](../../docs/standards/architecture.md) — modules and layer boundaries
 - [`docs/standards/testing-standards.md`](../../docs/standards/testing-standards.md) — quality gates
-- [`docs/standards/spec-workflow.md`](../../docs/standards/spec-workflow.md) — spec-driven workflow
+- [`docs/standards/lawbook.md`](../../docs/standards/lawbook.md) — spec-driven workflow
 - [`docs/standards/base-standards.md`](../../docs/standards/base-standards.md) — cross-cutting rules
 
 Use `compass_explore` to locate the real entrypoints, routers, schemas,

package/dist/modules/tools/assets/packs/agents/frontend-developer.md

@@ -22,7 +22,7 @@ Output path:
 - [`docs/standards/frontend-standards.md`](../../docs/standards/frontend-standards.md) — layers, rendering boundaries, state, i18n, UI
 - [`docs/standards/architecture.md`](../../docs/standards/architecture.md) — modules and layer boundaries
 - [`docs/standards/testing-standards.md`](../../docs/standards/testing-standards.md) — quality gates
-- [`docs/standards/spec-workflow.md`](../../docs/standards/spec-workflow.md) — spec-driven workflow
+- [`docs/standards/lawbook.md`](../../docs/standards/lawbook.md) — spec-driven workflow
 - [`docs/standards/base-standards.md`](../../docs/standards/base-standards.md) — cross-cutting rules
 
 Use `compass_explore` to locate the real entry files, feature routes, shared

package/dist/server.js

@@ -1,7 +1,7 @@
 import { McpServer } from "@modelcontextprotocol/sdk/server/mcp.js";
 import { StdioServerTransport } from "@modelcontextprotocol/sdk/server/stdio.js";
 import { registerCompass } from "./modules/compass/register.js";
-import { registerSpec } from "./modules/spec/register.js";
+import { registerSpec } from "./modules/lawbook/register.js";
 import { registerFoundation } from "./modules/foundation/register.js";
 import { registerTools } from "./modules/tools/register.js";
 /** Build the speclaw MCP server with every module's tools registered. */
@@ -9,7 +9,7 @@ export function buildServer() {
     const server = new McpServer({ name: "speclaw", version: "0.1.0" });
     // Each module contributes its own MCP tools. Adding a module = one line here.
     registerFoundation(server); // init_project, scaffold, configure_agent, doctor
-    registerSpec(server); // spec_init, spec_validate, spec_sync, spec_archive, spec_list
+    registerSpec(server); // lawbook_init, lawbook_validate, lawbook_sync, lawbook_archive, lawbook_list
     registerCompass(server); // compass_index, explore, search, recall, impact, trace, watch
     registerTools(server); // list_packs, add_pack
     return server;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@esneiderbravo/speclaw",
-  "version": "0.1.0",
+  "version": "0.1.2",
   "publishConfig": {
     "access": "public"
   },
@@ -17,6 +17,14 @@
   ],
   "author": "Esneider Bravo",
   "license": "MIT",
+  "repository": {
+    "type": "git",
+    "url": "git+https://github.com/esneiderbravo/speclaw.git"
+  },
+  "homepage": "https://github.com/esneiderbravo/speclaw#readme",
+  "bugs": {
+    "url": "https://github.com/esneiderbravo/speclaw/issues"
+  },
   "type": "module",
   "bin": {
     "speclaw": "dist/cli/index.js"
@@ -28,6 +36,7 @@
   ],
   "scripts": {
     "build": "tsc && node scripts/copy-assets.mjs",
+    "brand": "node scripts/render-brand.mjs",
     "start": "node dist/cli/index.js",
     "prepublishOnly": "npm run build"
   },
@@ -43,6 +52,7 @@
     "zod": "^3.23.0"
   },
   "devDependencies": {
+    "@resvg/resvg-js": "^2.6.2",
     "@types/node": "^22.0.0",
     "typescript": "^5.6.0"
   }

package/dist/modules/spec/assets/skills/sync/SKILL.md

@@ -1,21 +0,0 @@
----
-name: sync
-description: Promote a change's delta specs into the canonical specs, without archiving. Use when the user wants to update the source-of-truth specs from a change: "sync the specs", "update the canonical specs", "promote the specs". Part of speclaw's spec module (draft → build → sync → archive).
----
-
-# sync — Promote delta specs to canonical
-
-Update the project's canonical specifications (`spec/specs/`) with a change's
-delta specs, without archiving the change. Use this when the specs should
-become the source of truth but the change isn't finished (e.g. multi-PR work).
-
-## Steps
-
-1. Confirm which change to sync (run `spec_list` if unsure).
-2. Run `spec_validate` for the change; do not sync a change whose specs are
-   invalid.
-3. Run the `spec_sync` tool for the change. It copies each
-   `spec/changes/<name>/specs/<capability>/spec.md` over the canonical
-   `spec/specs/<capability>/spec.md` and reports what it promoted.
-4. Report the promoted files to the user. The change stays active — `archive`
-   it when it's fully done.