@forwardimpact/outpost 3.12.0 → 3.13.0

package/templates/.claude/skills/extract-entities/references/sources.md

@@ -19,11 +19,11 @@ Calendar events. Internal-only meetings still enrich Project and Topic notes
 (decisions, agenda items). Only skip all-day placeholders with no attendees and
 no description (e.g. "Block", "OOO").
 
-**Stub guard:** calendar attendance alone never creates a People note — calendar
-events only *enrich* existing notes (see the table below). An attendee who is
-only on the invite list, with no interaction or decision attributed to them, is
-not profiled. If they matter, they go in the Organization's `## Contacts`. Never
-write a placeholder profile; see the
+**Stub guard:** calendar attendance alone never creates a People note. Calendar
+events only *enrich* existing notes (see the table below). Do not profile an
+attendee who is only on the invite list, with no interaction or decision
+attributed to them. If they matter, they go in the Organization's `## Contacts`.
+Never write a placeholder profile. See the
 [minimum content bar](resolution.md#minimum-content-bar--no-stubs).
 
 ## Skip entirely
@@ -40,7 +40,7 @@ write a placeholder profile; see the
 
 ## Process — update existing notes only
 
-- Emails from people already in `Knowledge/People/`.
+- Emails from people already in `3-Team/People/`.
 - Emails referencing existing projects or organizations.
 
 ## Process — can create new notes
@@ -54,9 +54,9 @@ write a placeholder profile; see the
 If an email is a warm introduction from someone with a note, and they introduce
 a new person, **create** a note for the introduced person.
 
-Signals: subject contains "Intro:", "Introduction:", "Meet", "Connecting"; body
-contains "introduce you to", "want to connect", "meet [Name]"; new person is
-CC'd.
+Signals: the subject contains "Intro:", "Introduction:", "Meet", or
+"Connecting". The body contains "introduce you to", "want to connect", or
+"meet [Name]". The sender CCs the new person.
 
 ## Self-exclusion
 

package/templates/.claude/skills/extract-entities/references/templates-conditions.md

@@ -1,10 +1,16 @@
 # Condition Template
 
 Conditions are time-bound organizational states that affect multiple entities.
-They can be **auto-created** by the librarian agent when cross-cutting patterns
-are detected, or manually created by the user. Lifecycle: active → resolved.
+The librarian agent can **auto-create** them when it detects cross-cutting
+patterns. The user can also create them manually. Lifecycle: active → resolved.
 
 ```markdown
+---
+type: condition
+created: {YYYY-MM-DD}
+updated: {YYYY-MM-DD}
+---
+
 # {Condition Name}
 
 ## Info
@@ -16,10 +22,10 @@ are detected, or manually created by the user. Lifecycle: active → resolved.
 **Resolution signal:** {What would indicate this condition has ended}
 
 ## Affects
-{Priorities, Projects, Roles, and People impacted by this condition}
-- [[Priorities/{Priority}]] — {how it's affected}
-- [[Projects/{Project}]] — {how it's affected}
-- [[Roles/{Role}]] — {how it's affected}
+{Priorities, Projects, and People impacted by this condition. A Role file
+links here instead — a Condition never links into a narrower tier.}
+- [[3-Team/Priorities/{Priority}]] — {how it's affected}
+- [[3-Team/Projects/{Project}]] — {how it's affected}
 
 ## Agent implications
 {How agents should modify their behavior while this condition is active}

package/templates/.claude/skills/extract-entities/references/templates-people-orgs.md

@@ -1,16 +1,28 @@
 # People and Organization Templates
 
+Every template opens with the YAML frontmatter block: the core keys (`type`,
+`created`, `updated`) plus the type's conditional keys from `registry.yaml`.
+A key lifted into frontmatter (`aliases` here) leaves the body; unmatched
+bold keys stay body prose.
+
 ## People
 
 ```markdown
+---
+type: person
+created: {YYYY-MM-DD}
+updated: {YYYY-MM-DD}
+aliases:
+  - "{name variant}"
+---
+
 # {Full Name}
 
 ## Info
 **Role:** {role or inferred role with qualifier}
-**Organization:** [[Organizations/{organization}]]
-**Reports to:** [[People/{{Person}}]]
+**Organization:** [[3-Team/Organizations/{organization}]]
+**Reports to:** [[3-Team/People/{{Person}}]]
 **Email:** {email}
-**Aliases:** {comma-separated variants}
 **First met:** {YYYY-MM-DD}
 **Last seen:** {YYYY-MM-DD}
 
@@ -18,12 +30,12 @@
 {2-3 sentences: who they are, why you know them, what you're working on}
 
 ## Connected to
-- [[Organizations/{Org}]] — works at
-- [[People/{Person}]] — {relationship}
-- [[Projects/{Project}]] — {role}
+- [[3-Team/Organizations/{Org}]] — works at
+- [[3-Team/People/{Person}]] — {relationship}
+- [[3-Team/Projects/{Project}]] — {role}
 
 ## Activity
-- **{YYYY-MM-DD}** ({meeting|email|voice memo}): {Summary with [[Folder/Name]] links}
+- **{YYYY-MM-DD}** ({meeting|email|voice memo}): {Summary with [[3-Team/Folder/Name]] links}
 
 ## Key facts
 {substantive facts only — leave empty if none}
@@ -35,6 +47,14 @@
 ## Organizations
 
 ```markdown
+---
+type: organization
+created: {YYYY-MM-DD}
+updated: {YYYY-MM-DD}
+aliases:
+  - "{name variant}"
+---
+
 # {Organization Name}
 
 ## Info
@@ -42,7 +62,6 @@
 **Industry:** {industry}
 **Relationship:** {customer|prospect|partner|vendor}
 **Domain:** {primary email domain}
-**Aliases:** {comma-separated}
 **First met:** {YYYY-MM-DD}
 **Last seen:** {YYYY-MM-DD}
 
@@ -50,13 +69,13 @@
 {2-3 sentences}
 
 ## People
-- [[People/{Person}]] — {role}
+- [[3-Team/People/{Person}]] — {role}
 
 ## Contacts
 {for transactional contacts who don't get their own notes}
 
 ## Projects
-- [[Projects/{Project}]] — {relationship}
+- [[3-Team/Projects/{Project}]] — {relationship}
 
 ## Activity
 - **{YYYY-MM-DD}** ({type}): {Summary}

package/templates/.claude/skills/extract-entities/references/templates-priorities.md

@@ -1,20 +1,26 @@
 # Priority Templates
 
-Priorities are **never auto-created** by `extract-entities`. They are set
-deliberately by the user. This template is for manual creation only —
+`extract-entities` **never auto-creates** Priorities. The user sets them
+deliberately. Use this template only for a note you write by hand.
 `extract-entities` and `anarlog-process` only **link to** and **update progress
 on** existing notes.
 
 ## Priorities
 
 ```markdown
+---
+type: priority
+created: {YYYY-MM-DD}
+updated: {YYYY-MM-DD}
+---
+
 # {Priority Name}
 
 ## About
 {2-3 sentences: what this strategic direction means and why it matters}
 
 **Status:** {active|paused|retired}
-**Owner:** [[People/{Person}]]
+**Owner:** [[3-Team/People/{Person}]]
 **Set:** {YYYY-MM-DD}
 
 ## What this means
@@ -25,7 +31,7 @@ on** existing notes.
 here — there is no separate Goals entity.}
 
 ## Projects
-- [[Projects/{Project}]] — {relationship}
+- [[3-Team/Projects/{Project}]] — {relationship}
 
 ## Key facts
 {substantive facts only — leave empty if none}

package/templates/.claude/skills/extract-entities/references/templates-projects-topics.md

@@ -3,6 +3,12 @@
 ## Projects
 
 ```markdown
+---
+type: project
+created: {YYYY-MM-DD}
+updated: {YYYY-MM-DD}
+---
+
 # {Project Name}
 
 ## Info
@@ -15,17 +21,17 @@
 {2-3 sentences}
 
 ## Priorities
-- [[Priorities/{Priority}]] — {how this project contributes}
+- [[3-Team/Priorities/{Priority}]] — {how this project contributes}
 
 ## People
-- [[People/{Person}]] — {role}
+- [[3-Team/People/{Person}]] — {role}
 
 ## Organizations
-- [[Organizations/{Org}]] — {relationship}
+- [[3-Team/Organizations/{Org}]] — {relationship}
 
 ## Related
-- [[Priorities/{Priority}]] — {relationship}
-- [[Topics/{Topic}]] — {relationship}
+- [[3-Team/Priorities/{Priority}]] — {relationship}
+- [[3-Team/Topics/{Topic}]] — {relationship}
 
 ## Timeline
 **{YYYY-MM-DD}** ({type})
@@ -42,6 +48,12 @@
 ## Topics
 
 ```markdown
+---
+type: topic
+created: {YYYY-MM-DD}
+updated: {YYYY-MM-DD}
+---
+
 # {Topic Name}
 
 ## About
@@ -53,8 +65,8 @@
 **Last mentioned:** {YYYY-MM-DD}
 
 ## Related
-- [[People/{Person}]] — {relationship}
-- [[Organizations/{Org}]] — {relationship}
+- [[3-Team/People/{Person}]] — {relationship}
+- [[3-Team/Organizations/{Org}]] — {relationship}
 
 ## Log
 **{YYYY-MM-DD}** ({type}: {title})

package/templates/.claude/skills/extract-entities/scripts/state.mjs

@@ -2,12 +2,13 @@
 /**
  * Manage graph_processed state for entity extraction.
  *
- * Tracks which source files (synced emails and calendar events) have already
- * been processed by the extract-entities skill. The `check` command lists files
- * that are new or changed since their last recorded hash; `update` marks files
- * as processed by storing their current SHA-256 hash.
+ * The script tracks which source files the extract-entities skill already
+ * processed. Those files are synced emails and calendar events. The `check`
+ * command lists files that are new or changed since their last recorded hash.
+ * The `update` command marks files as processed. It stores the current
+ * SHA-256 hash of each file.
  *
- * State is persisted as a TSV file at
+ * The script keeps the state in a TSV file at
  * ~/.cache/fit/outpost/state/graph_processed (path<TAB>hash).
  */
 
@@ -43,7 +44,7 @@ const SOURCE_DIRS = [
   join(HOME, ".cache/fit/outpost/teams_chat"),
 ];
 
-/** Compute SHA-256 hash of a file. */
+/** Compute the SHA-256 hash of a file. */
 function fileHash(filePath) {
   const data = readFileSync(filePath);
   return createHash("sha256").update(data).digest("hex");
@@ -74,7 +75,7 @@ function saveState(state) {
   writeFileSync(STATE_FILE, text);
 }
 
-/** Find source files that are new or have changed since last processing. */
+/** Find source files that are new or changed since the last run. */
 function check() {
   const state = loadState();
   const newFiles = [];
@@ -97,7 +98,7 @@ function check() {
   return newFiles.length;
 }
 
-/** Mark files as processed by updating their hashes in state. */
+/** Mark files as processed. Update their hashes in the state file. */
 function update(filePaths) {
   const state = loadState();
   for (const fp of filePaths) {

package/templates/.claude/skills/meeting-prep/SKILL.md

@@ -1,13 +1,16 @@
 ---
 name: meeting-prep
-description: Prepare for meetings by gathering context from the knowledge base and calendar. Use when the user asks to prep for a meeting or wants a briefing on upcoming meetings. Creates personalized briefings with attendee history, open items, and suggested talking points.
+description: Prepare for meetings. Gather context from the knowledge base and calendar. Use when the user asks to prep for a meeting or wants a briefing on upcoming meetings. Creates personalized briefings with attendee history, open items, and suggested talking points.
 ---
 
 # Meeting Prep
 
-Help the user prepare for meetings by gathering context from the knowledge base
-and calendar. Creates personalized briefing documents with attendee history,
-open items, and suggested talking points.
+Write tier: none (the output is personal `Briefings/`)
+Frontmatter: none
+
+Help the user prepare for meetings. Gather context from the knowledge base and
+calendar. Create personalized briefing documents with attendee history, open
+items, and suggested talking points.
 
 ## Trigger
 
@@ -17,19 +20,21 @@ meetings.
 ## Prerequisites
 
 - Calendar data synced in `~/.cache/fit/outpost/apple_calendar/`
-- Knowledge base populated (from `extract-entities` skill)
+- A populated knowledge base (from the `extract-entities` skill)
 
 ## Inputs
 
 - `~/.cache/fit/outpost/apple_calendar/*.json` — calendar events
-- `Knowledge/People/*.md` — attendee context
-- `Knowledge/Organizations/*.md` — company context
-- `Knowledge/Projects/*.md` — project context
-- `Knowledge/Priorities/*.md` — active priorities and strategic context for
-  framing
-- `Knowledge/Candidates/*/brief.md` — candidate context (for interview meetings)
-- `Knowledge/Roles/*.md` — role/requisition context (for interview meetings);
-  check the `**Status:**` field to distinguish active from historical reqs
+- `3-Team/People/*.md` — attendee context
+- `3-Team/Organizations/*.md` — company context
+- `3-Team/Projects/*.md` — project context
+- `3-Team/Priorities/*.md` — active priorities and strategic context to
+  frame the brief
+- `2-Confidential/Candidates/*/brief.md` — candidate context (for interview
+  meetings)
+- `2-Confidential/Roles/*.md` — role/requisition context (for interview
+  meetings). Check the `**Status:**` field to distinguish active from historical
+  reqs
 
 ## Outputs
 
@@ -39,32 +44,32 @@ meetings.
 
 ## Critical: Always Look Up Context First
 
-**BEFORE creating any meeting brief, you MUST look up the attendees in the
+**BEFORE you create any meeting brief, you MUST look up the attendees in the
 knowledge base.**
 
 When the user asks to prep for a meeting:
 
 1. **STOP** — Do not create a generic brief
-2. **SEARCH** — Look up each attendee: `rg -l "Attendee Name" Knowledge/`
-3. **READ** — Read their notes: `cat "Knowledge/People/Attendee Name.md"`
+2. **SEARCH** — Look up each attendee: `rg -l "Attendee Name" [0-9]-*/`
+3. **READ** — Read their notes: `cat "3-Team/People/Attendee Name.md"`
 4. **UNDERSTAND** — Extract role, organization, history, open items
-5. **THEN BRIEF** — Create the meeting brief using this context
+5. **THEN BRIEF** — Create the meeting brief with this context
 
 ## Key Principles
 
-**Ask, don't guess:**
+**Ask. Do not guess:**
 
 - If unclear which meeting, ASK
 - If multiple upcoming meetings, offer choices
 - **WRONG:** "Here's a generic meeting prep template"
 - **RIGHT:** "I see meetings with Sarah (2pm) and John (4pm). Which one?"
 
-**Be thorough, not generic:**
+**Be thorough. Do not be generic:**
 
-- Include specific history, open items, and context from knowledge base
+- Include specific history, open items, and context from the knowledge base
 - Reference actual past interactions and commitments
 
-## Processing Flow
+## Process Flow
 
 ### Step 1: Identify the Meeting
 
@@ -82,7 +87,7 @@ If "prep me for my next meeting":
 
 - Query upcoming events with `--upcoming 2h`
 - Find the next meeting with external attendees
-- Confirm with user if unclear
+- Confirm with the user if unclear
 
 ### Step 2: Parse Calendar Event
 
@@ -93,18 +98,18 @@ Extract: summary, start/end time, attendees (names and emails), description.
 For each attendee:
 
 ```bash
-rg -l "attendee_name" Knowledge/People/
-rg -l "attendee_email" Knowledge/People/
-cat "Knowledge/People/Attendee Name.md"
-cat "Knowledge/Organizations/Their Company.md"
-rg -l "attendee_name" Knowledge/Projects/
+rg -l "attendee_name" 3-Team/People/
+rg -l "attendee_email" 3-Team/People/
+cat "3-Team/People/Attendee Name.md"
+cat "3-Team/Organizations/Their Company.md"
+rg -l "attendee_name" 3-Team/Projects/
 ```
 
 Extract: role/title, company, key facts, previous interactions, open items.
 
-Also check `Knowledge/Priorities/` for context relevant
-to the meeting topic — e.g. if the meeting is about hiring, surface the relevant
-hiring Priority's status and progress.
+Also check `3-Team/Priorities/` for context relevant to the meeting topic.
+For example, if the meeting is about hiring, surface the relevant hiring
+Priority's status and progress.
 
 ### Step 4: Create Meeting Brief
 
@@ -134,19 +139,20 @@ Suggested Talking Points
 **Guidelines:**
 
 - Use `[[Name]]` wiki-link syntax for cross-references
-- Keep "About" section to 2-3 sentences max
+- Keep the "About" section to 2-3 sentences max
 - History: reverse chronological, 3-5 most relevant items
-- Talking points: concrete, not generic
+- Talking points: concrete. Avoid generic suggestions
 - If no notes exist for a person, mention that and offer to create one
 
 ### Interview Meeting Context
 
-When preparing for interview meetings (title contains "Interview", "Screening",
-"Decomposition", "Panel", or a candidate name from `Knowledge/Candidates/`):
+When you prepare for interview meetings (title contains "Interview",
+"Screening", "Decomposition", "Panel", or a candidate name from
+`2-Confidential/Candidates/`):
 
-1. **Read the candidate brief:** `Knowledge/Candidates/{Name}/brief.md`
+1. **Read the candidate brief:** `2-Confidential/Candidates/{Name}/brief.md`
 2. **Read the Role file:** Look up the `Req` field and read the corresponding
-   `Knowledge/Roles/*.md` file; check the `**Status:**` field for context.
+   `2-Confidential/Roles/*.md` file. Check the `**Status:**` field for context.
 3. **Include in the briefing:**
    - Candidate's current status, skills, and screening recommendation
    - Role context: hiring manager, domain lead, remaining positions

package/templates/.claude/skills/organize-files/SKILL.md

@@ -1,15 +1,18 @@
 ---
 name: organize-files
-description: Organize, tidy up, and find files in ~/Desktop/ and ~/Downloads/. Use when the user asks to find, organize, clean up, or tidy files on their Mac. Always previews changes before acting and never deletes without explicit confirmation. Extracts entities from document files using the extract-entities skill.
+description: Organize, tidy up, and find files in ~/Desktop/ and ~/Downloads/. Use when the user asks to find, organize, clean up, or tidy files on their Mac. Always previews changes before it acts. Never deletes without explicit confirmation. Extracts entities from document files with the extract-entities skill.
 compatibility: Requires macOS filesystem access
 ---
 
 # Organize Files
 
+Write tier: none (delegates graph writes to extract-entities)
+Frontmatter: none
+
 Organize, tidy up, and find files in `~/Desktop/` and `~/Downloads/`. Always
-previews changes before acting and never deletes without explicit confirmation.
+preview changes before you act. Never delete without explicit confirmation.
 
-After organizing, extract entities from document files by invoking the
+After you organize, extract entities from document files. Invoke the
 **`extract-entities`** skill.
 
 ## Trigger
@@ -29,7 +32,7 @@ Run when the user asks to find, organize, clean up, or tidy files on their Mac.
 
 - Organized files moved to logical subdirectories within `~/Desktop/` and
   `~/Downloads/`
-- Entity extraction triggered on document files via the **`extract-entities`**
+- Entity extraction triggered on document files with the **`extract-entities`**
   skill
 - Summary of actions taken
 
@@ -42,22 +45,23 @@ Run when the user asks to find, organize, clean up, or tidy files on their Mac.
 2. **Organize files** — Move files into logical subfolders
 3. **Tidy up** — Clean up cluttered `~/Desktop/` and `~/Downloads/`
 4. **Create structure** — Set up folder hierarchies
-5. **Extract entities** — After organizing, invoke the **`extract-entities`**
-   skill on document files to populate the knowledge graph
+5. **Extract entities** — After you organize, invoke the
+   **`extract-entities`** skill on document files to populate the knowledge
+   graph
 
 ## Key Principles
 
-**Always preview before acting:**
+**Always preview before you act:**
 
-- Show what files will be affected BEFORE moving/deleting
+- Show which files change BEFORE you move or delete them
 - List proposed changes and ask for confirmation
 
 **Be conservative with destructive operations:**
 
 - Never delete without explicit confirmation
-- Prefer moving to a "to-review" folder over deleting
+- Move to a "to-review" folder rather than delete
 
-## Summarizing Contents
+## Summarize the Contents
 
 Get an overview of both directories:
 
@@ -65,7 +69,7 @@ Get an overview of both directories:
 node scripts/summarize.mjs
 ```
 
-## Finding Files
+## Find Files
 
 ```bash
 find ~/Downloads -maxdepth 1 -name "*.pdf" -type f
@@ -76,7 +80,7 @@ find ~/Downloads -maxdepth 1 -type f -mtime +30    # older than 30 days
 find ~/Desktop -maxdepth 1 \( -name "Screenshot*" -o -name "Screen Shot*" \)
 ```
 
-## Organizing by File Type
+## Organize by File Type
 
 Organize a directory into type-based subdirectories (Documents, Images,
 Archives, Installers, Screenshots):
@@ -86,13 +90,13 @@ node scripts/organize-by-type.mjs ~/Downloads
 node scripts/organize-by-type.mjs ~/Desktop
 ```
 
-The script creates subdirectories and moves matching files. It does NOT delete
-anything.
+The script creates subdirectories and moves the files that match. It does NOT
+delete anything.
 
 ## Entity Extraction
 
-After organizing files, identify document files that may contain entity
-information (people, organizations, projects, topics) and invoke the
+After you organize the files, identify document files that may contain entity
+information (people, organizations, projects, topics). Then invoke the
 **`extract-entities`** skill to process them.
 
 ### Which files to send for extraction
@@ -103,8 +107,8 @@ information (people, organizations, projects, topics) and invoke the
 
 ### How to invoke
 
-After organizing, collect the paths of document files and invoke the
-**`extract-entities`** skill, passing the file paths as ad-hoc file inputs.
+After you organize, collect the paths of the document files. Then invoke the
+**`extract-entities`** skill and pass the file paths as ad-hoc file inputs.
 
 ## Output Format
 
@@ -141,10 +145,11 @@ Entity extraction: invoked extract-entities on 12 document files
 
 ## Safety Rules
 
-1. **Never delete without permission** — "cleanup" means organize, not delete
+1. **Never delete without permission** — "cleanup" means organize. It does not
+   mean delete
 2. **Don't touch system folders** — /System, /Library, /Applications
-3. **Don't touch hidden files** — files starting with `.` unless asked
+3. **Don't touch hidden files** — files that start with `.` unless asked
 4. **Limit scope** — only operate on `~/Desktop/` and `~/Downloads/`
-5. **Limit depth** — use `-maxdepth 1` unless user wants recursive
-6. **Show before doing** — always preview first
+5. **Limit depth** — use `-maxdepth 1` unless the user wants recursive
+6. **Show before you act** — always preview first
 7. **Quote paths** — handle spaces: `"$HOME/My Documents"`

package/templates/.claude/skills/organize-files/scripts/organize-by-type.mjs

@@ -2,10 +2,11 @@
 /**
  * Organize files in a directory by type into subdirectories.
  *
- * Scans the top level of the given directory and moves files into category
- * subdirectories: Screenshots, Documents, Images, Archives, and Installers.
- * Categories are determined by file extension and name prefix. Files that do
- * not match any category are left in place. Does NOT delete anything.
+ * The script scans the top level of the given directory. It moves files into
+ * category subdirectories: Screenshots, Documents, Images, Archives, and
+ * Installers. The file extension and the name prefix set the category. The
+ * script leaves a file in place if it matches no category. It does NOT delete
+ * anything.
  */
 
 import {

package/templates/.claude/skills/organize-files/scripts/summarize.mjs

@@ -2,10 +2,10 @@
 /**
  * Summarize the contents of ~/Desktop/ and ~/Downloads/.
  *
- * Counts top-level files in both directories by type (Screenshots, PDFs,
- * Images, Documents, Archives, Installers, Other) and prints a human-readable
- * table for each. Used by the organize-files skill to preview directory
- * contents before organizing.
+ * The script counts top-level files in both directories by type
+ * (Screenshots, PDFs, Images, Documents, Archives, Installers, Other). It
+ * prints a human-readable table for each directory. The organize-files skill
+ * uses this script to preview directory contents before it organizes them.
  */
 
 import { existsSync, readdirSync, statSync } from "node:fs";