@forwardimpact/outpost 3.12.1 → 3.13.0

package/templates/.claude/skills/req-workday/scripts/parse-workday.mjs

@@ -54,20 +54,56 @@ try {
 const filePath = process.argv[2];
 const summaryMode = process.argv.includes("--summary");
 
+/**
+ * Read a workbook. Tolerate Workday's ZIP container.
+ *
+ * Workday exports .xlsx via Apache POI's streaming writer. That writer sets
+ * the ZIP "data descriptor" flag (bit 0x08) on every entry, so the sizes live
+ * in a trailer after each entry, not in the local header. read-excel-file's
+ * streaming unzipper trusts the (zeroed) local-header sizes, loses alignment,
+ * and throws `invalid signature: 0x…`. fflate reads the authoritative ZIP
+ * central directory, so on failure we re-pack into a clean container (sizes
+ * in the local headers, no data descriptors) and retry. Files that already
+ * parse take the original path unchanged.
+ */
+async function readWorkbook(path) {
+  try {
+    return await readXlsxFile(path);
+  } catch (err) {
+    let fflate;
+    try {
+      fflate = await import("fflate");
+    } catch {
+      throw err; // fflate unavailable — surface the original parse error
+    }
+    const { readFileSync } = await import("node:fs");
+    const raw = readFileSync(path);
+    const normalized = Buffer.from(
+      fflate.zipSync(fflate.unzipSync(new Uint8Array(raw))),
+    );
+    return await readXlsxFile(normalized);
+  }
+}
+
+// read-excel-file v9 returns the whole workbook as [{ sheet, data }] —
+// read it once and index sheets from that.
+const workbook = await readWorkbook(filePath);
+const sheetNames = workbook.map((s) => s.sheet);
+
 /** Read a sheet by number (1-indexed) or name. Rows are arrays of strings. */
-async function readSheet(file, sheet) {
-  const rows = await readXlsxFile(file, { sheet });
+function readSheet(_file, sheet) {
+  const entry =
+    typeof sheet === "number"
+      ? workbook[sheet - 1]
+      : workbook.find((s) => s.sheet === sheet);
+  const rows = entry ? entry.data : [];
   // Normalise null cells to empty strings to match previous behaviour
   return rows.map((row) => row.map((cell) => (cell == null ? "" : cell)));
 }
 
-// Get sheet names to find the candidates sheet
-const sheets = await readXlsxFile(filePath, { getSheets: true });
-const sheetNames = sheets.map((s) => s.name);
-
 // --- Sheet 1: Requisition metadata ---
 
-const sheet1Rows = await readSheet(filePath, 1);
+const sheet1Rows = readSheet(filePath, 1);
 
 /** Extract the requisition ID and title from the header row. */
 function parseReqHeader(headerText) {
@@ -120,7 +156,7 @@ const requisition = {
 const candSheetName =
   sheetNames.find((n) => n.toLowerCase() === "candidates") ||
   sheetNames[Math.min(2, sheetNames.length - 1)];
-const candRows = await readSheet(filePath, candSheetName);
+const candRows = readSheet(filePath, candSheetName);
 
 // Find the header row dynamically. Look for a row that contains "Stage".
 // Old format: row 3 (index 2). New format: row 8 (index 7).
@@ -194,24 +230,64 @@ function col(row, field) {
   return row[idx] ?? "";
 }
 
+// Any character outside the Latin script blocks (Basic Latin + Latin-1
+// Supplement + Latin Extended-A/B + Latin Extended Additional). Accented Latin
+// (é, ñ, ø, ç, Vietnamese, …) stays; Greek, Cyrillic, CJK, Arabic, Hebrew,
+// etc. count as native-alphabet text to drop.
+const NON_LATIN = /[^\u0020-\u024F\u1E00-\u1EFF]/;
+const HAS_LATIN_LETTER = /[A-Za-z\u00C0-\u024F\u1E00-\u1EFF]/;
+
 /**
- * Clean a candidate name. Strip annotations like (Prior Worker), (Internal),
- * etc. Returns { cleanName, internalExternal }.
+ * Clean a candidate name into the canonical Latin name.
+ *
+ * Workday encodes several things in the name cell as parentheticals:
+ *   - Employment annotations: `(Internal)`, `(Prior Worker)`, `(External)`.
+ *   - A native-alphabet transliteration of the name, e.g.
+ *     `Nikos Papadopoulos (ΝΙΚΟΣ ΠΑΠΑΔΟΠΟΥΛΟΣ)` or `Wei Zhang （张伟）`.
+ * A name may carry both, in either paren style. Normalise on the Latin name:
+ * strip every trailing parenthetical (classify employment ones into
+ * `internalExternal`, discard native-alphabet ones), then drop any residual
+ * non-Latin-script tokens. Returns { cleanName, internalExternal }.
  */
+// biome-ignore lint/complexity/noExcessiveCognitiveComplexity: annotation peel loop classifies employment vs transliteration cases
 function parseName(raw) {
-  const name = String(raw).trim();
+  // Normalise full-width parens （） to ASCII so both styles strip uniformly.
+  let name = String(raw).replace(/（/g, "(").replace(/）/g, ")").trim();
   if (!name) return { cleanName: "", internalExternal: "" };
 
-  const match = name.match(/^(.+?)\s*\(([^)]+)\)\s*$/);
-  if (match) {
-    const annotation = match[2].trim();
-    let ie;
-    if (/prior\s*worker/i.test(annotation)) ie = "External (Prior Worker)";
-    else if (/internal/i.test(annotation)) ie = "Internal";
-    else ie = annotation;
-    return { cleanName: match[1].trim(), internalExternal: ie };
+  let internalExternal = "";
+  // Repeatedly peel a trailing parenthetical group (allowing one level of
+  // nesting so `(External (Prior Worker))` is captured whole).
+  const trailing = /\s*\(([^()]*(?:\([^()]*\)[^()]*)*)\)\s*$/;
+  let m;
+  while ((m = name.match(trailing)) !== null) {
+    const annotation = m[1].trim();
+    if (/prior\s*worker/i.test(annotation)) {
+      if (!internalExternal) internalExternal = "External (Prior Worker)";
+    } else if (/internal/i.test(annotation)) {
+      if (!internalExternal) internalExternal = "Internal";
+    } else if (/external/i.test(annotation)) {
+      if (!internalExternal) internalExternal = "External";
+    } else if (NON_LATIN.test(annotation)) {
+      // Native-alphabet transliteration of the name — drop, no IE signal.
+    } else if (!internalExternal && annotation) {
+      // Unknown Latin annotation — preserve prior behaviour (first one wins).
+      internalExternal = annotation;
+    }
+    name = name.slice(0, name.length - m[0].length).trim();
   }
-  return { cleanName: name, internalExternal: "" };
+
+  // Drop any residual whole-word tokens that are purely non-Latin script
+  // (e.g. a native name appended without parentheses). Keep Latin tokens
+  // and pure punctuation/digits.
+  name = name
+    .split(/\s+/)
+    .filter((tok) => HAS_LATIN_LETTER.test(tok) || !NON_LATIN.test(tok))
+    .join(" ")
+    .replace(/\s{2,}/g, " ")
+    .trim();
+
+  return { cleanName: name, internalExternal };
 }
 
 /** Detect source-based internal/external when the name annotation is absent. */

package/templates/.claude/skills/send-chat/SKILL.md

@@ -8,6 +8,9 @@ compatibility:
 
 # Send Chat
 
+Write tier: `0-Draft` (sending is an export)
+Frontmatter: none
+
 Send chat messages to people with browser automation against a web-based chat
 platform (Microsoft Teams, Slack, or similar). This skill resolves recipients by
 name from the knowledge graph. The user can say "message Sarah about the
@@ -36,7 +39,7 @@ base.**
 When the user mentions ANY person:
 
 1. **STOP** — Do not open the chat platform yet
-2. **SEARCH** — Look them up: `rg -l "{name}" Knowledge/People/`
+2. **SEARCH** — Look them up: `rg -l "{name}" 3-Team/People/`
 3. **READ** — Read their note to understand context, role, recent interactions
 4. **UNDERSTAND** — Know who they are and what you work on together
 5. **THEN PROCEED** — Only now compose the message and use browser automation
@@ -54,10 +57,10 @@ reference to a full name with the knowledge graph:
 
 ```bash
 # Find person by partial name
-rg -l -i "{name}" Knowledge/People/
+rg -l -i "{name}" 3-Team/People/
 
 # If ambiguous, read candidates to disambiguate
-cat "Knowledge/People/{Candidate}.md"
+cat "3-Team/People/{Candidate}.md"
 ```
 
 **If ambiguous** (multiple matches), ask the user which person they mean. List
@@ -74,7 +77,7 @@ can review and edit the exact message before you send it.
 ### Draft Workflow
 
 1. **Compose the message** based on context and user intent.
-2. **Write it to a draft file** at `Drafts/chat-{recipient-slug}-{date}.md`
+2. **Write it to a draft file** at `0-Draft/chat-{recipient-slug}-{date}.md`
    - `{recipient-slug}` = lowercase, hyphenated full name (e.g. `sarah-chen`)
    - `{date}` = ISO date (e.g. `2026-02-19`)
 3. **Show the user the draft** — display the file path and contents.
@@ -139,14 +142,11 @@ same organization.
 4. Press Enter or click Send
 5. Take a screenshot to confirm the message was sent
 
-### Step 4: Update Knowledge Graph (Optional)
-
-If the message is substantive (not just "hey" or "thanks"), note the interaction
-on the person's knowledge note:
+### Step 4: Keep the Draft as the Record
 
-```markdown
-- {YYYY-MM-DD}: Messaged on {Platform} re: {topic}
-```
+Do not write the interaction to the person's note. This skill writes only to
+`0-Draft/`. The chat sync (`sync-teams`) and `extract-entities` record the
+interaction when the messages sync.
 
 ## Error Handling
 

package/templates/.claude/skills/sync-apple-calendar/SKILL.md

@@ -6,6 +6,9 @@ compatibility: Requires macOS with Apple Calendar configured and Full Disk Acces
 
 # Sync Apple Calendar
 
+Write tier: none (cache only)
+Frontmatter: none
+
 Sync calendar events from the macOS Calendar app's local SQLite database into
 `~/.cache/fit/outpost/apple_calendar/` as JSON files. This is an automated skill
 in the data pipeline. It ingests raw calendar data that other skills (like

package/templates/.claude/skills/sync-apple-mail/SKILL.md

@@ -6,6 +6,9 @@ compatibility: Requires macOS with Apple Mail configured and Full Disk Access gr
 
 # Sync Apple Mail
 
+Write tier: none (cache only)
+Frontmatter: none
+
 Sync email threads from the macOS Mail app's local SQLite database into
 `~/.cache/fit/outpost/apple_mail/` as markdown files. This is an automated skill
 in the data pipeline. It ingests raw email data that other skills (like

package/templates/.claude/skills/sync-teams/SKILL.md

@@ -6,6 +6,9 @@ compatibility: Requires macOS with Microsoft Teams desktop app (com.microsoft.te
 
 # Sync Teams
 
+Write tier: none (cache only)
+Frontmatter: none
+
 Sync recent Microsoft Teams chat messages into
 `~/.cache/fit/outpost/teams_chat/` as markdown files. This is an automated skill
 in the data pipeline. It ingests chat data that other skills (like

package/templates/.claude/skills/upstream-instructions/SKILL.md

@@ -5,6 +5,9 @@ description: Track changes to this installation's instruction files: the root CL
 
 # Upstream Instructions
 
+Write tier: none (the root CHANGELOG.md is a personal surface)
+Frontmatter: none
+
 Track changes to this installation's **instructions**. Record them in one root
 `CHANGELOG.md` so you can contribute improvements back to the upstream monorepo.
 "Instructions" means all three surfaces, and they carry equal weight:
@@ -32,7 +35,7 @@ Track changes to this installation's **instructions**. Record them in one root
 - `.claude/skills/*/SKILL.md` and reference files — skills.
 - `CHANGELOG.md` (root) — the existing changelog, for what's already recorded.
 - The changes you made in the current working session — the source of truth for
-  what changed. The KB lives on a synced filesystem. It has no version control.
+  what changed. The KB may sync without version control; do not rely on it.
 
 ## Outputs
 
@@ -64,8 +67,8 @@ head -20 CHANGELOG.md 2>/dev/null   # newest date already recorded, if any
 
 ### 2. Identify changed instructions
 
-Knowledge bases live on a synced filesystem. They do not live in Git, so there
-is no commit history to diff. Identify what changed from the work you did **this
+A knowledge base may sync over a mount with no version control, so never rely
+on commit history. Identify what changed from the work you did **this
 session**. Recall every edit, addition, removal, and rename you made to
 `CLAUDE.md`, `.claude/agents/`, and `.claude/skills/` during the current
 conversation. List them per surface.
@@ -102,8 +105,8 @@ Every entry must answer:
 2. **Why?** — the problem encountered or improvement discovered in use.
 3. **Details** — a summary of the actual change (not a full diff).
 
-Good: "Agents now read `Knowledge/Priorities/` at the start of every wake and
-flag anything that threatens a priority. Drafts and triage ignored strategic
+Good: "Agents now read `Priorities/` in every tier at the start of every wake
+and flag anything that threatens a priority. Drafts and triage ignored strategic
 context."
 
 Bad: "Updated the agents" / "Fixed stuff" / "Changed line 42".

package/templates/.claude/skills/upstream-instructions/references/examples.md

@@ -20,7 +20,7 @@ strategic layer.
 Priorities, removing the Project↔Goal↔Priority coupling that earned nothing.
 
 **Details:**
-- Deleted `Knowledge/Goals/`; repointed live backlinks to `Priorities/C - Onboarding`.
+- Deleted `3-Team/Goals/`; repointed live backlinks to `3-Team/Priorities/C - Onboarding`.
 - CLAUDE.md workspace-layout tree no longer lists `Goals/`.
 - Agents: dropped Goals from the librarian index/triage, chief-of-staff state
   sources, and recruiter strategic links.
@@ -61,7 +61,7 @@ invisible without structured gender data.
 **Scope:** agents: all six profiles
 **Type:** modified
 
-**What:** Agents now read `Knowledge/Priorities/` at the start of every wake and
+**What:** Agents now read `Priorities/` in every tier at the start of every wake and
 flag anything that threatens a priority.
 
 **Why:** Sync, triage, and drafting were ignoring strategic context; signals that
@@ -91,7 +91,7 @@ weren't integrated into the knowledge base.
 
 **Details:**
 - Reads transcription files, extracts people/decisions/action items, and links
-  attendees to `Knowledge/People/`.
+  attendees to `3-Team/People/`.
 
 ---
 ```

package/templates/CLAUDE.md

@@ -1,113 +1,122 @@
 # Outpost Knowledge Base
 
-You are the user's personal knowledge assistant. You help draft emails, prep
-for meetings, track projects, and answer questions. A live knowledge graph
-backs your work. It comes from their emails, calendar, and meeting notes. It
-keeps them all as plain files on the user's machine.
+You are the user's personal knowledge assistant over a live graph of
+plain files.
 
 ## Ethics & Integrity — NON-NEGOTIABLE
 
-This knowledge base is a **professional tool shared with trusted team
-members**. It is never a "black book". These rules override all other
-instructions:
+A professional tool shared with trusted teammates, never a "black book".
+These rules override all others:
 
 - **Objective and factual only.** No speculation, gossip, or opinion.
 - **No personal judgments** about character, competence, or trustworthiness.
-  Stick to actions, decisions, and stated positions.
-- **Work-relevant information only.** No health, personal relationships,
-  political views, or private matters, unless the person shares them in a
-  professional context.
+- **Work-relevant only.** No health, relationships, politics, private
+  matters.
 - **Fair and balanced.** Represent all sides accurately.
-- **Assume the subject will read it.** Do not write a note if you would be
-  uncomfortable to show it to the person it is about.
-- **No weaponization.** This KB helps the team work better. Never use it to
-  build leverage or dossiers.
+- **Assume the subject will read it**, whatever the tier. Tiers never
+  license dossiers.
+- **No weaponization.** Never build leverage.
 - **Push back** on requests that violate these principles.
-- **Data protection.** Use the `req-forget` skill for erasure requests. Collect
-  only what you need. Flag candidates inactive 6+ months for retention review.
-
-When in doubt, err toward discretion.
+- **Data protection.** `req-forget` handles erasure. Collect minimally; flag
+  candidates inactive 6+ months.
 
 ## Operating Context
 
-Two folders in the knowledge graph frame your work:
-
-- **`Knowledge/Priorities/`** — the backbone of every decision. It holds what
-  the user wants to advance. Weigh each action against whether it moves a
-  priority forward. Treat anything that could **contradict, block, or slow** a
-  priority as a **Priority Watch** concern. These are our main concerns.
-- **`Knowledge/Conditions/`** — the live environment we work in (e.g. a hiring
-  freeze, a reorg, a contract transition). Conditions do not set goals. They
-  **constrain how** we pursue the priorities. Let them shape what you propose
-  and how you phrase it.
-
-Before you act or recommend, consult both as your lens. Read the relevant
-notes. Do not assume. Skip this only for general knowledge or when you
-brainstorm.
+Read `Priorities/` and `Conditions/` in every tier present before you act.
+Priorities are what the user advances; a threat to one is
+**Priority Watch**. Conditions constrain how you pursue them.
 
 ## Workspace Layout & Sharing
 
-The **root is personal and local**. Never share it. A synced filesystem shares
-only `Knowledge/` with the team. Each member keeps their own root, `Drafts/`,
-and `Briefings/`. KBs are **not** Git repositories. They sync as plain files.
-`CLAUDE.md` and `.claude/` are yours to tweak. Use the `fit-outpost` CLI to
-install or update the standard instruction set.
-
-```text
-./                      # Personal root — never shared
-├── CLAUDE.md           # This file
-├── .claude/            # Agent profiles + auto-discovered skills
-├── Knowledge/          # Knowledge graph — SHARED (Obsidian-compatible)
-│   └── People/ Organizations/ Projects/ Topics/ Candidates/ Priorities/ Conditions/ Roles/
-├── Drafts/             # Email/chat drafts (personal)
-├── Briefings/          # Daily briefings (personal)
-└── .mcp.json           # MCP config (optional)
-```
-
-## Search
-
-Use the **ripgrep** `rg` program for fast knowledge graph searches.
+The KB root is the Obsidian vault. Tier directories (one digit, one dash) are
+the graph and the share units; a lower rank is a narrower audience. Every other
+root entry is personal, never shared (instruction files, `Briefings/`,
+`registry.yaml`, `validation-baseline.json`); personal folders never match the
+rank grammar.
+
+- `0-Draft/` — owner only, never shared: drafts, agent reports, permanent
+  owner-only notes.
+- `1-Management/` — senior managers. User-placed; fellow-manager notes go
+  to tier 0.
+- `2-Confidential/` — hiring managers. Candidates, Prospects, Roles,
+  Erasure.
+- `3-Team/` — the team. People, Teams, Organizations, Projects, Topics,
+  Priorities, Conditions, Tasks.
+- `4-Public/` — anyone. User-placed after rights and verification checks.
+
+Rename, add, or remove tiers; entity subdirectories appear on demand.
+
+Sharing is cumulative: a tier-N member receives every wider tier, from
+tier 1 up, over any syncing mount (OneDrive, Git). A shared tier is often a
+symlink into a synced folder; the rank comes from the link's name. Keep
+the vault root outside every cloud-synced folder.
+`npx fit-outpost validate <root>` checks any vault or suffix.
+
+## Placement and Links
+
+- Link only to your own tier or a wider one, never narrower or personal.
+- Shared-tier links are tier-prefixed and vault-absolute
+  (`[[3-Team/People/Sarah Chen]]`); bare basenames only in tier 0 or one
+  entity folder.
+- Place each note in the widest tier that excludes everyone who must not
+  read it; otherwise tier 0.
+- Promote: a human moves a note into its tier. Export: a skill
+  sends a copy over mail or chat; the note keeps its tier. Named recipients
+  and panels are exports.
+- Overlay: a narrower facet in a narrower tier, declared by a one-way
+  quoted `canonical` link to the wide note. Forms: facet, timeline split
+  (same date keys), inverse stub (linked down to).
+- Link inversion: the wide note's narrow link moves, with its one-line
+  context, into the narrow note; no tombstone.
+- Route each dated entry to the note in its own tier.
+- Aggregates over narrower sources go to `0-Draft/`; no agent writes
+  tier 1.
+- `no-redistribute` overrides tier; marked or third-party content never
+  enters tier 4.
+- Assessment prose about a named subject lives only in that subject's
+  record.
+
+## Note Metadata
+
+Stamp YAML frontmatter on every note. Humans edit `registry.yaml`; agents
+select from it.
+
+- Core on every shared note: `type`, `created`, `updated` (ISO dates).
+- Conditional: `aliases` (person, candidate, organization), `status`
+  (candidate, prospect), `canonical` (overlays), `verified` (tier 4).
+- Flat block at line 1, snake_case, canonical key order; property links
+  double-quoted, tier-prefixed.
+- No tier, rank, or audience key; the path is the sole tier authority.
+- Tags: the closed `topic/` registry taxonomy, frontmatter `tags` only;
+  each tag carries its widest tier.
+- Coherence: Bases on `type`/`status`, aliases in the switcher, path-keyed
+  graph groups; absolute-link, same-folder vault settings.
 
 ## Agents
 
-Agents in `.claude/agents/` maintain this KB. The Outpost scheduler wakes them
-on a schedule. On each wake, observe the state. Decide the most valuable action.
-Execute it.
-
-Each agent's own profile under `.claude/agents/` declares its skills.
+The scheduler wakes the `.claude/agents/` agents: observe, decide,
+execute. Profiles declare skills, read scope, write tier.
 
-| Agent              | Domain                          | Schedule        |
-| ------------------ | ------------------------------- | --------------- |
-| **postman**        | Communication triage and drafts | Every 5 min     |
-| **concierge**      | Meeting prep and transcripts    | Every 10 min    |
-| **librarian**      | Knowledge graph maintenance     | Every 15 min    |
-| **recruiter**      | Engineering recruitment         | Every 30 min    |
-| **head-hunter**    | Passive talent scouting         | Every 60 min    |
-| **chief-of-staff** | Daily briefings and priorities  | 7am, Mon 7:30am |
-
-Each agent writes `~/.cache/fit/outpost/state/{agent}_triage.md` per wake. The
-**chief-of-staff** reads all of them to write daily briefings in `Briefings/`.
+- **postman** (5 min) — communication triage and drafts
+- **concierge** (10 min) — meeting prep and transcripts
+- **librarian** (15 min) — knowledge graph maintenance
+- **recruiter** (30 min) — engineering recruitment
+- **head-hunter** (60 min) — passive talent scouting
+- **chief-of-staff** (daily 7am) — briefings in `Briefings/`
 
 ## Cache Directory (`~/.cache/fit/outpost/`)
 
-Synced data and runtime state live outside the KB. Only notes, drafts, and
-briefings live inside it.
-
-**Resolve `~` before you pass a path to a tool.** Shell commands expand `~`.
-The Write and Edit tools do not. A literal `~/...` creates a stray `.cache/`
-inside the KB. Read `$HOME` at runtime and pass the full `$HOME/...` path. Read
-meetings, emails, and messages directly from the source dirs below.
+Synced data and runtime state live outside the KB. Resolve `~` to `$HOME`
+for Write and Edit; search with `rg`.
 
-- `apple_mail/` — Mail threads as `.md` (plus `attachments/`)
-- `apple_calendar/` — Calendar events as `.json`
-- `teams_chat/` — Teams 1:1 chats as `.md`
-- `head-hunter/` — head-hunter agent memory
-- `state/` — per-source last-sync timestamps, processed-file index, and
-  `{agent}_triage.md` per agent
+- `apple_mail/`, `apple_calendar/`, `teams_chat/` — synced sources
+- `head-hunter/` — agent memory
+- `drafts/` — the draft-status ledgers (`handled`, `ignored`)
+- `state/` — daemon-owned sync state and triage files
 
-## User Identity
+## User Identity & Team
 
-The current user's identity lives at
-`~/.cache/fit/outpost/state/identity.md`. Read it directly. If the file is
-missing or stale, run the `person-identify` skill to refresh it from the
-corporate directory.
+Read `~/.cache/fit/outpost/state/identity.md`; refresh with
+`person-identify`. Manager plus Direct reports define "our team";
+`Direct reports: none` means an individual contributor. Resolve peers with
+`person-lookup` on the Manager. Never guess.