@forwardimpact/outpost 3.12.0 → 3.13.0

package/src/outpost.js

@@ -7,14 +7,15 @@
 //   fit-outpost init [name]         Initialize a knowledge base by name (default: Team)
 //   fit-outpost update [path]       Update KB with latest CLAUDE.md, agents and skills (defaults to current directory)
 //   fit-outpost stop                Gracefully stop daemon and all running agents
-//   fit-outpost validate            Validate agent definitions exist
+//   fit-outpost validate [path]     Validate agent definitions and knowledge bases
 //   fit-outpost status              Show agent status
 //   fit-outpost --help              Show this help
 //
-// This module owns the CLI definition and dispatch table. The runtime
-// collaborator bag is constructed once in bin/fit-outpost.js (the sole
-// construction site) and threaded into `run(runtime, version)`; `run` returns
-// the process exit code and the bin translates it to `runtime.proc.exit`.
+// This module owns the CLI definition and dispatch table. bin/fit-outpost.js
+// constructs the runtime collaborator bag once. That file is the sole
+// construction site. It threads the bag into `run(runtime, version)`. `run`
+// returns the process exit code. The bin translates that code to
+// `runtime.proc.exit`.
 
 import { join, dirname, resolve } from "node:path";
 import { homedir } from "node:os";
@@ -26,6 +27,7 @@ import { StateManager } from "./state-manager.js";
 import { AgentRunner } from "./agent-runner.js";
 import { Scheduler, formatLocalTime } from "./scheduler.js";
 import { KBManager } from "./kb-manager.js";
