@appchy/jarvis 0.1.37 → 0.1.39

package/dist/hooks/user-prompt-submit.js

@@ -5,33 +5,11 @@ import { appendFile, mkdir } from "fs/promises";
 import { join } from "path";
 
 // src/config.ts
-import fs from "fs";
 import path from "path";
 import os from "os";
-import { fileURLToPath } from "url";
-var __filename = fileURLToPath(import.meta.url);
-var __dirname = path.dirname(__filename);
-function isDev() {
-  const candidates = [
-    path.join(__dirname, "env.json"),
-    path.join(__dirname, "..", "env.json")
-  ];
-  for (const envFile of candidates) {
-    try {
-      const data = JSON.parse(fs.readFileSync(envFile, "utf-8"));
-      return data.env === "development";
-    } catch {
-    }
-  }
-  return false;
-}
-function resolveConfigDir() {
-  if (process.env.JARVIS_CONFIG_DIR) return process.env.JARVIS_CONFIG_DIR;
-  const base = path.join(os.homedir(), ".jarvis");
-  return isDev() ? path.join(base, "dev") : base;
-}
 function configDir() {
-  return resolveConfigDir();
+  if (process.env.JARVIS_CONFIG_DIR) return process.env.JARVIS_CONFIG_DIR;
+  return path.join(os.homedir(), ".jarvis");
 }
 function getHooksDir() {
   return path.join(configDir(), "hooks");
@@ -39,9 +17,9 @@ function getHooksDir() {
 
 // src/hooks/drop.ts
 async function appendDrop(req) {
-  if (!req.sessionId || !req.kind || !req.uniqId) {
+  if (!req.sessionId || !req.type || !req.uniqId) {
     process.stderr.write(
-      `[hook] skip ${req.kind ?? "?"} missing field sessionId=${!!req.sessionId} uniqId=${!!req.uniqId}
+      `[hook] skip ${req.type ?? "?"} missing field sessionId=${!!req.sessionId} uniqId=${!!req.uniqId}
 `
     );
     return;
@@ -52,7 +30,7 @@ async function appendDrop(req) {
 `);
   });
   const envelope = {
-    kind: req.kind,
+    type: req.type,
     sessionId: req.sessionId,
     ts: (/* @__PURE__ */ new Date()).toISOString(),
     uniqId: req.uniqId,
@@ -62,7 +40,7 @@ async function appendDrop(req) {
   try {
     await appendFile(file, JSON.stringify(envelope) + "\n");
     process.stderr.write(
-      `[hook] ${req.kind} appended sessionId=${req.sessionId} uniqId=${req.uniqId}
+      `[hook] ${req.type} appended sessionId=${req.sessionId} uniqId=${req.uniqId}
 `
     );
   } catch (err) {
@@ -101,7 +79,7 @@ async function main() {
     ...p.cwd ? { cwd: p.cwd } : {}
   };
   await appendDrop({
-    kind: "user-prompt-submit",
+    type: "user-prompt-submit",
     sessionId,
     uniqId: `user-prompt-submit-${ts}`,
     data

package/dist/hooks/user-prompt-submit.js.map

@@ -1 +1 @@
-{"version":3,"sources":["../../src/hooks/drop.ts","../../src/config.ts","../../src/hooks/user-prompt-submit.ts"],"sourcesContent":["/**\n * Shared helpers for CC hook scripts.\n *\n * Each hook script (pre-tool-use, session-start, stop, …) is a tiny\n * stdin → append-line → exit binary. They all write to the same per-\n * session JSONL at `<hooksDir>/<sessionId>.jsonl`. This module\n * concentrates the envelope shape and the atomic append so the per-\n * hook scripts stay <30 lines each.\n *\n * Hot-path constraints: NEVER block, NEVER network, NEVER read user\n * input. Pure stdin parse + filesystem append + exit. Worst-case one\n * `mkdir` + one `appendFile` per fire.\n */\n\nimport { appendFile, mkdir } from \"node:fs/promises\";\nimport { join } from \"node:path\";\n\nimport { getHooksDir } from \"../config\";\n\n/** Wire-format envelope written one-per-line to the hook JSONL.\n *  The watcher in `sessions.ts` parses this exact shape — keep in sync. */\nexport interface HookDropEnvelope<TData = unknown> {\n  kind: string;\n  sessionId: string;\n  ts: string;\n  /** Idempotency key. Lets the watcher's replay-on-restart skip drops\n   *  whose effects were already emitted (see `HookCursor.applied`). */\n  uniqId: string;\n  data: TData;\n}\n\nexport interface AppendDropRequest<TData> {\n  kind: string;\n  sessionId: string;\n  uniqId: string;\n  data: TData;\n}\n\n/** Append one envelope line to the per-session hook JSONL. Atomic between\n *  hook processes via POSIX `O_APPEND` (Node's `fs.appendFile`) — concurrent\n *  appends from different CC sessions / hook kinds can't interleave bytes\n *  within a line as long as the line stays < `PIPE_BUF` (4KB). Drops are\n *  <1KB in practice, so this is safe without locks.\n *\n *  Stderr logs are written so `tail -f ~/.jarvis[/dev]/hooks/hook.log` (when\n *  CC pipes hook stderr there, which it does by default) shows what fired.\n *  Stderr never breaks CC — it only watches stdout for decision JSON. */\nexport async function appendDrop<TData>(req: AppendDropRequest<TData>): Promise<void> {\n  if (!req.sessionId || !req.kind || !req.uniqId) {\n    process.stderr.write(\n      `[hook] skip ${req.kind ?? \"?\"} missing field ` +\n        `sessionId=${!!req.sessionId} uniqId=${!!req.uniqId}\\n`,\n    );\n    return;\n  }\n  const dir = getHooksDir();\n  await mkdir(dir, { recursive: true }).catch((err) => {\n    process.stderr.write(`[hook] mkdir failed ${dir}: ${err}\\n`);\n  });\n  const envelope: HookDropEnvelope<TData> = {\n    kind: req.kind,\n    sessionId: req.sessionId,\n    ts: new Date().toISOString(),\n    uniqId: req.uniqId,\n    data: req.data,\n  };\n  const file = join(dir, `${req.sessionId}.jsonl`);\n  try {\n    await appendFile(file, JSON.stringify(envelope) + \"\\n\");\n    process.stderr.write(\n      `[hook] ${req.kind} appended sessionId=${req.sessionId} uniqId=${req.uniqId}\\n`,\n    );\n  } catch (err) {\n    process.stderr.write(`[hook] append failed ${file}: ${err}\\n`);\n  }\n}\n\n/** Read CC's hook payload from stdin. Returns `null` on parse failure\n *  (never throws — the hook must never block CC). */\nexport async function readHookStdin<T = Record<string, unknown>>(): Promise<T | null> {\n  try {\n    const chunks: Buffer[] = [];\n    for await (const chunk of process.stdin) {\n      chunks.push(typeof chunk === \"string\" ? Buffer.from(chunk) : chunk);\n    }\n    const raw = Buffer.concat(chunks).toString(\"utf-8\");\n    if (!raw) return null;\n    return JSON.parse(raw) as T;\n  } catch {\n    return null;\n  }\n}\n\n/** Hard cap any hook so an exotic stdin stall can't pile up forever\n *  before CC's terminal prompt fires. We exit 0 with no output → CC\n *  proceeds with its normal permission flow. */\nexport function installHookTimeout(ms = 750): void {\n  const timer = setTimeout(() => process.exit(0), ms);\n  timer.unref();\n}\n","/**\n * Agent Config\n *\n * Manages ~/.jarvis/config.json — saved by `jarvis connect <token>`,\n * read on `jarvis start`.\n */\n\nimport fs from \"fs\";\nimport path from \"path\";\nimport os from \"os\";\nimport { fileURLToPath } from \"url\";\n\n// =============================================================================\n// Types\n// =============================================================================\n\nexport interface AgentConfig {\n  /** Cloud WS API URL (from connect token) */\n  apiUrl?: string;\n  /** JWT auth token (from connect token) */\n  token?: string;\n  /** Long-lived refresh token for obtaining new access tokens */\n  refreshToken?: string;\n  /** User ID */\n  userId: string;\n  /** Environment ID */\n  envId?: string;\n  /** Workspace root path for repo operations */\n  workspacePath?: string;\n  /** Web app URL for browser-based auth */\n  appUrl?: string;\n  /** Anthropic API key (for local-only use without cloud) */\n  anthropicApiKey?: string;\n  /** Use Anthropic subscription instead of API key */\n  useSubscription?: boolean;\n  /** When the config was last updated */\n  connectedAt?: string;\n}\n\nexport interface ConnectToken {\n  apiUrl: string;\n  jwt: string;\n  refreshToken: string;\n  userId: string;\n  envId: string;\n}\n\n// =============================================================================\n// Paths\n// =============================================================================\n\n// =============================================================================\n// Environment (single source of truth)\n// =============================================================================\n\nconst __filename = fileURLToPath(import.meta.url);\nconst __dirname = path.dirname(__filename);\n\n/** Single source of truth for dev vs prod.\n *  Two locations, picked by which file is shipped:\n *    Dev:  apps/cli/env.json     (committed, `{ \"env\": \"development\" }`)\n *    Prod: apps/cli/dist/env.json (written by tsup build, `{ \"env\": \"production\" }`)\n *  We try the prod-style sibling first (next to bin.js when bundled), then fall\n *  back to the dev-style parent path (one up from src/config.ts). The prod bundle\n *  has no `..` parent env.json, and the dev source tree has no sibling env.json,\n *  so the two never collide. Safe default if neither exists: prod. */\nexport function isDev(): boolean {\n  const candidates = [\n    path.join(__dirname, \"env.json\"),\n    path.join(__dirname, \"..\", \"env.json\"),\n  ];\n  for (const envFile of candidates) {\n    try {\n      const data = JSON.parse(fs.readFileSync(envFile, \"utf-8\"));\n      return data.env === \"development\";\n    } catch {\n      /* try next candidate */\n    }\n  }\n  return false;\n}\n\nconst PROD_APP_URL = \"https://jarvis.appchy.com\";\nconst DEV_APP_URL = \"http://localhost:3000\";\n\nconst PROD_WS_URL = \"wss://jarvis.appchy.com/ws\";\nconst DEV_WS_URL = \"ws://localhost:7863\";\n\n/** App URL for the current environment. */\nexport function getDefaultAppUrl(): string {\n  return isDev() ? (process.env.APP_URL || DEV_APP_URL) : PROD_APP_URL;\n}\n\n/** WS hub URL for the current environment. Hardcoded per build so the prod\n *  binary can never subscribe to the dev hub (or vice versa) regardless of\n *  what's stored in `config.apiUrl`. Dev permits a `JARVIS_UPSTREAM_URL`\n *  override for tests/CI on a non-default port; prod has no escape hatch. */\nexport function getDefaultWsUrl(): string {\n  return isDev() ? (process.env.JARVIS_UPSTREAM_URL || DEV_WS_URL) : PROD_WS_URL;\n}\n\n// =============================================================================\n// Config directory\n// =============================================================================\n\n/** Determine config directory.\n *  - JARVIS_CONFIG_DIR env var takes priority (escape hatch for CI/testing)\n *  - dev → ~/.jarvis/dev/\n *  - prod → ~/.jarvis/\n *\n *  Called fresh on every read so test environments that set\n *  `JARVIS_CONFIG_DIR` AFTER module load still see the override — caching\n *  the value at module init would lock tests onto the host's real\n *  `~/.jarvis/dev/` and leak production state into the in-memory infra. */\nfunction resolveConfigDir(): string {\n  if (process.env.JARVIS_CONFIG_DIR) return process.env.JARVIS_CONFIG_DIR;\n  const base = path.join(os.homedir(), \".jarvis\");\n  return isDev() ? path.join(base, \"dev\") : base;\n}\n\nfunction configDir(): string {\n  return resolveConfigDir();\n}\n\nfunction configFile(): string {\n  return path.join(configDir(), \"config.json\");\n}\n\n/** Absolute path to the per-daemon config directory.\n *  `prod` → `~/.jarvis/`, `dev` → `~/.jarvis/dev/`. */\nexport function getConfigDir(): string {\n  return configDir();\n}\n\n/** Per-daemon directory for PreToolUse hook drop files. The CC hook script\n *  writes `<sessionId>/<toolUseId>.json` here; the sessions watcher consumes\n *  them. Prod and dev daemons each own their own subtree so a hook installed\n *  for one never feeds the other. */\nexport function getHooksDir(): string {\n  return path.join(configDir(), \"hooks\");\n}\n\n// =============================================================================\n// Operations\n// =============================================================================\n\nexport function loadConfig(): AgentConfig | null {\n  try {\n    const raw = fs.readFileSync(configFile(), \"utf-8\");\n    return JSON.parse(raw) as AgentConfig;\n  } catch {\n    return null;\n  }\n}\n\nexport function saveConfig(config: AgentConfig): void {\n  fs.mkdirSync(configDir(), { recursive: true });\n  fs.writeFileSync(configFile(), JSON.stringify(config, null, 2) + \"\\n\");\n}\n\nexport function clearConfig(): void {\n  try {\n    fs.unlinkSync(configFile());\n  } catch {}\n}\n\nexport function parseConnectToken(token: string): ConnectToken {\n  try {\n    const decoded = Buffer.from(token, \"base64\").toString(\"utf-8\");\n    const parsed = JSON.parse(decoded);\n    if (!parsed.apiUrl || !parsed.jwt || !parsed.userId) {\n      throw new Error(\"Invalid token: missing required fields (apiUrl, jwt, userId)\");\n    }\n    return parsed as ConnectToken;\n  } catch (err) {\n    if (err instanceof SyntaxError) {\n      throw new Error(\"Invalid token: not valid base64-encoded JSON\");\n    }\n    throw err;\n  }\n}\n\nexport function getConfigPath(): string {\n  return configFile();\n}\n","/**\n * UserPromptSubmit hook — drops an envelope each time a terminal `claude`\n * user submits a prompt. The daemon SDK runs with `settingSources: []`\n * so its own `query()` calls never trigger this hook — every drop\n * observed here is unambiguously a terminal-typed turn.\n *\n * Used to flip `SessionCacheEntry.controller` to `\"claudeCode\"` on the\n * watcher side, surfacing the controller change in the web UI's pill.\n */\n\nimport { appendDrop, installHookTimeout, readHookStdin } from \"./drop\";\n\ninterface CcUserPromptSubmitInput {\n  session_id?: string;\n  transcript_path?: string;\n  cwd?: string;\n  prompt?: string;\n}\n\ninterface UserPromptSubmitDropData {\n  transcriptPath?: string;\n  cwd?: string;\n}\n\ninstallHookTimeout();\n\nasync function main(): Promise<void> {\n  const p = await readHookStdin<CcUserPromptSubmitInput>();\n  if (!p) return;\n  const sessionId = p.session_id;\n  if (!sessionId) return;\n\n  const ts = new Date().toISOString();\n  const data: UserPromptSubmitDropData = {\n    ...(p.transcript_path ? { transcriptPath: p.transcript_path } : {}),\n    ...(p.cwd ? { cwd: p.cwd } : {}),\n  };\n\n  await appendDrop<UserPromptSubmitDropData>({\n    kind: \"user-prompt-submit\",\n    sessionId,\n    uniqId: `user-prompt-submit-${ts}`,\n    data,\n  });\n}\n\nvoid main().finally(() => process.exit(0));\n"],"mappings":";;;AAcA,SAAS,YAAY,aAAa;AAClC,SAAS,YAAY;;;ACRrB,OAAO,QAAQ;AACf,OAAO,UAAU;AACjB,OAAO,QAAQ;AACf,SAAS,qBAAqB;AA6C9B,IAAM,aAAa,cAAc,YAAY,GAAG;AAChD,IAAM,YAAY,KAAK,QAAQ,UAAU;AAUlC,SAAS,QAAiB;AAC/B,QAAM,aAAa;AAAA,IACjB,KAAK,KAAK,WAAW,UAAU;AAAA,IAC/B,KAAK,KAAK,WAAW,MAAM,UAAU;AAAA,EACvC;AACA,aAAW,WAAW,YAAY;AAChC,QAAI;AACF,YAAM,OAAO,KAAK,MAAM,GAAG,aAAa,SAAS,OAAO,CAAC;AACzD,aAAO,KAAK,QAAQ;AAAA,IACtB,QAAQ;AAAA,IAER;AAAA,EACF;AACA,SAAO;AACT;AAkCA,SAAS,mBAA2B;AAClC,MAAI,QAAQ,IAAI,kBAAmB,QAAO,QAAQ,IAAI;AACtD,QAAM,OAAO,KAAK,KAAK,GAAG,QAAQ,GAAG,SAAS;AAC9C,SAAO,MAAM,IAAI,KAAK,KAAK,MAAM,KAAK,IAAI;AAC5C;AAEA,SAAS,YAAoB;AAC3B,SAAO,iBAAiB;AAC1B;AAgBO,SAAS,cAAsB;AACpC,SAAO,KAAK,KAAK,UAAU,GAAG,OAAO;AACvC;;;AD7FA,eAAsB,WAAkB,KAA8C;AACpF,MAAI,CAAC,IAAI,aAAa,CAAC,IAAI,QAAQ,CAAC,IAAI,QAAQ;AAC9C,YAAQ,OAAO;AAAA,MACb,eAAe,IAAI,QAAQ,GAAG,4BACf,CAAC,CAAC,IAAI,SAAS,WAAW,CAAC,CAAC,IAAI,MAAM;AAAA;AAAA,IACvD;AACA;AAAA,EACF;AACA,QAAM,MAAM,YAAY;AACxB,QAAM,MAAM,KAAK,EAAE,WAAW,KAAK,CAAC,EAAE,MAAM,CAAC,QAAQ;AACnD,YAAQ,OAAO,MAAM,uBAAuB,GAAG,KAAK,GAAG;AAAA,CAAI;AAAA,EAC7D,CAAC;AACD,QAAM,WAAoC;AAAA,IACxC,MAAM,IAAI;AAAA,IACV,WAAW,IAAI;AAAA,IACf,KAAI,oBAAI,KAAK,GAAE,YAAY;AAAA,IAC3B,QAAQ,IAAI;AAAA,IACZ,MAAM,IAAI;AAAA,EACZ;AACA,QAAM,OAAO,KAAK,KAAK,GAAG,IAAI,SAAS,QAAQ;AAC/C,MAAI;AACF,UAAM,WAAW,MAAM,KAAK,UAAU,QAAQ,IAAI,IAAI;AACtD,YAAQ,OAAO;AAAA,MACb,UAAU,IAAI,IAAI,uBAAuB,IAAI,SAAS,WAAW,IAAI,MAAM;AAAA;AAAA,IAC7E;AAAA,EACF,SAAS,KAAK;AACZ,YAAQ,OAAO,MAAM,wBAAwB,IAAI,KAAK,GAAG;AAAA,CAAI;AAAA,EAC/D;AACF;AAIA,eAAsB,gBAAgE;AACpF,MAAI;AACF,UAAM,SAAmB,CAAC;AAC1B,qBAAiB,SAAS,QAAQ,OAAO;AACvC,aAAO,KAAK,OAAO,UAAU,WAAW,OAAO,KAAK,KAAK,IAAI,KAAK;AAAA,IACpE;AACA,UAAM,MAAM,OAAO,OAAO,MAAM,EAAE,SAAS,OAAO;AAClD,QAAI,CAAC,IAAK,QAAO;AACjB,WAAO,KAAK,MAAM,GAAG;AAAA,EACvB,QAAQ;AACN,WAAO;AAAA,EACT;AACF;AAKO,SAAS,mBAAmB,KAAK,KAAW;AACjD,QAAM,QAAQ,WAAW,MAAM,QAAQ,KAAK,CAAC,GAAG,EAAE;AAClD,QAAM,MAAM;AACd;;;AE3EA,mBAAmB;AAEnB,eAAe,OAAsB;AACnC,QAAM,IAAI,MAAM,cAAuC;AACvD,MAAI,CAAC,EAAG;AACR,QAAM,YAAY,EAAE;AACpB,MAAI,CAAC,UAAW;AAEhB,QAAM,MAAK,oBAAI,KAAK,GAAE,YAAY;AAClC,QAAM,OAAiC;AAAA,IACrC,GAAI,EAAE,kBAAkB,EAAE,gBAAgB,EAAE,gBAAgB,IAAI,CAAC;AAAA,IACjE,GAAI,EAAE,MAAM,EAAE,KAAK,EAAE,IAAI,IAAI,CAAC;AAAA,EAChC;AAEA,QAAM,WAAqC;AAAA,IACzC,MAAM;AAAA,IACN;AAAA,IACA,QAAQ,sBAAsB,EAAE;AAAA,IAChC;AAAA,EACF,CAAC;AACH;AAEA,KAAK,KAAK,EAAE,QAAQ,MAAM,QAAQ,KAAK,CAAC,CAAC;","names":[]}
+{"version":3,"sources":["../../src/hooks/drop.ts","../../src/config.ts","../../src/hooks/user-prompt-submit.ts"],"sourcesContent":["/**\n * Shared helpers for CC hook scripts.\n *\n * Each hook script (pre-tool-use, session-start, stop, …) is a tiny\n * stdin → append-line → exit binary. They all write to the same per-\n * session JSONL at `<hooksDir>/<sessionId>.jsonl`. This module\n * concentrates the envelope shape and the atomic append so the per-\n * hook scripts stay <30 lines each.\n *\n * Hot-path constraints: NEVER block, NEVER network, NEVER read user\n * input. Pure stdin parse + filesystem append + exit. Worst-case one\n * `mkdir` + one `appendFile` per fire.\n */\n\nimport { appendFile, mkdir } from \"node:fs/promises\";\nimport { join } from \"node:path\";\n\nimport { getHooksDir } from \"../config\";\n\n/** Wire-format envelope written one-per-line to the hook JSONL.\n *  The watcher in `sessions.ts` parses this exact shape — keep in sync. */\nexport interface HookDropEnvelope<TData = unknown> {\n  type: string;\n  sessionId: string;\n  ts: string;\n  /** Idempotency key. Lets the watcher's replay-on-restart skip drops\n   *  whose effects were already emitted (see `HookCursor.applied`). */\n  uniqId: string;\n  data: TData;\n}\n\nexport interface AppendDropRequest<TData> {\n  type: string;\n  sessionId: string;\n  uniqId: string;\n  data: TData;\n}\n\n/** Append one envelope line to the per-session hook JSONL. Atomic between\n *  hook processes via POSIX `O_APPEND` (Node's `fs.appendFile`) — concurrent\n *  appends from different CC sessions / hook types can't interleave bytes\n *  within a line as long as the line stays < `PIPE_BUF` (4KB). Drops are\n *  <1KB in practice, so this is safe without locks.\n *\n *  Stderr logs are written so `tail -f ~/.jarvis/hooks/hook.log` (when\n *  CC pipes hook stderr there, which it does by default) shows what fired.\n *  Stderr never breaks CC — it only watches stdout for decision JSON. */\nexport async function appendDrop<TData>(req: AppendDropRequest<TData>): Promise<void> {\n  if (!req.sessionId || !req.type || !req.uniqId) {\n    process.stderr.write(\n      `[hook] skip ${req.type ?? \"?\"} missing field ` +\n        `sessionId=${!!req.sessionId} uniqId=${!!req.uniqId}\\n`,\n    );\n    return;\n  }\n  const dir = getHooksDir();\n  await mkdir(dir, { recursive: true }).catch((err) => {\n    process.stderr.write(`[hook] mkdir failed ${dir}: ${err}\\n`);\n  });\n  const envelope: HookDropEnvelope<TData> = {\n    type: req.type,\n    sessionId: req.sessionId,\n    ts: new Date().toISOString(),\n    uniqId: req.uniqId,\n    data: req.data,\n  };\n  const file = join(dir, `${req.sessionId}.jsonl`);\n  try {\n    await appendFile(file, JSON.stringify(envelope) + \"\\n\");\n    process.stderr.write(\n      `[hook] ${req.type} appended sessionId=${req.sessionId} uniqId=${req.uniqId}\\n`,\n    );\n  } catch (err) {\n    process.stderr.write(`[hook] append failed ${file}: ${err}\\n`);\n  }\n}\n\n/** Read CC's hook payload from stdin. Returns `null` on parse failure\n *  (never throws — the hook must never block CC). */\nexport async function readHookStdin<T = Record<string, unknown>>(): Promise<T | null> {\n  try {\n    const chunks: Buffer[] = [];\n    for await (const chunk of process.stdin) {\n      chunks.push(typeof chunk === \"string\" ? Buffer.from(chunk) : chunk);\n    }\n    const raw = Buffer.concat(chunks).toString(\"utf-8\");\n    if (!raw) return null;\n    return JSON.parse(raw) as T;\n  } catch {\n    return null;\n  }\n}\n\n/** Hard cap any hook so an exotic stdin stall can't pile up forever\n *  before CC's terminal prompt fires. We exit 0 with no output → CC\n *  proceeds with its normal permission flow. */\nexport function installHookTimeout(ms = 750): void {\n  const timer = setTimeout(() => process.exit(0), ms);\n  timer.unref();\n}\n","/**\n * Agent Config\n *\n * Manages ~/.jarvis/config.json — saved by `jarvis connect <token>`,\n * read on `jarvis start`.\n */\n\nimport fs from \"fs\";\nimport path from \"path\";\nimport os from \"os\";\n\n// =============================================================================\n// Types\n// =============================================================================\n\nexport interface AgentConfig {\n  /** The jarvis this machine joined — the address a person opens in a browser,\n   *  and what pairing talks to. Ours by default; `jarvis init --url <url>` joins\n   *  someone else's. */\n  url?: string;\n  /** WS hub URL this machine dials. Written once, by pairing, from the hub the\n   *  joined instance named — and never from a flag, an environment variable or\n   *  any later command. Re-pointing a machine means unpairing it first. */\n  hubUrl?: string;\n  /** JWT auth token (from connect token) */\n  token?: string;\n  /** Long-lived refresh token for obtaining new access tokens */\n  refreshToken?: string;\n  /** User ID */\n  userId: string;\n  /** Environment ID */\n  envId?: string;\n  /** Workspace root path for repo operations */\n  workspacePath?: string;\n  /** Anthropic API key (for local-only use without cloud) */\n  anthropicApiKey?: string;\n  /** Use Anthropic subscription instead of API key */\n  useSubscription?: boolean;\n  /** When the config was last updated */\n  connectedAt?: string;\n}\n\nexport interface ConnectToken {\n  hubUrl: string;\n  jwt: string;\n  refreshToken: string;\n  userId: string;\n  envId: string;\n}\n\n// =============================================================================\n// Environment\n// =============================================================================\n\n/** The jarvis a machine pairs with when nothing else is named. Only ever read\n *  by pairing: `jarvis init --url <url>` joins someone else's instead, and the\n *  hub URL is whatever that instance hands back. */\nexport const DEFAULT_URL = \"https://jarvis.appchy.com\";\n\n// =============================================================================\n// Config directory\n// =============================================================================\n\n/** The config dir is the machine's identity: what it paired as, and therefore\n *  which hub it dials. One daemon per dir, so a second identity on the same\n *  machine — a storage rig, a localhost instance — is a second dir, named by\n *  `JARVIS_CONFIG_DIR`, never a second binary.\n *\n *  Called fresh on every read so a test that sets `JARVIS_CONFIG_DIR` AFTER\n *  module load still sees the override — caching at module init would lock it\n *  onto the host's real `~/.jarvis/` and leak production state into the\n *  in-memory infra. */\nfunction configDir(): string {\n  if (process.env.JARVIS_CONFIG_DIR) return process.env.JARVIS_CONFIG_DIR;\n  return path.join(os.homedir(), \".jarvis\");\n}\n\nfunction configFile(): string {\n  return path.join(configDir(), \"config.json\");\n}\n\n/** Absolute path to the per-daemon config directory — `~/.jarvis/` unless\n *  `JARVIS_CONFIG_DIR` names another. */\nexport function getConfigDir(): string {\n  return configDir();\n}\n\n/** Per-daemon directory for PreToolUse hook drop files. The CC hook script\n *  writes `<sessionId>/<toolUseId>.json` here; the sessions watcher consumes\n *  them. Each daemon owns the subtree under its own config dir, so a hook\n *  installed for one never feeds another. */\nexport function getHooksDir(): string {\n  return path.join(configDir(), \"hooks\");\n}\n\n// =============================================================================\n// Operations\n// =============================================================================\n\n/** Read the machine's config, accepting the names these two fields used to\n *  carry. `appUrl`/`apiUrl` were renamed on 2026-08-15 — `apiUrl` never held an\n *  API URL, it held the hub's. A config written before that still loads, and\n *  `saveConfig` only ever writes the current names, so a machine heals itself on\n *  its next write with nothing to run. Delete this tolerance once no config\n *  predating the rename is in use. */\nexport function loadConfig(): AgentConfig | null {\n  try {\n    const stored = JSON.parse(fs.readFileSync(configFile(), \"utf-8\")) as AgentConfig &\n      Partial<{ appUrl: string; apiUrl: string }>;\n    const { appUrl, apiUrl, ...config } = stored;\n    const url = config.url ?? appUrl;\n    const hubUrl = config.hubUrl ?? apiUrl;\n    return {\n      ...config,\n      ...(url !== undefined ? { url } : {}),\n      ...(hubUrl !== undefined ? { hubUrl } : {}),\n    };\n  } catch {\n    return null;\n  }\n}\n\n/** Persist the machine's config.\n *\n *  Refuses to move an already-paired machine to a different hub. A machine that\n *  joins the wrong control plane hands it credentials, so re-pointing one is a\n *  deliberate act — `jarvis unpair` (which clears the config) and then pair\n *  again — rather than something a stale token or a mistyped command can do on\n *  its way past. Re-pairing to the same hub is unaffected. */\nexport function saveConfig(config: AgentConfig): void {\n  const paired = loadConfig();\n  if (paired?.hubUrl && config.hubUrl && config.hubUrl !== paired.hubUrl) {\n    throw new Error(\n      `This machine is paired with ${paired.hubUrl} and cannot be moved to ${config.hubUrl}.\\n` +\n        `  Run 'jarvis unpair' first if you mean to join a different jarvis.`,\n    );\n  }\n  fs.mkdirSync(configDir(), { recursive: true });\n  fs.writeFileSync(configFile(), JSON.stringify(config, null, 2) + \"\\n\");\n}\n\nexport function clearConfig(): void {\n  try {\n    fs.unlinkSync(configFile());\n  } catch {}\n}\n\nexport function parseConnectToken(token: string): ConnectToken {\n  try {\n    const decoded = Buffer.from(token, \"base64\").toString(\"utf-8\");\n    const parsed = JSON.parse(decoded);\n    if (!parsed.hubUrl || !parsed.jwt || !parsed.userId) {\n      throw new Error(\"Invalid token: missing required fields (hubUrl, jwt, userId)\");\n    }\n    return parsed as ConnectToken;\n  } catch (err) {\n    if (err instanceof SyntaxError) {\n      throw new Error(\"Invalid token: not valid base64-encoded JSON\");\n    }\n    throw err;\n  }\n}\n\nexport function getConfigPath(): string {\n  return configFile();\n}\n","/**\n * UserPromptSubmit hook — drops an envelope each time a `claude` user submits\n * a prompt. Jarvis starts no sessions, so every drop observed here is a\n * person's turn.\n *\n * Used to flip `SessionCacheEntry.controller` to `\"claudeCode\"` on the\n * watcher side, surfacing the controller change in the web UI's pill.\n */\n\nimport { appendDrop, installHookTimeout, readHookStdin } from \"./drop\";\n\ninterface CcUserPromptSubmitInput {\n  session_id?: string;\n  transcript_path?: string;\n  cwd?: string;\n  prompt?: string;\n}\n\ninterface UserPromptSubmitDropData {\n  transcriptPath?: string;\n  cwd?: string;\n}\n\ninstallHookTimeout();\n\nasync function main(): Promise<void> {\n  const p = await readHookStdin<CcUserPromptSubmitInput>();\n  if (!p) return;\n  const sessionId = p.session_id;\n  if (!sessionId) return;\n\n  const ts = new Date().toISOString();\n  const data: UserPromptSubmitDropData = {\n    ...(p.transcript_path ? { transcriptPath: p.transcript_path } : {}),\n    ...(p.cwd ? { cwd: p.cwd } : {}),\n  };\n\n  await appendDrop<UserPromptSubmitDropData>({\n    type: \"user-prompt-submit\",\n    sessionId,\n    uniqId: `user-prompt-submit-${ts}`,\n    data,\n  });\n}\n\nvoid main().finally(() => process.exit(0));\n"],"mappings":";;;AAcA,SAAS,YAAY,aAAa;AAClC,SAAS,YAAY;;;ACPrB,OAAO,UAAU;AACjB,OAAO,QAAQ;AA+Df,SAAS,YAAoB;AAC3B,MAAI,QAAQ,IAAI,kBAAmB,QAAO,QAAQ,IAAI;AACtD,SAAO,KAAK,KAAK,GAAG,QAAQ,GAAG,SAAS;AAC1C;AAgBO,SAAS,cAAsB;AACpC,SAAO,KAAK,KAAK,UAAU,GAAG,OAAO;AACvC;;;AD9CA,eAAsB,WAAkB,KAA8C;AACpF,MAAI,CAAC,IAAI,aAAa,CAAC,IAAI,QAAQ,CAAC,IAAI,QAAQ;AAC9C,YAAQ,OAAO;AAAA,MACb,eAAe,IAAI,QAAQ,GAAG,4BACf,CAAC,CAAC,IAAI,SAAS,WAAW,CAAC,CAAC,IAAI,MAAM;AAAA;AAAA,IACvD;AACA;AAAA,EACF;AACA,QAAM,MAAM,YAAY;AACxB,QAAM,MAAM,KAAK,EAAE,WAAW,KAAK,CAAC,EAAE,MAAM,CAAC,QAAQ;AACnD,YAAQ,OAAO,MAAM,uBAAuB,GAAG,KAAK,GAAG;AAAA,CAAI;AAAA,EAC7D,CAAC;AACD,QAAM,WAAoC;AAAA,IACxC,MAAM,IAAI;AAAA,IACV,WAAW,IAAI;AAAA,IACf,KAAI,oBAAI,KAAK,GAAE,YAAY;AAAA,IAC3B,QAAQ,IAAI;AAAA,IACZ,MAAM,IAAI;AAAA,EACZ;AACA,QAAM,OAAO,KAAK,KAAK,GAAG,IAAI,SAAS,QAAQ;AAC/C,MAAI;AACF,UAAM,WAAW,MAAM,KAAK,UAAU,QAAQ,IAAI,IAAI;AACtD,YAAQ,OAAO;AAAA,MACb,UAAU,IAAI,IAAI,uBAAuB,IAAI,SAAS,WAAW,IAAI,MAAM;AAAA;AAAA,IAC7E;AAAA,EACF,SAAS,KAAK;AACZ,YAAQ,OAAO,MAAM,wBAAwB,IAAI,KAAK,GAAG;AAAA,CAAI;AAAA,EAC/D;AACF;AAIA,eAAsB,gBAAgE;AACpF,MAAI;AACF,UAAM,SAAmB,CAAC;AAC1B,qBAAiB,SAAS,QAAQ,OAAO;AACvC,aAAO,KAAK,OAAO,UAAU,WAAW,OAAO,KAAK,KAAK,IAAI,KAAK;AAAA,IACpE;AACA,UAAM,MAAM,OAAO,OAAO,MAAM,EAAE,SAAS,OAAO;AAClD,QAAI,CAAC,IAAK,QAAO;AACjB,WAAO,KAAK,MAAM,GAAG;AAAA,EACvB,QAAQ;AACN,WAAO;AAAA,EACT;AACF;AAKO,SAAS,mBAAmB,KAAK,KAAW;AACjD,QAAM,QAAQ,WAAW,MAAM,QAAQ,KAAK,CAAC,GAAG,EAAE;AAClD,QAAM,MAAM;AACd;;;AE5EA,mBAAmB;AAEnB,eAAe,OAAsB;AACnC,QAAM,IAAI,MAAM,cAAuC;AACvD,MAAI,CAAC,EAAG;AACR,QAAM,YAAY,EAAE;AACpB,MAAI,CAAC,UAAW;AAEhB,QAAM,MAAK,oBAAI,KAAK,GAAE,YAAY;AAClC,QAAM,OAAiC;AAAA,IACrC,GAAI,EAAE,kBAAkB,EAAE,gBAAgB,EAAE,gBAAgB,IAAI,CAAC;AAAA,IACjE,GAAI,EAAE,MAAM,EAAE,KAAK,EAAE,IAAI,IAAI,CAAC;AAAA,EAChC;AAEA,QAAM,WAAqC;AAAA,IACzC,MAAM;AAAA,IACN;AAAA,IACA,QAAQ,sBAAsB,EAAE;AAAA,IAChC;AAAA,EACF,CAAC;AACH;AAEA,KAAK,KAAK,EAAE,QAAQ,MAAM,QAAQ,KAAK,CAAC,CAAC;","names":[]}

package/harness/assets/architecture-template.md

@@ -0,0 +1,53 @@
+# {{TITLE}} — technical architecture + phased plan
+
+<!-- NOT a claude.ai/design UI brief (see design.md for that). This is the
+     version-level TECHNICAL brief — the cross-task "plan FROM this" doc: the
+     shared seams, the migration/build slices, the rules that must not
+     regress. Owner of record for the cross-task design; each task's own
+     `plan.md` still owns its own As-found + Architecture at pickup. -->
+
+> Direction → <!-- rule id(s) -->
+<!-- Cite the governing rule ids (+ any narrowing/superseding ones) and, if this
+     version has one, the research report it draws from. -->
+
+## As-found
+
+<!-- Raw, factual account of how the in-scope code works today — file:line,
+     confirmed by the blast-radius sweep. No opinions. What exists, what's
+     missing, where the
+     seams already are. -->
+
+## Target architecture
+
+<!-- Lead with a diagram, then the rationale (why this shape, alternatives
+     weighed). The shared seams/contracts every task in this version builds
+     against. -->
+
+## Code map
+
+<!-- Per `code` region this version touches — a MAP of seams/decisions/links,
+     NEVER a code dump. Where Pass-1 topology + the architect's foundation
+     reasoning land (SKILL.md §Two-pass decomposition). One block per region;
+     omit a region until the cut actually touches it. -->
+
+### <code-region>
+
+- **Seam** — <the shared contract/boundary here; link `path:line`, don't paste>
+- **Known-next constraints** — <what later same-region tasks will need this seam
+  to support, so it isn't built too narrow>
+- **Consumers** — <the features/tasks that build on this seam (≥2 for a real
+  foundation)>
+- **Foundation task** — <the task that lands this seam first, if any; else "—">
+
+## Phases
+
+<!-- Each phase independently shippable (own acceptance, own commit) —
+     never a partial, unshippable slice. One subsection per phase:
+     name, what it delivers, what it depends on. -->
+
+1. **<phase-name>** — <what ships, dependencies>
+
+## Risks
+
+<!-- Open items / risks to resolve per-phase, measure-first. What could
+     invalidate the target architecture; what to watch for. -->

package/harness/assets/design-template.md

@@ -0,0 +1,89 @@
+# {{TITLE}} — claude.ai/design brief
+
+<!-- Paste this into https://claude.ai/design and link this repo. Claude Design
+     already has the full design context — the prototype in /wireframes/, the
+     codebase's components, architecture and styling.
+
+     Claude Design owns the "how" (layout, controls, copy, states). This brief
+     is the "what" — the version goal, the user stories, the audience. Don't
+     pre-spec screens or content shapes; let Claude Design propose them. -->
+
+## Goal
+
+<!-- One paragraph. The capability this version delivers in USER terms — what
+     can the user do after this ships that they cannot do today? Why does it
+     matter? No technical detail, no implementation hints. -->
+
+## User stories
+
+<!-- Lift from the feature stories of the features in this cut
+     (work/product/**.md §Stories — the durable owner; version stories.md
+     is retired). Each story in:
+     "As a <role>, I want <capability>, so that <outcome>."
+     followed by a short list of observable / verifiable behaviours it implies
+     (behaviours, not screens) — reference the feature's B-/AC- ids. -->
+
+## Audience
+
+<!-- Who the user is + what they already know — Claude Design needs this to
+     pitch affordances at the right level. One short paragraph. -->
+
+## Workflow
+
+Work in **two passes**, then clean up for export. Don't skip ahead — Pass 2
+implements what Pass 1 defines.
+
+### Pass 1 — Wireframes + behaviour
+
+Sketch the screens at low fidelity (layout, structure, key controls) and
+**define every behaviour alongside**. As you go, write the per-page spec to
+`ui.md` in this exact format:
+
+```
+# ui.md — {{TITLE}}
+
+## Page: <name>
+
+### Layout
+  <ASCII sketch: before>            <ASCII sketch: after>
+
+### Changed elements
+#### <element>
+- Does — <behaviour: what happens on interaction, what it reflects>
+- Looks — <visual states + variants, where it sits>
+- Relates to — <other elements/states it depends on or drives>
+- Blast radius — <sibling components, broker/protocol, persisted state>
+
+## Backend changes deduced
+- <what the client behaviour implies the broker / protocol / event model
+  must provide — the bridge into the implementation phase>
+```
+
+One section per page that changes; scope tightly (only changed elements
+appear, never untouched ones). Skip the "before" sketch for a brand-new page;
+skip the whole Layout block when the frame is unchanged and only inner
+elements moved. The Backend changes section at the end is mandatory — it is
+how the implementation phase finds its inputs.
+
+Iterate Pass 1 until every page's behaviour is settled in `ui.md`. Don't
+start the visual polish before this point.
+
+### Pass 2 — Live mock
+
+Implement what Pass 1 defined. Build the **polished HTML/CSS/JS prototype**,
+realising the behaviours from `ui.md` with the final visual style. The mock
+is the behavioural + visual source of truth.
+
+### Cleanup for export
+
+When the prototype is final:
+
+- **Delete old screenshots** captured during iteration.
+- **Re-take fresh screenshots** of every page in the final mock.
+- Re-check `ui.md` against the prototype (behaviour may have refined during
+  the polish pass) and update it if it drifted.
+- The project is **export-ready** — no dead files, no half-built states.
+
+The exported bundle (`project/` + `ui.md` + screenshots) drops into
+`/wireframes/` in the repo. The work skill takes it from there to decompose
+into tasks.

package/harness/assets/domains/architecture.md

@@ -0,0 +1,43 @@
+---
+type: domain
+id: architecture
+---
+
+# Architecture — how it is built
+
+## What belongs here
+
+Durable calls about **how the software is built** — the systems, their seams, the
+dependency rules, and the constraints a plan must not regress.
+
+Rules here live in `architecture/<system>.md`, not in this README: a system is a
+capability boundary that owns `code:` regions and hosts the rules governing them.
+This README is the domain's landing doc and carries the derived system index and
+dependency map. A region belongs to exactly ONE system.
+
+Its neighbours: [`product/`](../product/README.md) owns what the software must do —
+this domain owns the shape that delivers it.
+[`operations/`](../operations/README.md) owns getting it out and keeping it running;
+a build-time rule is this domain's, a deploy-time one is theirs.
+[`security/`](../security/README.md) owns what must stay safe while it runs.
+
+## Non-goals
+
+- **What the software does.** `product/`.
+- **How it ships and runs.** `operations/`.
+- **A rule about a kind of call rather than a system.** It belongs to the domain that owns that kind — filing it here because it was the only place that fit is the mis-filing the nine domains exist to end.
+- **Package inventory.** Derivable from the file tree; a system is not one-per-package.
+
+## Rules
+
+<!-- A durable rule lives in the domain that owns its KIND of call. Shape:
+
+     ### <id> — the rule, in one line
+     enforced_by: the check that catches a violation — a command, a test, a lint
+
+     `enforced_by: judgement` is legal where a person really must decide, and is
+     counted separately rather than treated as enforcement. An empty one is a wish.
+
+     This section is EMPTY ON PURPOSE in a fresh repo. Do not seed it with invented
+     rules to make the domain look occupied — an empty domain is a signpost saying
+     where a call will go when you make one. -->

package/harness/assets/domains/commercial.md

@@ -0,0 +1,42 @@
+---
+type: domain
+id: commercial
+---
+
+# Commercial — how we reach people and earn
+
+## What belongs here
+
+Durable calls about **reach and revenue** — pricing shape, packaging and tiers,
+positioning, distribution and partners, and how growth is measured.
+
+Expect many rules here to be `enforced_by: judgement`, and that is honest rather
+than lazy: a positioning call is not something a check can catch. They are still
+written down and still counted, because the alternative is that they live only in
+somebody's head and get silently re-argued.
+
+Its neighbours: [`product/`](../product/README.md) owns what the thing does — this
+domain owns who it is for and what it costs. [`legal/`](../legal/README.md) owns
+what a commitment binds us to. [`design/`](../design/README.md) owns the surface;
+brand *reach* is this domain's, brand *rendering* is theirs.
+
+## Non-goals
+
+- **What the product does.** `product/`.
+- **What a contract obliges.** `legal/`.
+- **How it is delivered technically.** `operations/`.
+- **A campaign.** That is work; the pricing rule behind it is durable.
+
+## Rules
+
+<!-- A durable rule lives in the domain that owns its KIND of call. Shape:
+
+     ### <id> — the rule, in one line
+     enforced_by: the check that catches a violation — a command, a test, a lint
+
+     `enforced_by: judgement` is legal where a person really must decide, and is
+     counted separately rather than treated as enforcement. An empty one is a wish.
+
+     This section is EMPTY ON PURPOSE in a fresh repo. Do not seed it with invented
+     rules to make the domain look occupied — an empty domain is a signpost saying
+     where a call will go when you make one. -->

package/harness/assets/domains/design.md

@@ -0,0 +1,42 @@
+---
+type: domain
+id: design
+---
+
+# Design — how it looks and reads
+
+## What belongs here
+
+Durable calls about the **visual and interaction surface** — layout, type, colour,
+motion, component behaviour, tone of the words on screen, and accessibility.
+
+A note on the word, because it costs sessions: **"design" unqualified means this
+domain**. A technical plan is "the plan", never "the design", however architectural
+it is. A repo that lets one word mean both ends up with two documents claiming to
+be the design of the same change.
+
+Its neighbours: [`product/`](../product/README.md) owns what a user must be able to
+do — this domain owns what that looks and feels like.
+[`support/`](../support/README.md) owns getting a stuck user moving; where a design
+choice is the thing that stuck them, the fix is this domain's.
+
+## Non-goals
+
+- **What the feature must do.** `product/`.
+- **The technical plan.** `architecture/`, and it is called the plan.
+- **Brand reach and positioning.** `commercial/`.
+- **One screen's spec.** That is a feature's `<feature>.md`, or a task's UI brief.
+
+## Rules
+
+<!-- A durable rule lives in the domain that owns its KIND of call. Shape:
+
+     ### <id> — the rule, in one line
+     enforced_by: the check that catches a violation — a command, a test, a lint
+
+     `enforced_by: judgement` is legal where a person really must decide, and is
+     counted separately rather than treated as enforcement. An empty one is a wish.
+
+     This section is EMPTY ON PURPOSE in a fresh repo. Do not seed it with invented
+     rules to make the domain look occupied — an empty domain is a signpost saying
+     where a call will go when you make one. -->

package/harness/assets/domains/legal.md

@@ -0,0 +1,43 @@
+---
+type: domain
+id: legal
+---
+
+# Legal — what binds us
+
+## What belongs here
+
+Durable calls about **obligation** — licensing of what we ship and what we depend
+on, attribution, terms and privacy commitments, regulatory constraints, and what a
+published artifact must and must not claim.
+
+Its neighbours: [`security/`](../security/README.md) owns technical safety — a
+credential rule is theirs, a data-retention *commitment* is this domain's.
+[`commercial/`](../commercial/README.md) owns the deal; this domain owns what
+agreeing to it binds us to.
+
+**Often empty in a young repo, and it ships anyway** — see the note in
+[`security/`](../security/README.md). The first rule that lands here is usually a
+dependency licence that turned out to constrain distribution, and it is much better
+found by a charter that already exists than by a lawyer.
+
+## Non-goals
+
+- **Technical safety measures.** `security/`.
+- **Pricing and packaging.** `commercial/`.
+- **How we run it.** `operations/`.
+- **One licence review.** That is work; the rule it establishes is durable.
+
+## Rules
+
+<!-- A durable rule lives in the domain that owns its KIND of call. Shape:
+
+     ### <id> — the rule, in one line
+     enforced_by: the check that catches a violation — a command, a test, a lint
+
+     `enforced_by: judgement` is legal where a person really must decide, and is
+     counted separately rather than treated as enforcement. An empty one is a wish.
+
+     This section is EMPTY ON PURPOSE in a fresh repo. Do not seed it with invented
+     rules to make the domain look occupied — an empty domain is a signpost saying
+     where a call will go when you make one. -->

package/harness/assets/domains/operations.md

@@ -0,0 +1,39 @@
+---
+type: domain
+id: operations
+---
+
+# Operations — how we ship it and run it
+
+## What belongs here
+
+Durable calls about **getting it out and keeping it running** — how something is
+published, how a consumer installs and updates, what a version means, how the
+release sequence works, and how the repo's own tooling runs.
+
+Its neighbours: [`security/`](../security/README.md) owns what must stay safe while
+we do it — a scan of a published artifact is a security rule, the publish path
+itself is this domain's. [`support/`](../support/README.md) owns keeping the *user*
+unblocked; this domain owns keeping the *system* shipping.
+[`architecture/`](../architecture/README.md) owns build-time structure.
+
+## Non-goals
+
+- **What the software does.** `product/`.
+- **How it is structured internally.** `architecture/`.
+- **Pricing and reach.** `commercial/`.
+- **One incident.** A postmortem is a document; the rule it produces belongs here.
+
+## Rules
+
+<!-- A durable rule lives in the domain that owns its KIND of call. Shape:
+
+     ### <id> — the rule, in one line
+     enforced_by: the check that catches a violation — a command, a test, a lint
+
+     `enforced_by: judgement` is legal where a person really must decide, and is
+     counted separately rather than treated as enforcement. An empty one is a wish.
+
+     This section is EMPTY ON PURPOSE in a fresh repo. Do not seed it with invented
+     rules to make the domain look occupied — an empty domain is a signpost saying
+     where a call will go when you make one. -->

package/harness/assets/domains/product.md

@@ -0,0 +1,43 @@
+---
+type: domain
+id: product
+---
+
+# Product — what it does
+
+## What belongs here
+
+Durable calls about **what the thing does** — the behaviour a user can rely on, and
+what the product *is*.
+
+This domain is the one that holds two kinds of file. The `<feature>.md` behaviour
+specs sit beside this charter and own stories, behaviour and `AC-nn`. This README
+also hosts `## Rules` like any other domain, because those are different facts: a
+feature spec says what the app does *today* and can be retired, while a product rule
+says what the product *is* and outlives any feature that expresses it.
+
+Its neighbours: [`design/`](../design/README.md) owns how it looks and reads —
+this domain owns what it must do. [`architecture/`](../architecture/README.md) owns
+how it is built. [`quality/`](../quality/README.md) owns how we know it works; a
+criterion's *text* is a feature's, the *standard of proof* is quality's.
+
+## Non-goals
+
+- **How it is built.** `architecture/`.
+- **How it looks.** `design/`.
+- **Whether it works.** `quality/` owns the standard of evidence; the `AC-nn` text stays in `<feature>.md`.
+- **Task-level scope.** A task brief is not durable direction.
+
+## Rules
+
+<!-- A durable rule lives in the domain that owns its KIND of call. Shape:
+
+     ### <id> — the rule, in one line
+     enforced_by: the check that catches a violation — a command, a test, a lint
+
+     `enforced_by: judgement` is legal where a person really must decide, and is
+     counted separately rather than treated as enforcement. An empty one is a wish.
+
+     This section is EMPTY ON PURPOSE in a fresh repo. Do not seed it with invented
+     rules to make the domain look occupied — an empty domain is a signpost saying
+     where a call will go when you make one. -->

package/harness/assets/domains/quality.md

@@ -0,0 +1,43 @@
+---
+type: domain
+id: quality
+---
+
+# Quality — how we know it is good
+
+## What belongs here
+
+Durable calls about **evidence** — what counts as proof that something works, how a
+test binds to the criterion it proves, what the levels of proof are, and what makes
+a green run trustworthy.
+
+The distinction that earns this domain its own home: *what the app should do* is
+product's, *whether it does* is this domain's. A rule that says "a criterion is
+proven by a tag-bound passing test, never by a comment" is not a build rule and not
+a behaviour spec — and before the domains split, it had nowhere to live.
+
+Its neighbours: [`architecture/`](../architecture/README.md) owns how code is
+built; this domain owns how we know the result is right.
+[`product/`](../product/README.md) owns the `AC-nn` text this domain sets the
+standard of proof for.
+
+## Non-goals
+
+- **The behaviour being proven.** `product/`.
+- **How the code is structured.** `architecture/`.
+- **Whether the deploy succeeded.** `operations/`.
+- **A single test's assertions.** Code, not governance.
+
+## Rules
+
+<!-- A durable rule lives in the domain that owns its KIND of call. Shape:
+
+     ### <id> — the rule, in one line
+     enforced_by: the check that catches a violation — a command, a test, a lint
+
+     `enforced_by: judgement` is legal where a person really must decide, and is
+     counted separately rather than treated as enforcement. An empty one is a wish.
+
+     This section is EMPTY ON PURPOSE in a fresh repo. Do not seed it with invented
+     rules to make the domain look occupied — an empty domain is a signpost saying
+     where a call will go when you make one. -->

package/harness/assets/domains/security.md

@@ -0,0 +1,44 @@
+---
+type: domain
+id: security
+---
+
+# Security — what keeps it safe
+
+## What belongs here
+
+Durable calls about **what must stay safe** — secrets and how they are held,
+authentication and authorization boundaries, what untrusted input is and where it is
+trusted, data handling, and what must never enter a published artifact.
+
+Its neighbours: [`operations/`](../operations/README.md) owns the publish path and
+keeping the system running — this domain owns what must remain true while it does.
+[`legal/`](../legal/README.md) owns what binds us contractually; a rule about
+technical safety is this domain's, one about obligation is theirs.
+[`architecture/`](../architecture/README.md) owns the seams; where a seam exists
+*because* of a trust boundary, cite this domain's rule from it.
+
+**This domain is often empty in a young repo, and that is fine.** It ships anyway,
+because the cost of an empty charter is one file and the cost of a missing domain is
+a security rule mis-filed under whichever system happened to be nearby.
+
+## Non-goals
+
+- **How it is deployed.** `operations/`.
+- **Contractual and regulatory obligation.** `legal/`.
+- **Whether the feature works.** `quality/`.
+- **A specific vulnerability.** That is a task, not a durable rule — though the rule that prevents its class belongs here.
+
+## Rules
+
+<!-- A durable rule lives in the domain that owns its KIND of call. Shape:
+
+     ### <id> — the rule, in one line
+     enforced_by: the check that catches a violation — a command, a test, a lint
+
+     `enforced_by: judgement` is legal where a person really must decide, and is
+     counted separately rather than treated as enforcement. An empty one is a wish.
+
+     This section is EMPTY ON PURPOSE in a fresh repo. Do not seed it with invented
+     rules to make the domain look occupied — an empty domain is a signpost saying
+     where a call will go when you make one. -->