@forwardimpact/outpost 3.8.0 → 3.9.0

package/config/scheduler.json

@@ -1,32 +1,38 @@
 {
   "agents": {
     "postman": {
-      "kb": "~/Documents/Personal",
+      "kb": "~/.local/share/fit/outpost/Team",
+      "privilege": "full",
       "schedule": { "type": "cron", "expression": "*/15 8-18 * * 1-5" },
       "enabled": true
     },
     "concierge": {
-      "kb": "~/Documents/Personal",
+      "kb": "~/.local/share/fit/outpost/Team",
+      "privilege": "full",
       "schedule": { "type": "cron", "expression": "*/30 8-18 * * 1-5" },
       "enabled": true
     },
     "librarian": {
-      "kb": "~/Documents/Personal",
+      "kb": "~/.local/share/fit/outpost/Team",
+      "privilege": "restricted",
       "schedule": { "type": "cron", "expression": "0 9,12,15,18 * * 1-5" },
       "enabled": true
     },
     "chief-of-staff": {
-      "kb": "~/Documents/Personal",
+      "kb": "~/.local/share/fit/outpost/Team",
+      "privilege": "restricted",
       "schedule": { "type": "cron", "expression": "0 7,18 * * 1-5" },
       "enabled": true
     },
     "recruiter": {
-      "kb": "~/Documents/Personal",
+      "kb": "~/.local/share/fit/outpost/Team",
+      "privilege": "restricted",
       "schedule": { "type": "cron", "expression": "0 8,12,17 * * 1-5" },
       "enabled": true
     },
     "head-hunter": {
-      "kb": "~/Documents/Personal",
+      "kb": "~/.local/share/fit/outpost/Team",
+      "privilege": "restricted",
       "schedule": { "type": "cron", "expression": "0 9 * * 1-5" },
       "enabled": true
     }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@forwardimpact/outpost",
-  "version": "3.8.0",
+  "version": "3.9.0",
   "description": "Personal operations center — context from email, calendar, and knowledge assembled so preparation is continuous, not a morning scramble.",
   "homepage": "https://www.forwardimpact.team",
   "repository": {

package/src/agent-runner.js

@@ -11,6 +11,7 @@ import {
   loadManifest,
   draftSkills,
 } from "./posture.js";
+import { resolvePrivilege, disclaimFor } from "./privilege.js";
 import { buildSpawnEnv } from "./spawn-env.js";
 
 /**
@@ -176,6 +177,24 @@ export class AgentRunner {
    * @param {Record<string, string>} [configEnv] - Extra env vars from config
    */
   async wake(agentName, agent, state, configEnv) {
+    // Resolve the mandatory privilege level before any work. A missing or
+    // invalid level is fail-closed: log and skip the wake — no agent process is
+    // spawned with a guessed privilege. The level lives in the user-only trust
+    // root, so a spawned agent cannot raise its own.
+    let level;
+    try {
+      level = resolvePrivilege(agent);
+    } catch (err) {
+      this.#log(
+        JSON.stringify({
+          event: "outpost.privilege.rejected",
+          agent: agentName,
+          error: err.message,
+        }),
+      );
+      return;
+    }
+
     if (!agent.kb) {
       this.#log(`Agent ${agentName}: no "kb" specified, skipping.`);
       return;
@@ -191,6 +210,13 @@ export class AgentRunner {
     const claude = await this.#findClaude();
 
     this.#log(`Waking agent: ${agentName} (kb: ${agent.kb})`);
+    this.#log(
+      JSON.stringify({
+        event: "outpost.privilege.resolved",
+        agent: agentName,
+        level,
+      }),
+    );
 
     const as = (state.agents[agentName] ||= {});
     as.status = "active";
@@ -226,6 +252,7 @@ export class AgentRunner {
         env,
         kbPath,
         this.#runtime,
+        disclaimFor(level),
       );
       this.#activeChildren.add(pid);
 

package/src/kb-manager.js

@@ -23,6 +23,33 @@ export class KBManager {
     this.#logger = createLogger("outpost", runtime);
   }
 
+  /**
+   * Resolve a knowledge-base name to its path under the XDG data home,
+   * `~/.local/share/fit/outpost/<name>`. The argument is a single path segment,
+   * never an arbitrary filesystem path, so a provisioned KB always lands outside
+   * TCC-protected folders. The name is validated — not sanitised — against the
+   * same rule as `agent-path.js`: a name carrying `/`, `\`, `..`, NUL, or a
+   * leading `~` could steer the KB back inside `~/Documents`, reopening the TCC
+   * hole, so it is rejected rather than rewritten.
+   * @param {string} name - The KB name (e.g. `Team`, `personal`).
+   * @returns {string} Absolute path under the data home.
+   * @throws {Error} when `name` is empty, non-string, or an unsafe segment.
+   */
+  static kbPathForName(name) {
+    if (
+      typeof name !== "string" ||
+      name.length === 0 ||
+      name.includes("/") ||
+      name.includes("\\") ||
+      name.includes("..") ||
+      name.includes("\0") ||
+      name.startsWith("~")
+    ) {
+      throw new Error(`unsafe KB name: ${JSON.stringify(name)}`);
+    }
+    return join(homedir(), ".local/share/fit/outpost", name);
+  }
+
   /**
    * Test whether a path exists, via the async fs surface.
    * @param {string} p

package/src/outpost.js

@@ -4,7 +4,7 @@
 //   fit-outpost                     Wake due agents once and exit
 //   fit-outpost daemon              Run continuously (poll every 60s)
 //   fit-outpost wake <agent>        Wake a specific agent immediately
-//   fit-outpost init <path>         Initialize a new knowledge base
+//   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
@@ -58,7 +58,7 @@ function buildDefinition(version) {
       },
       {
         name: "init",
-        args: "<path>",
+        args: "[name]",
         description: "Initialize a new knowledge base",
       },
       {
@@ -433,13 +433,20 @@ export async function run(runtime, version) {
       return 1;
     },
     init: async () => {
-      if (!args[0]) {
-        cli.usageError("missing required argument <path>");
+      // `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.
+      const name = args[0] ?? "Team";
+      let target;
+      try {
+        target = KBManager.kbPathForName(name);
+      } catch {
+        cli.usageError(`invalid KB name "${name}"`);
         return 2;
       }
       const tpl = await requireTemplateDir();
       if (tpl === null) return 1;
-      const result = await kbManager.init(args[0], tpl);
+      const result = await kbManager.init(target, tpl);
       if (!result.ok) {
         proc.stderr.write(result.error + "\n");
         return result.code;

package/src/privilege.js

@@ -0,0 +1,45 @@
+/**
+ * Privilege — resolve an agent's least-privilege execution level and map it to
+ * 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.
+ *
+ * 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 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.
+ * @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}.
+ */
+export function resolvePrivilege(agent) {
+  const level = agent?.privilege;
+  if (!PRIVILEGE_LEVELS.includes(level)) {
+    throw new Error(
+      `invalid privilege "${level}"; expected one of ${PRIVILEGE_LEVELS.join(", ")}`,
+    );
+  }
+  return level;
+}
+
+/**
+ * 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}
+ */
+export function disclaimFor(level) {
+  return level === "restricted" ? 1 : 0;
+}

package/templates/.claude/agents/recruiter.md

@@ -66,7 +66,7 @@ candidates, pipeline totals by stage/track, aggregate diversity, retention flags
 
 ```
 Decision: {observation and chosen action}
-Action: {e.g. "req-screen for John Smith against J060 forward_deployed"}
+Action: {e.g. "req-screen for John Smith against J060 forward-deployed"}
 Stage: {1 | 2 | sync | erasure}
 Priority Watch: {priority at risk + one-line why, or "none"}
 ```

package/templates/.claude/skills/candidate-report/SKILL.md

@@ -31,7 +31,7 @@ before deciding whether to invest interview time.
 
 - **Candidate name** — locates `Knowledge/Candidates/{Name}/brief.md`.
 - **Target role** — discipline, level, track (e.g.
-  `software_engineering J070 forward_deployed`). If not given, infer from the
+  `software-engineering J070 forward-deployed`). If not given, infer from the
   candidate's `Req` field → Role file. Ask the user if it can't be inferred.
 - **Recipient** — pod lead or hiring manager the report is for.
 - **CV file** (optional) — read directly when no `screening.md` exists.

package/templates/.claude/skills/req-assess/references/rubric.md

@@ -51,7 +51,7 @@ from the transcript — "seemed strong" is not evidence.
 | `emerging`      | Behaviour not observed or only when prompted                 |
 | `developing`    | Behaviour present but inconsistent or surface-level          |
 | `practicing`    | Behaviour consistent and natural throughout the interview    |
-| `role_modeling` | Behaviour demonstrated at high level, influenced the room    |
+| `role-modeling` | Behaviour demonstrated at high level, influenced the room    |
 | `exemplifying`  | Behaviour exceptional, set the standard for the conversation |
 
 ## Level signals

package/templates/.claude/skills/req-decide/references/template.md

@@ -64,7 +64,7 @@ journey.}
 
 ### Track Confirmation
 
-**Recommended track:** {forward_deployed / platform / either}
+**Recommended track:** {forward-deployed / platform / either}
 
 {Explain track fit, referencing interview moments.}
 

package/templates/.claude/skills/req-scan/references/template.md

@@ -10,7 +10,7 @@ Reference for `req-scan` Step 4. Save to `Knowledge/Prospects/{Name}.md`.
 **Date found:** {YYYY-MM-DD}
 **Location:** {location or "Not specified"}
 **Estimated level:** {J040–J110} (confidence: {high/medium/low})
-**Best track fit:** {forward_deployed / platform / either}
+**Best track fit:** {forward-deployed / platform / either}
 **Match strength:** {strong / moderate}
 
 ## Profile

package/templates/.claude/skills/req-screen/SKILL.md

@@ -92,7 +92,7 @@ If no target is available, estimate one using the level heuristics in
 ```bash
 bunx fit-pathway job {discipline} {level} --track={track}
 bunx fit-pathway job {discipline} {level} --track={track} --skills
-bunx fit-pathway track forward_deployed
+bunx fit-pathway track forward-deployed
 bunx fit-pathway track platform
 ```
 

package/templates/.claude/skills/req-screen/references/template.md

@@ -26,7 +26,7 @@ around the screening question — is this worth an interview?}
 | Dimension      | Assessment                             |
 | -------------- | -------------------------------------- |
 | **Level**      | {estimated level and confidence}       |
-| **Track fit**  | {forward_deployed / platform / either} |
+| **Track fit**  | {forward-deployed / platform / either} |
 | **Discipline** | {best discipline match}                |
 | **Gender**     | {Woman / Man / —}                      |
 
@@ -54,7 +54,7 @@ Standard reference: `{discipline} {level} --track={track}`
 
 ## Track Fit Analysis
 
-{Paragraph explaining why the candidate fits forward_deployed,
+{Paragraph explaining why the candidate fits forward-deployed,
 platform, or either. Reference specific CV evidence.}
 
 ## Screening Recommendation

package/templates/.claude/skills/req-track/SKILL.md

@@ -186,7 +186,7 @@ either skill until it changes.
 bunx fit-pathway skill --list
 ```
 
-Use agent-aligned engineering standard IDs (e.g. `data_integration`,
+Use agent-aligned engineering standard IDs (e.g. `data-integration`,
 `full_stack_development`, `architecture_and_design`) in the `## Skills` section
 instead of free-form tags. Flag any candidate with a CV attachment for
 `req-screen`.

package/templates/.claude/skills/req-workday/references/templates.md

@@ -15,7 +15,7 @@ Use when no Role file exists for the requisition. Filename:
 **Title:** {Full title from export}
 **Level:** {Infer from title: "Principal" → J100, "Staff" → J090, "Director" → J100 M-track, "Senior" → J070}
 **Track:** {P-track for IC roles, M-track for Director/Manager roles}
-**Discipline:** {Infer: "Software Engineer" → software_engineering, "Data Engineer" → data_engineering, "Data Scientist" → data_science}
+**Discipline:** {Infer: "Software Engineer" → software-engineering, "Data Engineer" → data-engineering, "Data Scientist" → data-science}
 **Domain lead:** —
 **Hiring manager:** {From export metadata if available, or "—"}
 **Locations:** {Primary Location from export}