+import { validateKnowledgeBase } from "./kb-validator.js";
 import { SocketServer, requestShutdown, requestWake } from "./socket-server.js";
 import {
   readPosture,
@@ -38,13 +40,13 @@ import {
 const SHARE_DIR = "/usr/local/share/fit-outpost";
 
 /**
- * Build the CLI definition. The object is byte-identical to the libcli
- * definition the goldens were captured against, so `--help` / `--version`
- * output stays stable.
+ * Build the CLI definition. This object is byte-identical to the libcli
+ * definition that the golden capture used, and `test/golden.test.js`
+ * enforces that contract. So `--help` and `--version` output stays stable.
  * @param {string} version
  * @returns {object}
  */
-function buildDefinition(version) {
+export function buildDefinition(version) {
   return {
     name: "fit-outpost",
     version,
@@ -71,7 +73,11 @@ function buildDefinition(version) {
         name: "stop",
         description: "Gracefully stop daemon and all running agents",
       },
-      { name: "validate", description: "Validate agent definitions exist" },
+      {
+        name: "validate",
+        args: "[path]",
+        description: "Validate agent definitions and knowledge bases",
+      },
       { name: "status", description: "Show agent status" },
       {
         name: "posture",
@@ -82,7 +88,10 @@ function buildDefinition(version) {
     globalOptions: {
       help: { type: "boolean", short: "h", description: "Show this help" },
       version: { type: "boolean", description: "Show version" },
-      json: { type: "boolean", description: "JSON output (with --help)" },
+      json: {
+        type: "boolean",
+        description: "JSON output (with --help and validate)",
+      },
     },
     documentation: [
       {
@@ -111,7 +120,7 @@ function buildDefinition(version) {
 }
 
 /**
- * Render an agent's multi-line status block (pure formatting).
+ * Render an agent's multi-line status block. This is a pure format step.
  * @param {string} name
  * @param {Object} agent
  * @param {Object} s - The agent's persisted state.
@@ -145,7 +154,8 @@ export async function run(runtime, version) {
   const logger = createLogger("outpost", runtime);
 
   /**
-   * Async existence check via the one fs surface this module uses.
+   * Test whether a path exists, through the one async fs surface this module
+   * uses.
    * @param {string} p
    * @returns {Promise<boolean>}
    */
@@ -193,10 +203,10 @@ export async function run(runtime, version) {
   }
 
   // --- Wire dependencies -----------------------------------------------------
-  // posix-spawn is a Bun-FFI module (`bun:ffi`); importing it eagerly would
-  // crash plain `node` (e.g. `--help`/`--version`/golden capture). Load it
-  // lazily so only an actual agent wake — which only runs under Bun on macOS —
-  // pulls it in.
+  // posix-spawn is a Bun-FFI module (`bun:ffi`). An eager import would crash
+  // plain `node` (e.g. `--help`/`--version`/golden capture). So load it
+  // lazily. Then only an actual agent wake pulls it in. That wake only runs
+  // under Bun on macOS.
   const loadSpawn = () => import("@forwardimpact/libmacos/posix-spawn");
   const stateManager = new StateManager(STATE_PATH, runtime);
   const agentRunner = new AgentRunner(
@@ -247,7 +257,7 @@ export async function run(runtime, version) {
   // --- Daemon ----------------------------------------------------------------
   async function daemon() {
     const daemonStartedAt = clock.now();
-    log("Scheduler daemon started. Polling every 60 seconds.");
+    log("Scheduler daemon started. It polls every 60 seconds.");
     log(`Config: ${CONFIG_PATH}  State: ${STATE_PATH}`);
 
     // Reset any agents left "active" from a previous daemon session.
@@ -276,8 +286,8 @@ export async function run(runtime, version) {
     void socketServer.whenStopped().then(() => {
       stopped = true;
       // Cancel any pending poll so the armed timer does not keep the event
-      // loop alive after shutdown — `run()` returns 0 and the bin exits only
-      // on a nonzero code, so a lingering 60s timer would delay exit.
+      // loop alive after shutdown. `run()` returns 0, and the bin exits only
+      // on a nonzero code. So a 60s timer that stays armed would delay exit.
       if (tickHandle !== undefined) clock.clearTimeout(tickHandle);
     });
 
@@ -292,8 +302,8 @@ export async function run(runtime, version) {
     }
     void tick();
 
-    // Block until a shutdown is requested via socket or signal; the bin then
-    // owns the process-exit call.
+    // Block until a socket or a signal requests a shutdown. The bin then owns
+    // the process-exit call.
     await socketServer.whenStopped();
     return 0;
   }
@@ -323,9 +333,9 @@ export async function run(runtime, version) {
     const state = await stateManager.load();
     const posture = await readPosture(fs, POSTURE_PATH);
     logger.info("\nOutpost Scheduler\n==================\n");
-    // The posture must be observable on a line matching
-    // `^posture: (brief|brief+draft|unset)$`, so write it as plain text to
-    // stdout rather than through the RFC5424-prefixed logger.
+    // The posture must be observable on a line that matches
+    // `^posture: (brief|brief+draft|unset)$`. So write it as plain text to
+    // stdout. Do not write it through the RFC5424-prefixed logger.
     proc.stdout.write(`posture: ${posture ?? "unset"}\n`);
 
     const agents = Object.entries(config.agents || {});
@@ -373,7 +383,59 @@ export async function run(runtime, version) {
     return !!found;
   }
 
+  /**
+   * Render one knowledge finding as a report line. Baselined findings warn.
+   * @param {import("./kb-validator.js").Finding} f
+   * @returns {string}
+   */
+  function formatFinding(f) {
+    const prefix = f.baselined ? "warn: " : "";
+    if (f.path !== undefined) {
+      return `${prefix}${f.path} ${f.kind}${f.message ? ` — ${f.message}` : ""}`;
+    }
+    return `${prefix}${f.file}:${f.line} ${f.kind} ${f.link ?? f.property}`;
+  }
+
+  /**
+   * Render one KB root's findings as report lines through the logger.
+   * @param {string} root - Absolute KB root path.
+   * @param {import("./kb-validator.js").Finding[]} findings
+   * @returns {void}
+   */
+  function reportFindings(root, findings) {
+    logger.info(`\nKnowledge base: ${root}`);
+    for (const f of findings) logger.info(`  ${formatFinding(f)}`);
+    if (findings.length === 0) logger.info("  OK");
+  }
+
+  /**
+   * Run the knowledge checks over each KB root. With `--json` the merged
+   * findings array is the only stdout, so tooling can parse it. A root the
+   * validator cannot read (a mistyped path, a malformed registry or
+   * baseline) fails with one clean error line instead of a stack trace.
+   * @param {string[]} roots - Absolute KB root paths.
+   * @returns {Promise<number>} 1 when any finding is not baselined, else 0.
+   */
+  async function runKnowledgeChecks(roots) {
+    const all = [];
+    for (const root of roots) {
+      let result;
+      try {
+        result = await validateKnowledgeBase(root, runtime);
+      } catch (err) {
+        cli.error(`validate failed for ${root}: ${err.message}`);
+        return 1;
+      }
+      if (!values.json) reportFindings(root, result.findings);
+      all.push(...result.findings);
+    }
+    if (values.json) proc.stdout.write(`${JSON.stringify(all)}\n`);
+    return all.some((f) => !f.baselined) ? 1 : 0;
+  }
+
   async function validate() {
+    if (args[0]) return runKnowledgeChecks([expandPath(args[0])]);
+
     const config = await loadConfig();
     const agents = Object.entries(config.agents || {});
     if (agents.length === 0) {
@@ -389,7 +451,12 @@ export async function run(runtime, version) {
     }
 
     logger.info(errors > 0 ? `\n${errors} error(s).` : "\nAll OK.");
-    return errors > 0 ? 1 : 0;
+    // The logger writes to stderr, so with --json the findings array stays
+    // the only stdout even on the no-path form.
+    const kbRoots = [
+      ...new Set(agents.map(([, a]) => a.kb).filter(Boolean)),
+    ].map(expandPath);
+    return Math.max(errors ? 1 : 0, await runKnowledgeChecks(kbRoots));
   }
 
   // --- CLI entry point -------------------------------------------------------
@@ -397,7 +464,7 @@ export async function run(runtime, version) {
   const parsed = cli.parse(proc.argv.slice(2));
   if (!parsed) return 0;
 
-  const { positionals } = parsed;
+  const { positionals, values } = parsed;
   const [command, ...args] = positionals;
 
   await fs.mkdir(OUTPOST_HOME, { recursive: true });
@@ -409,13 +476,14 @@ export async function run(runtime, version) {
         cli.usageError("missing required argument <agent>");
         return 2;
       }
-      // Always route the wake through the running daemon. The daemon is the
-      // only spawn site that descends from fit-outpost.app, so a `claude`
-      // spawned there inherits the app as its TCC responsible process and a
-      // single grant to the app covers it. Spawning from this CLI process
-      // would attribute the access to the terminal instead, breaking the
-      // single-grant model. If no daemon is running there is nowhere to wake
-      // with correct attribution, so this errors rather than spawning locally.
+      // Always route the wake through the daemon that already runs. The daemon
+      // is the only spawn site that descends from fit-outpost.app. So a
+      // `claude` spawned there inherits the app as its TCC responsible
+      // process, and a single grant to the app covers it. A spawn from this
+      // CLI process would attribute the access to the terminal instead. That
+      // breaks the single-grant model. When no daemon runs, there is nowhere
+      // to wake with correct attribution. So this command errors. It does not
+      // spawn locally.
       const result = await requestWake(SOCKET_PATH, args[0], runtime);
       if (result.ok) {
         log(`Wake dispatched to daemon for "${args[0]}".`);
@@ -423,7 +491,7 @@ export async function run(runtime, version) {
       }
       if (result.reason === "not-running") {
         cli.error(
-          "daemon not running. Start fit-outpost.app (or run `fit-outpost daemon`) before waking an agent.",
+          "daemon not running. Start fit-outpost.app (or run `fit-outpost daemon`) before you wake an agent.",
         );
       } else if (result.reason === "timeout") {
         cli.error("daemon did not respond to the wake request.");
@@ -434,8 +502,9 @@ export async function run(runtime, version) {
     },
     init: async () => {
       // `init [name]` provisions a KB by name under the data home (default
-      // `Team`), never an arbitrary path — so the substrate cannot be
-      // steered back into a TCC-protected folder. An unsafe name is refused.
+      // `Team`). It never accepts an arbitrary path. So nobody can steer the
+      // substrate back into a TCC-protected folder. This command refuses an
+      // unsafe name.
       const name = args[0] ?? "Team";
       let target;
       try {
@@ -452,8 +521,8 @@ export async function run(runtime, version) {
         return result.code;
       }
       // A fresh init defaults the posture to `brief`, the opted-into trust
-      // contract. Only write when none is recorded so re-running never flips
-      // an existing posture.
+      // contract. Only write when no posture is recorded. A later run then
+      // never flips an existing posture.
       if ((await readPosture(fs, POSTURE_PATH)) === null) {
         await writePosture(fs, POSTURE_PATH, "brief");
       }

package/src/posture.js

@@ -2,7 +2,7 @@
  * Posture — read/write the adoption-posture record and resolve the
  * draft-side deny set from the skill-posture manifest.
  *
- * The two committed posture strings are the only valid values; they appear
+ * The two committed posture strings are the only valid values. They appear
  * verbatim in CLI flags, `status` output, and landing-page copy.
  */
 
@@ -46,8 +46,8 @@ export async function writePosture(fs, posturePath, value) {
 }
 
 /**
- * Resolve the effective posture, applying the default when no posture has been
- * recorded so a posture-less install behaves as `brief`.
+ * Resolve the effective posture. Apply the default when no posture is
+ * recorded. A posture-less install then behaves as `brief`.
  * @param {"brief"|"brief+draft"|null} stored
  * @returns {"brief"|"brief+draft"}
  */

package/src/privilege.js

@@ -3,23 +3,23 @@
  * the hop-2 spawn disclaim flag.
  *
  * The level governs the macOS reach the daemon grants a woken agent. `full`
- * keeps today's single-grant model (the child inherits `fit-outpost.app` as its
- * responsible process, so Full Disk Access and Automation flow to it); a
- * `restricted` agent is held responsible for itself, so those grants are not
- * extended and it can reach only non-TCC-protected substrate.
+ * keeps today's single-grant model. The child inherits `fit-outpost.app` as its
+ * responsible process, so Full Disk Access and Automation flow to it. A
+ * `restricted` agent is responsible for itself. Those grants do not extend to
+ * it, so it can reach only non-TCC-protected substrate.
  *
- * The level is mandatory and lives in the same user-only trust root as the
- * spawn-env allow-set and the state roots, so an agent cannot raise its own
- * level. Patterned on `posture.js` but with no `effective*` coercion and no
- * default — a missing or unrecognised value throws.
+ * The level is mandatory. It lives in the same user-only trust root as the
+ * spawn-env allow-set and the state roots. So an agent cannot raise its own
+ * level. This module follows the `posture.js` pattern, with no `effective*`
+ * coercion and no default. A missing or unrecognised value throws.
  */
 
 /** The two privilege levels, in declaration order. */
 export const PRIVILEGE_LEVELS = ["full", "restricted"];
 
 /**
- * Resolve an agent's declared privilege level. The level is mandatory: a
- * missing or unrecognised value throws — there is no default.
+ * Resolve an agent's declared privilege level. The level is mandatory. A
+ * missing or unrecognised value throws. There is no default.
  * @param {{ privilege?: string }} agent - One agent's config.
  * @returns {"full"|"restricted"} The declared level.
  * @throws {Error} when `agent.privilege` is not one of {@link PRIVILEGE_LEVELS}.
@@ -35,7 +35,7 @@ export function resolvePrivilege(agent) {
 }
 
 /**
- * Map a level to the hop-2 disclaim flag: `restricted` self-disclaims (`1`),
+ * Map a level to the hop-2 disclaim flag. `restricted` self-disclaims (`1`).
  * `full` keeps the inherited responsible process (`0`).
  * @param {"full"|"restricted"} level
  * @returns {0|1}

package/src/scheduler.js

@@ -3,23 +3,24 @@
  *
  * The genuine wall-clock read ("what time is it now?") routes through the
  * injected `runtime.clock` (see `Scheduler#wakeDueAgents` and `failAgent`).
- * The pure cron helpers below receive that `now` as an explicit `Date` and
+ * The pure cron helpers below receive that `now` as an explicit `Date`. They
  * construct further `Date` objects only for deterministic date *arithmetic*
  * over caller-supplied or parsed-from-state inputs (never an ambient no-arg
- * `new Date()`); the AST checker cannot distinguish the two, so this file is
- * allow-listed in .coaligned/invariants/ambient-deps.allow.yml with that reason.
+ * `new Date()`). The AST checker cannot distinguish the two, so
+ * .jidoka/invariants/ambient-deps.allow.yml allow-lists this file with that
+ * reason.
  */
 
 import { isoTimestamp } from "@forwardimpact/libutil";
 
-/** Maximum time an agent can be "active" before being considered stale (35 min). */
+/** Maximum time an agent can be "active" before it becomes stale (35 min). */
 const MAX_AGENT_RUNTIME_MS = 35 * 60_000;
 
 /**
  * Build a `Date` for "now" from the injected clock's milliseconds. The cron
- * helpers operate on `Date` objects; this is the single seam that turns the
- * wall-clock read (`runtime.clock.now()`) into one, so callers in other
- * modules never construct an ambient `new Date()` themselves.
+ * helpers operate on `Date` objects. This function is the single seam that
+ * turns the wall-clock read (`runtime.clock.now()`) into one. So callers in
+ * other modules never construct an ambient `new Date()` themselves.
  * @param {{now: () => number}} clock
  * @returns {Date}
  */
@@ -28,9 +29,9 @@ export function nowFromClock(clock) {
 }
 
 /**
- * Format a stored ISO timestamp as a human-readable local time string. Parses
- * an explicit value (never the wall clock); lives here so the only `new Date`
- * construction sites stay in this allow-listed module.
+ * Format a stored ISO timestamp as a human-readable local time string. This
+ * function parses an explicit value (never the wall clock). It lives here so
+ * the only `new Date` construction sites stay in this allow-listed module.
  * @param {string} iso
  * @returns {string}
  */
@@ -179,7 +180,7 @@ export function failAgent(agentState, error, nowMs) {
 
 // --- Scheduler class ---------------------------------------------------------
 
-/** Orchestrate periodic agent wakes by evaluating schedules and delegating to AgentRunner. */
+/** Orchestrate periodic agent wakes. Evaluate schedules and delegate to AgentRunner. */
 export class Scheduler {
   #loadConfig;
   #stateManager;
@@ -209,7 +210,8 @@ export class Scheduler {
   }
 
   /**
-   * Reset any agents exceeding max runtime, reload config, then wake each agent whose schedule is due.
+   * Reset any agent that exceeds the maximum runtime. Reload the config. Then
+   * wake each agent whose schedule is due.
    */
   async wakeDueAgents() {
     const config = await this.#loadConfig();

package/src/socket-server.js

@@ -75,8 +75,9 @@ export class SocketServer {
   }
 
   /**
-   * Resolves once a shutdown has been requested (via socket or signal). The
-   * daemon awaits this, then the bin translates it to `runtime.proc.exit(0)`.
+   * The returned promise resolves once the daemon receives a shutdown request
+   * through the socket or a signal. The daemon awaits this. Then the bin
+   * translates it to `runtime.proc.exit(0)`.
    * @returns {Promise<void>}
    */
   whenStopped() {
@@ -102,7 +103,7 @@ export class SocketServer {
   }
 
   /**
-   * Find the most recently modified file in a directory matching a filter.
+   * Find the most recently modified file in `dir` whose name passes `filter`.
    * @param {string} dir
    * @param {(name: string) => boolean} filter
    * @returns {string|null}
@@ -124,7 +125,7 @@ export class SocketServer {
   }
 
   /**
-   * Resolve briefing file for an agent
+   * Resolve the briefing file for an agent
    * @param {string} agentName
    * @param {Object} agentConfig
    * @returns {string|null}
@@ -218,7 +219,7 @@ export class SocketServer {
     if (request.type === "status") return this.#handleStatusRequest(socket);
 
     if (request.type === "shutdown") {
-      this.#log("Shutdown requested via socket.");
+      this.#log("Shutdown requested through the socket.");
       this.#send(socket, { type: "ack", command: "shutdown" });
       socket.end();
       this.#requestShutdown();
@@ -258,9 +259,9 @@ export class SocketServer {
   }
 
   /**
-   * Tear down active children and the listening socket, then signal the daemon
-   * (via `whenStopped`) that it is safe to exit. The bin owns the actual
-   * `runtime.proc.exit` call (design Decision 4).
+   * Tear down active children and the socket that listens. Then signal the
+   * daemon through `whenStopped` that it is safe to exit. The bin owns the
+   * actual `runtime.proc.exit` call (design Decision 4).
    */
   #requestShutdown() {
     this.#agentRunner.killActiveChildren();
@@ -272,7 +273,7 @@ export class SocketServer {
   }
 
   /**
-   * Remove any existing socket file, bind the server, and register
+   * Remove any existing socket file. Bind the server. Register
    * SIGTERM/SIGINT handlers that request a graceful shutdown.
    * @returns {import('node:net').Server}
    */
@@ -324,15 +325,15 @@ export class SocketServer {
 }
 
 /**
- * Connect to the running daemon and ask it to wake an agent.
+ * Connect to the daemon that already runs and ask it to wake an agent.
  *
- * The wake runs inside the daemon process, which is the only spawn site that
- * descends from fit-outpost.app — so the spawned `claude` inherits the app as
- * its TCC responsible process. Routing every wake through the daemon is what
- * keeps the single-grant model intact; a wake spawned from this CLI process
- * would be attributed to the terminal instead. The daemon acknowledges
- * (`ack`) once it has accepted the request and then runs the wake
- * asynchronously, so this resolves on the ack rather than on completion.
+ * The wake runs inside the daemon process. That process is the only spawn site
+ * that descends from fit-outpost.app. So the spawned `claude` inherits the app
+ * as its TCC responsible process. Every wake routes through the daemon to keep
+ * the single-grant model intact. macOS would attribute a wake spawned from
+ * this CLI process to the terminal instead. The daemon acknowledges (`ack`)
+ * once it accepts the request. It then runs the wake asynchronously. So this
+ * function resolves on the ack. It does not wait for the wake to finish.
  *
  * @param {string} socketPath
  * @param {string} agent - Agent name to wake.
@@ -379,7 +380,7 @@ export async function requestWake(socketPath, agent, runtime) {
       }
     });
 
-    // A stale socket file (daemon crashed) refuses the connection; treat it
+    // A stale socket file (daemon crashed) refuses the connection. Treat it
     // the same as a missing daemon.
     socket.on("error", () => {
       runtime.clock.clearTimeout(timeout);

package/src/spawn-env.js

@@ -3,16 +3,16 @@
  *
  * The daemon-mediated wake paths forward `config.env` from
  * `~/.fit/outpost/scheduler.json` into spawned `claude` processes. This module
- * is the single trust contract that decides which keys are honored.
+ * is the single trust contract that decides which keys the daemon honors.
  */
 
 import { homedir } from "node:os";
 import { join } from "node:path";
 
 /**
- * Build a Set whose mutators are neutralised. `Object.freeze` alone does not
- * stop `Set.prototype.add`/`delete`/`clear` from mutating internal state, so
- * the allow-set is only a durable trust contract if the mutators themselves
+ * Build a Set with neutralised mutators. `Object.freeze` alone does not stop
+ * `Set.prototype.add`/`delete`/`clear`. They still mutate internal state. So
+ * the allow-set is a durable trust contract only when the mutators themselves
  * throw.
  * @param {string[]} keys
  * @returns {ReadonlySet<string>}
@@ -38,8 +38,9 @@ export const AGENT_ENV_ALLOWSET = frozenSet(["ANTHROPIC_API_KEY"]);
 
 /**
  * Build the spawn environment from a base env plus allow-set members of
- * `configEnv`. Keys outside the allow-set are dropped and returned in
- * `rejections`. Tilde-prefixed values are home-expanded. Pure; the caller logs.
+ * `configEnv`. This function drops keys outside the allow-set and returns them
+ * in `rejections`. It expands tilde-prefixed values to the home directory. It
+ * is pure, so the caller logs.
  * @param {Record<string,string>=} configEnv
  * @param {NodeJS.ProcessEnv} baseEnv
  * @returns {{ env: Record<string,string>, rejections: string[] }}

package/src/state-manager.js

@@ -27,8 +27,8 @@ export class StateManager {
   }
 
   /**
-   * Read and parse state from disk; on any read or parse error, write a fresh
-   * empty state and return it.
+   * Read and parse the state from disk. On any read or parse error, write a
+   * fresh empty state and return it.
    * @returns {Promise<Object>}
    */
   async load() {

package/templates/.claude/agents/chief-of-staff.md

@@ -3,34 +3,41 @@ name: chief-of-staff
 description: >
   The user's executive assistant. Creates daily briefings that synthesize
   email, calendar, and knowledge graph state into actionable priorities.
-  Woken at key moments (morning, evening) by the Outpost scheduler.
+  The Outpost scheduler wakes it at key moments (morning, evening).
 model: sonnet
 permissionMode: bypassPermissions
 ---
 
-You are the chief of staff — the user's executive assistant. Each wake:
-synthesize what matters across email, calendar, and the knowledge graph into a
-single briefing.
+You are the chief of staff. You are the user's executive assistant. On each
+wake, synthesize what matters across email, calendar, and the knowledge graph
+into a single briefing.
+
+## Tiers
+
+Read: every tier present
+Write: none (the output is personal `Briefings/`)
+Stamp the frontmatter standard per CLAUDE.md on every note you write.
+Aggregate outputs over narrower-tier sources go to `0-Draft/`.
 
 ## Priorities
 
-`Knowledge/Priorities/` is the backbone of every briefing. Read it and
-`Knowledge/Conditions/` (the live constraints that shape how priorities are
-pursued — see Operating Context in CLAUDE.md) each wake (both are also listed
-under Inputs) and frame the whole briefing around what advances or threatens the
-user's priorities.
+`Priorities/` notes in every tier present are the backbone of every briefing.
+Read them and `Conditions/` on each wake. Conditions hold the live
+constraints that shape how you pursue the priorities. See Operating Context in
+CLAUDE.md. The Inputs section below also lists both folders. Frame the whole
+briefing around what advances or threatens the user's priorities.
 
 - **Always consider them.** Tie the schedule, the top actions, and the pipeline
   back to the priority each one serves.
 - **Always escalate risks.** Consolidate every `## Priority Watch` flag from the
-  sibling triage files — plus anything you find in your own reads — into a
-  `## Priority Watch` section in the briefing, each item naming the priority,
-  the evidence, and the risk. A signal that could contradict, block, or slow a
+  sibling triage files into a `## Priority Watch` section in the briefing. Add
+  anything you find in your own reads. Each item names the priority, the
+  evidence, and the risk. A signal that could contradict, block, or slow a
   priority is the most important thing the briefing surfaces.
 
 ## Inputs
 
-Read all five sibling agents' triage files before writing — these are the
+Read all five sibling agents' triage files before you write. These files are the
 authoritative current-state summaries:
 
 - `~/.cache/fit/outpost/state/postman_triage.md`
@@ -39,9 +46,9 @@ authoritative current-state summaries:
 - `~/.cache/fit/outpost/state/recruiter_triage.md`
 - `~/.cache/fit/outpost/state/head_hunter_triage.md`
 
-Plus directly: `Knowledge/Priorities/`, `Knowledge/Conditions/`, `Drafts/`,
-`~/.cache/fit/outpost/apple_calendar/`, and unchecked `- [ ]` items in
-`Knowledge/`.
+Also read these directly: `Priorities/` and `Conditions/` in every tier,
+`0-Draft/`, `~/.cache/fit/outpost/apple_calendar/`, and unchecked `- [ ]`
+items across the tiers.
 
 ## Routing
 
@@ -51,17 +58,18 @@ Plus directly: `Knowledge/Priorities/`, `Knowledge/Conditions/`, `Drafts/`,
 | Noon or later  | `Briefings/{YYYY-MM-DD}-evening.md`      |
 
 A briefing covers: today's schedule with prep status, top three priority actions
-linked to `[[Priorities/...]]`, priority progress, a **Priority Watch** section
-consolidating priority risks flagged by the agents, inbox snapshot (urgent /
-awaiting reply), open commitments, recruitment pipeline summary, and a heads-up
-section. Evening briefings replace "Priority Actions" with "What Happened Today"
-and "Still Outstanding".
+linked with tier-prefixed links (`[[3-Team/Priorities/...]]`), priority
+progress, a **Priority Watch** section
+that consolidates the priority risks the agents flagged, inbox snapshot
+(urgent / awaiting reply), open commitments, recruitment pipeline summary, and a
+heads-up section. Evening briefings replace "Priority Actions" with "What
+Happened Today" and "Still Outstanding".
 
 ## Scope
 
-- This agent **synthesizes** — never duplicate work the other agents have
-  already triaged. Cite their findings, don't re-derive them.
-- Do not act on email, candidates, or transcripts directly — those belong to the
+- This agent **synthesizes**. Never duplicate work the other agents already
+  triaged. Cite their findings. Do not re-derive them.
+- Do not act on email, candidates, or transcripts directly. Those belong to the
   postman, recruiter, and concierge.
 
 ## Output