fdeops 3.15.1 → 3.15.2

package/bin/fde.js

@@ -1134,7 +1134,7 @@ function cmdResume(args) {
     const fdeDir = path.join(engRoot, '.fde')
     const existed = fs.existsSync(fdeDir)
 
-    // Optional stubs (AI eval pack, …) stay in templates/ for copy-on-use — not day-1 scaffold.
+    // Optional stubs (AI eval pack, …) stay in templates/ for copy-on-use - not day-1 scaffold.
     const SKIP_INIT_TEMPLATES = new Set(['evals.md'])
     const fillTemplates = (destFde) => {
       for (const f of fs.readdirSync(tpl)) {
@@ -1381,7 +1381,7 @@ function setContextPhase(eng, phase) {
 // as one dated debrief block. contact: lines may carry an inline [signal:x]
 // token anywhere in the text - preserved verbatim so computeSignals can trust it.
 // --smart: thin heuristic propose (existing prefixes + light keywords). Not a
-// brain — the agent rewrites .debrief-propose with prefixes; --apply commits.
+// brain - the agent rewrites .debrief-propose with prefixes; --apply commits.
 // --dry-run prints the routing without writing anything.
 function inferContactSignal(text) {
   const t = String(text)
@@ -1392,7 +1392,7 @@ function inferContactSignal(text) {
 }
 
 function looksLikePersonLine(text) {
-  // "Denise …" / "Randy opened…" — capitalized subject + field verb.
+  // "Denise …" / "Randy opened…" - capitalized subject + field verb.
   return /^[A-Z][a-z]{1,20}\b/.test(text) &&
     /\b(helping|quiet|skipped|said|will|opened|resistant|champion|warm|cold|unresponsive|demo|sheet|slack)\b/i.test(text)
 }
@@ -1688,7 +1688,7 @@ function cmdDebrief(args) {
 
 // Pull sink: stage raw artifacts outside the memory ledger, then reuse debrief
 // propose/apply. Never writes .fde/ until the FDE confirms apply. Source SaaS
-// (Granola/Gmail/…) is not here — only staging + the existing confirm gate.
+// (Granola/Gmail/…) is not here - only staging + the existing confirm gate.
 function inboxDir(eng) {
   return path.join(path.dirname(eng), '.inbox')
 }
@@ -1863,7 +1863,7 @@ function cmdIngest(args) {
   console.log(`staged → ${dest}`)
   console.log(`id: ${id}`)
   console.log('next:   fde ingest propose ' + id)
-  console.log('(does not write .fde/ — confirm via propose → apply)')
+  console.log('(does not write .fde/ - confirm via propose → apply)')
 }
 
 function cmdReceipts(args) {
@@ -2157,7 +2157,7 @@ function collectDoctorIssues(eng) {
     }
     if (engagementTouchesAI(eng) && !hasEvalReceipt(eng)) {
       issues.push(
-        `phase is ${s.phase} with AI in scope but no eval receipt (evals.md Verdict or delivery Eval / Ship receipts) — required before green ship/close`
+        `phase is ${s.phase} with AI in scope but no eval receipt (evals.md Verdict or delivery Eval / Ship receipts) - required before green ship/close`
       )
     }
   }
@@ -2302,7 +2302,7 @@ function hasValueBucket(eng) {
 // "pending review", "TBD.", "n/a (blocked)" and "..." are all the same thing an
 // FDE means by an empty cell - nagging about them teaches people to ignore doctor.
 const PENDING_CELL_RE =
-  /^(?:pending|tbd|to ?be ?(?:measured|confirmed|determined)|n\s*\/\s*a|na|none|unknown|not measured|\?+|\.{2,}|…|-+|—+|–+)(?:[^\w].*)?$/i
+  /^(?:pending|tbd|to ?be ?(?:measured|confirmed|determined)|n\s*\/\s*a|na|none|unknown|not measured|\?+|\.{2,}|…|-+|-+|-+)(?:[^\w].*)?$/i
 
 function parseValueLedger(eng) {
   const ledger = stripTemplateNoise(sectionBody(readClean(eng, 'delivery.md'), 'Value ledger') || '')
@@ -2359,7 +2359,7 @@ function valueLedgerStatusLines(eng, opts = {}) {
   return lines
 }
 
-// AI in scope for ship/close hygiene — delivery/decisions/trust evidence only.
+// AI in scope for ship/close hygiene - delivery/decisions/trust evidence only.
 // Do not scan terrain.md: its template headers mention LLM and would false-positive every ship.
 function engagementTouchesAI(eng) {
   const trust = readClean(eng, 'trust-profile.md')
@@ -2376,7 +2376,7 @@ function hasEvalReceipt(eng) {
   const evalsPath = path.join(eng, 'evals.md')
   if (fs.existsSync(evalsPath)) {
     const e = stripTemplateNoise(readClean(eng, 'evals.md'))
-    // Empty G1 stub + "Pass / fail" heading is not a receipt — need a real verdict/run/result.
+    // Empty G1 stub + "Pass / fail" heading is not a receipt - need a real verdict/run/result.
     if (/\*\*Verdict:\*\*\s*SHIP\b/i.test(e) || /(?:^|\n)\s*-\s*\*\*Verdict:\*\*\s*SHIP\b/i.test(e)) return true
     if (/\bLast run:\s*\d{4}-\d{2}-\d{2}/i.test(e)) return true
     if (/\|\s*G\d+\s*\|[^|\n]+\|[^|\n]+\|[^|\n]+\|[^|\n]+\|\s*pass\s*\|/i.test(e)) return true
@@ -2397,7 +2397,7 @@ function hygieneTriageLines(eng) {
   if (!issues.length) return []
   const top = issues[0].replace(/\s+/g, ' ').trim().slice(0, 72)
   return [
-    `  hygiene: ${issues.length} issue(s) — ${top}${issues[0].length > 72 ? '…' : ''}`,
+    `  hygiene: ${issues.length} issue(s) - ${top}${issues[0].length > 72 ? '…' : ''}`,
     '    → say "@fde clean up the fieldbook" when ready (agent runs fde doctor; nothing auto-rewrites)',
   ]
 }
@@ -2494,7 +2494,7 @@ function cmdPrep(args) {
   if (!eng) { console.error('no engagement - run: fde resume --init <name>'); process.exit(2) }
   const label = args.join(' ').trim() || 'next meeting'
   // Grounded brief: only text already in .fde/. No invention (Rowboat meeting-prep rule).
-  console.log(`MEETING PREP — ${label}`)
+  console.log(`MEETING PREP - ${label}`)
   console.log('(grounded in local .fde/ only - if a fact is missing, it is missing)\n')
   console.log(resumeTriage(eng))
   const owner = readOwner(eng)
@@ -2504,7 +2504,7 @@ function cmdPrep(args) {
   const people = extractStakeholders(eng).slice(0, 8)
   console.log('\nStakeholders (table + signal history)')
   if (!people.length) console.log('  (none yet - log contacts with --signal)')
-  else people.forEach(p => console.log(`  [${p.signal}] ${p.name}${p.role ? ` — ${p.role}` : ''}${p.note ? ` · ${p.note.slice(0, 60)}` : ''}`))
+  else people.forEach(p => console.log(`  [${p.signal}] ${p.name}${p.role ? ` - ${p.role}` : ''}${p.note ? ` · ${p.note.slice(0, 60)}` : ''}`))
 
   const risks = extractRisks(eng).slice(0, 5)
   console.log('\nOpen risks (table + dated bullets)')
@@ -2537,16 +2537,16 @@ function cmdGarden(args) {
   if (gitHealth.ok) {
     console.log('TIDY (contract: no new facts · no deleted substance · reversible via memory git)')
   } else if (gitHealth.reason === 'broken') {
-    console.log('TIDY (contract: no new facts · no deleted substance · ⚠ memory git BROKEN — NOT reversible until ledger is repaired)')
+    console.log('TIDY (contract: no new facts · no deleted substance · ⚠ memory git BROKEN - NOT reversible until ledger is repaired)')
   } else {
-    console.log('TIDY (contract: no new facts · no deleted substance · ⚠ memory not git-versioned — NOT reversible)')
+    console.log('TIDY (contract: no new facts · no deleted substance · ⚠ memory not git-versioned - NOT reversible)')
   }
   console.log(resumeTriage(eng))
   if (!gitHealth.ok) {
     console.log(
       gitHealth.reason === 'broken'
         ? '\n⚠ ledger is UNVERSIONED (corrupt .git). Repair before trusting tidy apply: mv .fde/.git .fde/.git.broken && run any fde write to re-init.'
-        : '\n⚠ no memory git — tidy apply cannot create a reversible commit until the ledger exists.'
+        : '\n⚠ no memory git - tidy apply cannot create a reversible commit until the ledger exists.'
     )
   }
   const proposals = []
@@ -2564,7 +2564,7 @@ function cmdGarden(args) {
     proposals.push({
       id: 'dedupe-risks',
       kind: 'apply',
-      text: `Consolidate ${dupes.length} duplicate open-risk cluster(s) (e.g. "${sample}${sample.length >= 50 ? '…' : ''}") — keep first, retire echoes`,
+      text: `Consolidate ${dupes.length} duplicate open-risk cluster(s) (e.g. "${sample}${sample.length >= 50 ? '…' : ''}") - keep first, retire echoes`,
       clusters: dupes,
     })
   }

package/bin/lib/memory.js

@@ -152,7 +152,7 @@ function createMemoryApi(deps) {
   }
 
   // True only when .git exists AND can resolve HEAD. A corrupt ledger (broken
-  // HEAD / missing objects) still has a .git directory — existsSync alone lied.
+  // HEAD / missing objects) still has a .git directory - existsSync alone lied.
   function memoryGitHealthy(eng) {
     if (!eng) return { ok: false, reason: 'missing' }
     if (!fs.existsSync(path.join(eng, '.git'))) return { ok: false, reason: 'missing' }

package/bin/lib/render.js

@@ -438,7 +438,7 @@ function todayViewHtml({ today, total, attentionCount, highRiskTotal, todayQueue
 <h1 class="fb-h1">Today</h1>
 <div class="fb-meta-line">${escapeHtml(today)} &middot; ${total} engagement${total === 1 ? '' : 's'} &middot; ${attentionCount} need you &middot; ${highRiskTotal} high risk${highRiskTotal === 1 ? '' : 's'} open</div>
 <div class="fb-block">
-<div class="fb-sec">Queue — next action per client, worst first</div>
+<div class="fb-sec">Queue - next action per client, worst first</div>
 ${todayQueue}
 </div>
 ${flagsHtml ? `<div class="fb-block">

package/bin/lib/trust.js

@@ -95,7 +95,7 @@ function createTrustApi(deps) {
 
   function nextActionLine(ctx) {
     // lastNonEmpty: template ships an empty ## Next action; agents often append a
-    // second heading with the real bullet — first-match would report "(none set)".
+    // second heading with the real bullet - first-match would report "(none set)".
     const body = sectionBody(ctx, 'Next action', { lastNonEmpty: true })
     for (const raw of body.split('\n')) {
       const t = raw.trim().replace(/^[-*]\s+/, '')

package/mcp/README.md

@@ -9,7 +9,7 @@ FDEOps MCP servers follow a **pluggable source model**: core owns the **sink**,
 | **Source** | FDE configures separately | Granola, Slack, Notion, Gmail, file |
 | **Sink** | FDEOps (`fdeops-ingest`) | stage → propose → apply into engagement memory |
 
-Source MCPs fetch raw text from SaaS APIs using credentials the FDE manages. The ingest MCP never stores OAuth tokens or calls external services — it only shells out to the local `fde` CLI.
+Source MCPs fetch raw text from SaaS APIs using credentials the FDE manages. The ingest MCP never stores OAuth tokens or calls external services - it only shells out to the local `fde` CLI.
 
 ## Ground loop
 
@@ -28,7 +28,7 @@ Source MCP(s)          fdeops-ingest MCP           fde CLI
 1. Agent pulls from whichever source MCPs are configured.
 2. Agent stages raw content via `ingest_stage` (with `source` provenance).
 3. Agent proposes routing via `ingest_propose`; FDE confirms.
-4. Agent applies via `ingest_apply` — nothing writes `.fde/` unreviewed.
+4. Agent applies via `ingest_apply` - nothing writes `.fde/` unreviewed.
 
 ## Packages
 

package/mcp/fdeops-ingest/README.md

@@ -2,9 +2,9 @@
 
 Thin stdio MCP server for the FDEOps **ingest sink** only: **stage → propose → apply**.
 
-This package shells out to the local `fde` CLI. It never calls SaaS APIs. Source MCPs (Granola, Slack, Notion, etc.) are **separate** — you add those in your own `mcp.json`.
+This package shells out to the local `fde` CLI. It never calls SaaS APIs. Source MCPs (Granola, Slack, Notion, etc.) are **separate** - you add those in your own `mcp.json`.
 
-**Prefer the CLI when this workspace is bound:** `fde ingest stage|list|propose|apply`. Use this MCP when the host did not start in a bound workspace — then pass `engagement` (path to `.fde/` from `fde resume --bind`) on every tool call.
+**Prefer the CLI when this workspace is bound:** `fde ingest stage|list|propose|apply`. Use this MCP when the host did not start in a bound workspace - then pass `engagement` (path to `.fde/` from `fde resume --bind`) on every tool call.
 
 ## Tools
 
@@ -70,12 +70,12 @@ Or after `npm link` in this directory:
 
 ## Daily loop (with separate source MCPs)
 
-1. **Fetch** — Use your source MCP (e.g. Granola, Gmail) to pull raw text. FDEOps does not bundle these.
-2. **Stage** — `ingest_stage` with `content`, `source` (e.g. `"granola"`), optional `title`.
-3. **List** — `ingest_list` to see staged items in `.inbox/`.
-4. **Propose** — `ingest_propose` with the staged `id`; agent reviews `.debrief-propose`.
-5. **Confirm** — FDE approves the proposal in chat.
-6. **Apply** — `ingest_apply` writes dated facts into `.fde/` with provenance.
+1. **Fetch** - Use your source MCP (e.g. Granola, Gmail) to pull raw text. FDEOps does not bundle these.
+2. **Stage** - `ingest_stage` with `content`, `source` (e.g. `"granola"`), optional `title`.
+3. **List** - `ingest_list` to see staged items in `.inbox/`.
+4. **Propose** - `ingest_propose` with the staged `id`; agent reviews `.debrief-propose`.
+5. **Confirm** - FDE approves the proposal in chat.
+6. **Apply** - `ingest_apply` writes dated facts into `.fde/` with provenance.
 
 Raw artifacts stay in `.inbox/`; the system of record (`.fde/`) stays thin and reviewed.
 

package/mcp/fdeops-ingest/package.json

@@ -1,6 +1,6 @@
 {
   "name": "fdeops-ingest-mcp",
-  "version": "3.15.1",
+  "version": "3.15.2",
   "private": true,
   "description": "Thin stdio MCP sink for FDEOps ingest (stage → propose → apply). Zero runtime dependencies.",
   "bin": {

package/mcp/fdeops-ingest/server.js

@@ -2,7 +2,7 @@
 'use strict'
 
 /**
- * fdeops-ingest MCP — thin stdio sink for FDEOps ingest.
+ * fdeops-ingest MCP - thin stdio sink for FDEOps ingest.
  * Shells out to local `fde` CLI only. Never calls SaaS.
  * MCP stdio transport: newline-delimited JSON-RPC 2.0
  * (Content-Length frames are accepted on input).

package/mcp/recipes/README.md

@@ -4,13 +4,13 @@ FDEOps does **not** bundle Granola / Slack / Notion OAuth and does **not** push
 
 **Daily (no MCP):** paste notes to `@fde debrief`, or drop a file ([file.md](./file.md)).
 
-**Pull (optional):** you add a **source** MCP. The agent fetches text, then runs `fde ingest` in this bound workspace (stage → propose → you confirm → apply). The `fdeops-ingest` MCP is optional — only if you are not using the CLI from a bound workspace.
+**Pull (optional):** you add a **source** MCP. The agent fetches text, then runs `fde ingest` in this bound workspace (stage → propose → you confirm → apply). The `fdeops-ingest` MCP is optional - only if you are not using the CLI from a bound workspace.
 
 | Recipe | When |
 |--------|------|
 | [file.md](./file.md) | Transcript / export already on disk, or paste |
 | [granola.md](./granola.md) | Meeting transcripts via a notes MCP (or export) |
-| [slack.md](./slack.md) | Pull a thread/channel as text — never post |
+| [slack.md](./slack.md) | Pull a thread/channel as text - never post |
 | [notion.md](./notion.md) | Read a Notion page (or export markdown) |
 
 **Natural language:** `@fde I want to connect Granola` (or Slack / Notion) → `skills/fde/references/ingest-connect.md`.

package/mcp/recipes/file.md

@@ -1,6 +1,6 @@
 # Recipe: local file / paste (no source MCP)
 
-**Use when:** you already have a transcript, `.eml`, or export on disk — or you paste into chat. This is the default FDE path.
+**Use when:** you already have a transcript, `.eml`, or export on disk - or you paste into chat. This is the default FDE path.
 
 ## Setup
 

package/mcp/recipes/granola.md

@@ -1,6 +1,6 @@
 # Recipe: Granola-shaped meeting transcripts
 
-**Use when:** meeting notes live in Granola (or a similar notes MCP). FDEOps does not ship a Granola server — you add whichever MCP/export path you trust.
+**Use when:** meeting notes live in Granola (or a similar notes MCP). FDEOps does not ship a Granola server - you add whichever MCP/export path you trust.
 
 Daily path if the notes are already in chat or on disk: paste to `@fde debrief` or [file.md](./file.md). This recipe is only for **pull**.
 
@@ -8,7 +8,7 @@ Daily path if the notes are already in chat or on disk: paste to `@fde debrief`
 
 1. Enable a **Granola (or notes) MCP** in Cursor/Claude per that product’s docs.
 2. Reload MCP / restart the host.
-3. Test: `@fde what can you pull?` — notes-source tools should appear.
+3. Test: `@fde what can you pull?` - notes-source tools should appear.
 
 The sink is **`fde ingest` in this bound workspace.** You do not need `fdeops-ingest` MCP for daily pull.
 
@@ -40,15 +40,15 @@ Replace command/args with whatever the real Granola MCP documents. FDEOps only n
 
 ## Agent steps
 
-1. Capability check — notes-source tools present?
+1. Capability check - notes-source tools present?
 2. Fetch transcript text (ask which meeting if ambiguous).
 3. `fde ingest stage --source granola --title "<short>"` then propose → confirm → apply.
-4. Extract decisions/risks/next — do not dump the raw transcript into `.fde/`.
+4. Extract decisions/risks/next - do not dump the raw transcript into `.fde/`.
 
 ## Common fails
 
 | Symptom | Fix |
 |---------|-----|
-| No Granola tools | Source MCP not loaded — they save + reload |
+| No Granola tools | Source MCP not loaded - they save + reload |
 | Wrong meeting | One clarifying question, then fetch |
 | Wrong engagement | `fde resume` in this workspace before staging |

package/mcp/recipes/notion.md

@@ -1,6 +1,6 @@
 # Recipe: Notion docs / meeting notes
 
-**Use when:** useful engagement notes live in Notion. FDEOps does not ship a Notion server — use a Notion MCP (or export markdown). We do not write back to Notion.
+**Use when:** useful engagement notes live in Notion. FDEOps does not ship a Notion server - use a Notion MCP (or export markdown). We do not write back to Notion.
 
 ## Setup (once)
 
@@ -36,7 +36,7 @@ The sink is **`fde ingest` in this bound workspace.** `fdeops-ingest` MCP is opt
 
 ## Agent steps
 
-1. Capability check — Notion read tools present?
+1. Capability check - Notion read tools present?
 2. Fetch page/block text (ask which page if ambiguous).
 3. `fde ingest stage --source notion --title "<short>"` → propose → confirm → apply.
 

package/mcp/recipes/slack.md

@@ -8,7 +8,7 @@ You add whatever Slack MCP your host already supports. We only accept **text you
 
 1. Enable a **Slack MCP** (official or community) with read access to the threads you need.
 2. Reload MCP / restart the host.
-3. Test: `@fde what can you pull?` — Slack fetch tools should appear. The FDEOps **CLI** (`fde ingest`) is the sink if this workspace is bound; you do not need `fdeops-ingest` MCP for daily use.
+3. Test: `@fde what can you pull?` - Slack fetch tools should appear. The FDEOps **CLI** (`fde ingest`) is the sink if this workspace is bound; you do not need `fdeops-ingest` MCP for daily use.
 
 ### Example mcp.json shape (illustrative)
 
@@ -40,10 +40,10 @@ Optional sink MCP (only if you are not running `fde ingest` from this workspace)
 
 ## Agent steps
 
-1. Capability check — Slack **read** tools present? If not → this recipe, then stop.
+1. Capability check - Slack **read** tools present? If not → this recipe, then stop.
 2. Fetch the thread/channel as **text** (ask which channel/thread if ambiguous).
 3. `fde ingest stage --source slack --title "<short>"` (CLI in this bound workspace).
-4. Propose → FDE confirms → apply. Extract decisions/risks/asks — do not dump the thread into `.fde/`.
+4. Propose → FDE confirms → apply. Extract decisions/risks/asks - do not dump the thread into `.fde/`.
 
 ## Never
 
@@ -55,7 +55,7 @@ Optional sink MCP (only if you are not running `fde ingest` from this workspace)
 
 | Symptom | Fix |
 |---------|-----|
-| No Slack tools | Source MCP not loaded — they save + reload; we cannot silent-install |
-| Missing channel | Token/scopes cannot read that workspace — their Slack admin, not FDEOps |
+| No Slack tools | Source MCP not loaded - they save + reload; we cannot silent-install |
+| Missing channel | Token/scopes cannot read that workspace - their Slack admin, not FDEOps |
 | Huge dump | Stage full text in `.inbox/`; apply only short dated facts |
 | Wrong client | Bind this workspace (`fde resume`) before staging |

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "fdeops",
-  "version": "3.15.1",
+  "version": "3.15.2",
   "description": "Forward deployed engineering skills for AI coding agents. Your agent forgets the client every morning - the sponsor, the promise, who signed off. FDEOps keeps that as dated markdown on your laptop: one @fde skill, a deterministic local CLI, and hooks that make it automatic. Claude Code plugin and any agent that loads skills.",
   "bin": {
     "fdeops": "bin/install.js",

package/plugin.json

@@ -1,7 +1,7 @@
 {
   "$schema": "https://agent-plugins.org/schemas/1.0.0/plugin.schema.json",
   "name": "fdeops",
-  "version": "3.15.1",
+  "version": "3.15.2",
   "description": "Forward deployed engineering skills for AI coding agents: per-client memory in local .fde/ files, one @fde skill. Local-only, no network.",
   "author": {
     "name": "Subash Natarajan",

package/skills/fde/SKILL.md

@@ -1,23 +1,23 @@
 ---
 name: fde
-description: Keeps engagement memory for client work - sponsor, promise, what shipped, who accepted it. Use when the human names a client, customer or stakeholder. Use when they debrief a meeting or paste notes from one. Use when they ask what was agreed, or want dates and receipts. Use when they prep a client meeting or readout, when scope or trust shifts, or when they say @fde. Route the phase and run the local fde CLI (or npx --yes fdeops if it is not installed); never ask them to type commands. Not for ordinary code edits, unit tests, refactors or commits.
+description: Keeps the engagement record for client work. Use when they name a client or stakeholder. Use when they debrief a meeting or paste notes. Use when they ask what was agreed. Use when they run a POC, slice a feature on the client's codebase, prove it on their staging, or need evals before a model acts. Use when they prep a readout, when trust shifts, or they say @fde. Route and run the local fde CLI (or npx --yes fdeops). Never ask them to type commands. Not for ordinary code edits in an unbound repo.
 ---
 
 # @fde
 
 ## Purpose
 
-The **engagement record** for one client. One skill; six stages (land → close). You pick the method; they never pick a skill. Confirm, then write `.fde/`. The host agent writes the TypeScript; you log what they got. The artifact is the memory.
+The **engagement record** for one client, from first meeting to signed outcome. One skill; six stages (land → close). You route; they never pick a skill. Confirm, then write `.fde/`. The workspace still compiles and commits. `@fde` does not leave.
 
 ## When to use
 
 - They named a client, pasted notes, or asked what was agreed
 - The brief feels wrong, a sponsor went quiet, or Friday needs the ledger
-- Unbound — ask the name once, then **you** run `fde resume --init`
+- Unbound - ask the name once, then **you** run `fde resume --init`
 
 ## When NOT to use
 
-TypeScript errors, unit tests, refactors, git commits, generic debug: **host agent**. Agreed slice + code: implement in the host, then `fde log delivery`.
+A one-line typo or compile error in a file that will not ship. On a bound client: stay here for POC, slice, characterisation, eval, go-live, rollback, and acceptance.
 
 ## Use these first
 
@@ -25,14 +25,26 @@ TypeScript errors, unit tests, refactors, git commits, generic debug: **host age
 |---------|-----------------|---------|-----------|
 | **The brief is wrong** | "If this works, who in their company would have to agree that it worked?" | `fde resume` then discover | `references/discover.md` |
 | **They went quiet** | "Is this a process gap, or a trust problem?" | `fde log contact "…" --signal amber\|red\|green` | `references/rescue.md` |
-| **When did we agree?** | Don't argue from memory. Search the record. | `fde receipts <term>` | — |
-| **What did they get?** | A number nobody signed is claimed, not delivered. | `fde status` | `references/status.md` |
+| **When did we agree?** | Don't argue from memory. Search the record. | `fde receipts <term>` | - |
+| **What's the outcome?** | A number nobody signed is claimed, not delivered. | `fde status` | `references/status.md` |
 
 After a meeting: `fde debrief --smart` → confirm → `--apply`. Walk-in: `fde prep`. Friday: `fde status`.
 
+## Ground loop
+
+On someone else's site the work is not "write code, remember later." Every slice stays on `@fde`:
+
+1. **Name it** in `decisions.md` (plan) or kill it in a day (sketch).
+2. **Characterise their code** before you change it (incremental-build). Their tests, their runner.
+3. **Prove it where they live.** Staging they operate, a screen the signer in `success.md` can reject.
+4. **If a model judges:** `evals.md` Verdict SHIP before the slice is done (eval-pack).
+5. **Log delivery.** Outcome is promised → measured → accepted, not a green CI.
+
+A throwaway file can skip the loop. A client slice cannot.
+
 ## Human surface vs agent plumbing
 
-**FDE (human):** `@fde` + English, or `/brief` `/discover` `/plan` `/ship` `/got` `/close` `/debrief` `/prep` `/quiet` `/agreed` `/status`. Never a skill catalog.
+**FDE (human):** `@fde` + English, or `/brief` `/discover` `/plan` `/ship` `/outcome` `/close` `/debrief` `/prep` `/quiet` `/agreed` `/status`. Never a skill catalog.
 
 **You (agent):** run the CLI. **Never tell the FDE to type** `fde …`. If unbound, you run `fde resume --init` after one question. Never ask them to run the CLI.
 
@@ -42,7 +54,7 @@ Fallbacks: `node ~/.claude/fdeops/fde.js …`, then `npx --yes fdeops …`. Skil
 
 1. `fde resume` (bounded `context.md`). `--full` only if you need the whole log.
 2. **NO ENGAGEMENT:** ask "What should we call this client?" then **you** init. Pasted notes → debrief after bind.
-3. Playback 2–3 lines. `hygiene:` → offer `fde doctor`; **never auto-rewrite**.
+3. Playback 2-3 lines. `hygiene:` → offer `fde doctor`; **never auto-rewrite**.
 4. Route. Read **one** `references/*.md`. Confirm, then write.
 
 Writes need a bind (`FDEOPS_ENGAGEMENT` or registry). Never install fdeops on infrastructure they do not control.
@@ -54,10 +66,10 @@ Writes need a bind (`FDEOPS_ENGAGEMENT` or registry). Never install fdeops on in
 | debrief / pasted notes | `fde debrief --smart` → you rewrite prefixes → confirm → `--apply`. `--smart` is a gate, not a brain. `references/debrief.md` |
 | prep me for … | `fde prep "<label>"` |
 | when did we agree | `fde receipts <term>` |
-| sponsor update / what they got | `fde status` |
+| sponsor update / the outcome | `fde status` |
 | they went quiet | `fde log contact "…" --signal amber\|green\|red` |
 | fieldbook page | `fde dashboard` |
-| clean up the fieldbook | `fde doctor` — never auto-rewrite |
+| clean up the fieldbook | `fde doctor` - never auto-rewrite |
 | scrub a secret | `fde redact <term>` then `--apply` after confirm |
 | pull Granola/Slack/transcript | capability check → `fde ingest stage` → confirm → apply. Never auto-apply. `references/ingest.md` |
 | connect an MCP | `references/ingest-connect.md` |
@@ -69,35 +81,35 @@ Writes need a bind (`FDEOPS_ENGAGEMENT` or registry). Never install fdeops on in
 2. **Deliverable = memory.** The work *is* the `.fde/` file. The reference names which one.
 3. **Evidence.** Every claim has a source. Traceable beats plausible.
 4. **No invented facts.** People, quotes, meetings, numbers: they said it or the repo shows it. Else `unknown - ask: <question>`.
-5. **Session digest** (end of session and before a PR) — thinking, not the chat. Confirm, then write. Never a transcript dump.
+5. **Session digest** (end of session and before a PR) - thinking, not the chat. Confirm, then write. Never a transcript dump.
 
    | Digest beat | Lands in |
    |-------------|----------|
    | **TL;DR** | `context.md` |
-   | **Key decisions & why** | `decisions.md` — skip if none |
+   | **Key decisions & why** | `decisions.md` - skip if none |
    | **Pivot / aha** | `context.md` or `decisions.md` |
    | **Scope + verification** | `delivery.md` if code/PR; else skip |
    | **Gotchas** | `context.md` |
-   | **Next action** | existing `## Next action` — **replace**; never append a second heading |
+   | **Next action** | existing `## Next action` - **replace**; never append a second heading |
 
    Judgment ships in the fieldbook. Raw transcripts stay on the machine. The `session-stop` hook is a thin backstop; **you** write the digest.
 
 6. **One customer, one folder.**
 7. Never drop `## Signal history` or `## Retired` when rewriting those files.
 
-**Don't invent.** Don't tell them to run the CLI. Don't fill `success.md` / `terrain.md` with guesses. Don't ship on "probably fine" — intent vs diff, then pre-blast. Don't grill mid-flow. Don't sync transcripts into git.
+**Don't invent.** Don't tell them to run the CLI. Don't fill `success.md` / `terrain.md` with guesses. Don't ship on "probably fine" - intent vs diff, then pre-blast. Don't grill mid-flow. Don't sync transcripts into git.
 
 ## Data boundary
 
-CLI is local (`git` + files, no network). You see their code only when they point you at it. AI policy unknown → ask before loading code. `<private>` is redacted from CLI/dashboard/hooks — do not open raw private blocks with file tools.
+CLI is local (`git` + files, no network). You see their code only when they point you at it. AI policy unknown → ask before loading code. `<private>` is redacted from CLI/dashboard/hooks - do not open raw private blocks with file tools.
 
 ## Voice
 
-Direct. Their words. No "Certainly." Playback 2–4 lines, then act. One question only when a missing fact changes the next move.
+Direct. Their words. No "Certainly." Playback 2-4 lines, then act. One question only when a missing fact changes the next move.
 
 New embed: sprint / standard / programme changes depth, not which methods exist. Before first code: safe place to break things, plus AI-code policy. Before go-live: who needs to know, what's the rollback. Before a sponsor artifact: as-is or gut-check first.
 
-Muddy signal: name it ("discover or rescue — leaning X"). Never a phase-picker interview. Default: land if new, audit if takeover.
+Muddy signal: name it ("discover or rescue - leaning X"). Never a phase-picker interview. Default: land if new, audit if takeover.
 
 ## Routing - 6 stages
 
@@ -120,7 +132,7 @@ Read **one** reference and follow it. Do not improvise from memory.
 | Don't know the real problem, brief feels wrong, shadow processes | discover | `references/discover.md` |
 | The brief feels too neat, assumptions untested, "we just need…" | assumption-audit | `references/assumption-audit.md` |
 | Multiple use cases competing, "we want to do everything" | use-case-scoring | `references/use-case-scoring.md` |
-| Need to validate a direction, prototype, demo to de-risk | sketch | `references/sketch.md` |
+| Need to validate a direction, prototype, demo to de-risk, **POC**, spike, killer assumption | sketch | `references/sketch.md` |
 
 ### Plan
 
@@ -135,13 +147,13 @@ Read **one** reference and follow it. Do not improvise from memory.
 
 | You hear | Skill | Reference |
 |----------|-------|-----------|
-| Large feature, need visible progress every 2–3 days | incremental-build | `references/incremental-build.md` |
+| Large feature, need visible progress every 2-3 days, slice it, characterise their tests, POC follow-through | incremental-build | `references/incremental-build.md` |
 | What could go wrong, touching shared infrastructure, need to assess impact | blast-radius | `references/blast-radius.md` |
 | Production down, urgent - OR stakeholder gone quiet, trust slipping | rescue | `references/rescue.md` |
 | Ready to deploy, going live, pre-flight check | ship | `references/ship.md` |
 | Review this change, is it safe, does it match what we agreed | review | `references/review.md` |
 | Diff grew / scope creep in the PR / "did we only build what we said" / KEEP JUSTIFY SPLIT DROP | review (+ ship if going live) | `references/review.md` Stage 1 · `references/ship.md` Intent vs diff |
-| Wrap the session / share the thinking / catch teammates up / before I open the PR | (memory contract — session digest) | SKILL.md **On exit** — write TL;DR + decisions/why into `.fde/`; no transcript sync |
+| Wrap the session / share the thinking / catch teammates up / before I open the PR | (memory contract - session digest) | SKILL.md **On exit** - write TL;DR + decisions/why into `.fde/`; no transcript sync |
 | "We can always revert" - need to actually test the escape route | rollback-drill | `references/rollback-drill.md` |
 
 ### Prove
@@ -173,7 +185,7 @@ Read **one** reference and follow it. Do not improvise from memory.
 | Signal | Overlay |
 |--------|---------|
 | AI, ML, LLM, model, embeddings, RAG, agents, fine-tuning, inference, drift | `references/ai.md` |
-| Golden set, eval suite, eval pack, pass/fail before AI ship, HITL gate for model | `references/eval-pack.md` (+ `ai.md`) |
+| Golden set, eval suite, eval pack, pass/fail before AI ship, HITL gate for model, POC the model | `references/eval-pack.md` (+ `ai.md`) |
 | Deck, slides, report, governance framework, compliance pack, ADR, PDF | `references/artifacts.md` |
 | Patient data, PHI, HIPAA, EHR, clinical | `references/healthcare.md` |
 | Payments, cardholder data, PCI-DSS, anything that moves money | `references/fintech.md` |
@@ -184,8 +196,9 @@ Ready to build with no `terrain.md` / plan: discover or plan first. Takeover wit
 ## Principles
 
 - Never ask the FDE to pick a phase. That's your job.
-- Read `context.md` before speaking. One sharp question — never a barrage.
-- Never invent people, meetings, or numbers — `unknown - ask:` beats a polished lie.
+- Ground loop on a bound client: name → characterise → prove where they live → log. Do not hand the slice to a generic coding pack.
+- Read `context.md` before speaking. One sharp question - never a barrage.
+- Never invent people, meetings, or numbers - `unknown - ask:` beats a polished lie.
 - Every phase ends with its artifact written. No artifact, no "done."
 - Evidence on every claim. The FDE will be challenged on these files.
 - Overlays activate on signal, not on request.

package/skills/fde/references/ai.md

@@ -29,7 +29,7 @@ Never start with the most powerful model. Start with the cheapest that meets the
 4. **Does it need fine-tuning?** Only when: you have 500+ high-quality examples, the base model fails consistently on your domain, and the cost of inference at scale justifies the training cost.
 
 **Evaluation method (before choosing):**
-- Build a test set: 50–100 representative inputs with expected outputs.
+- Build a test set: 50-100 representative inputs with expected outputs.
 - Run every candidate model against the test set.
 - Score: accuracy, latency, cost per call, failure modes.
 - The cheapest model that scores above the quality threshold wins.
@@ -38,14 +38,14 @@ Write model selection rationale to `decisions.md`. Include: models tested, test
 
 ## Engagement eval pack (before AI ships)
 
-When any slice touches a model, embeddings, RAG, or an agent: create or update `.fde/evals.md` **before** ship. Full method: `references/eval-pack.md`. This is the engagement-local test set — not unit tests.
+When any slice touches a model, embeddings, RAG, or an agent: create or update `.fde/evals.md` **before** ship. Full method: `references/eval-pack.md`. This is the engagement-local test set - not unit tests.
 
 **Minimum pack (do not grow until the minimum exists):**
-1. **Component + quality bar** — one sentence each; kill switch / fallback named.
-2. **Golden cases** — 5–20 representative inputs with expected outputs and a pass rule. Prefer real production-shaped data (sanitized).
-3. **Failure modes** — at least the silent ones: hallucination/ungrounded, retrieval miss (if RAG), drift, cost runaway.
-4. **Pass/fail** — dated run; Verdict **SHIP** or **NO-SHIP**; critical fails must be 0.
-5. **HITL gate** — which decisions need human review before action (align with `trust-profile.md`). Empty when policy requires review → NO-SHIP.
+1. **Component + quality bar** - one sentence each; kill switch / fallback named.
+2. **Golden cases** - 5-20 representative inputs with expected outputs and a pass rule. Prefer real production-shaped data (sanitized).
+3. **Failure modes** - at least the silent ones: hallucination/ungrounded, retrieval miss (if RAG), drift, cost runaway.
+4. **Pass/fail** - dated run; Verdict **SHIP** or **NO-SHIP**; critical fails must be 0.
+5. **HITL gate** - which decisions need human review before action (align with `trust-profile.md`). Empty when policy requires review → NO-SHIP.
 
 **When to write:** plan seeds the pack; sketch/build grows goldens; ship requires Verdict SHIP and a receipt in `delivery.md` → `## Ship receipts`. Non-AI work skips this file entirely.
 
@@ -59,7 +59,7 @@ When the AI needs to answer questions about the client's data:
 3. **Generate** - chunks + query → LLM → answer with citations
 
 **Common failure modes:**
-- **Chunk size wrong.** Too small = lost context. Too large = noise drowns signal. Start at 500–1000 tokens with 100-token overlap.
+- **Chunk size wrong.** Too small = lost context. Too large = noise drowns signal. Start at 500-1000 tokens with 100-token overlap.
 - **No citation/grounding.** If the model can't point to where it found the answer, you can't verify it. Always require source attribution.
 - **Stale index.** Documents update, embeddings don't. Define the refresh cadence. Real-time for critical data, daily for reference docs.
 - **Retrieval miss.** The right document exists but wasn't retrieved. Test with known-answer queries where the answer IS in the corpus - if retrieval misses these, the embedding model or chunking strategy needs work.

package/skills/fde/references/assumption-audit.md

@@ -76,11 +76,11 @@ Tell the FDE: how many assumptions extracted, how many critical, which ones were
 
 Acme's brief reads cleanly, which is the signal.
 
-Extracted assumptions include one nobody said aloud: *finance would act on an alert*. The whole plan rests on it, and the evidence behind it is a sentence in a kickoff. Blast radius CRITICAL — if false, alerting changes nothing and the engagement delivers a page nobody answers.
+Extracted assumptions include one nobody said aloud: *finance would act on an alert*. The whole plan rests on it, and the evidence behind it is a sentence in a kickoff. Blast radius CRITICAL - if false, alerting changes nothing and the engagement delivers a page nobody answers.
 
 Validation is a test, not a discussion, and it is cheap: send one real failure notification to the finance channel and watch what happens. It goes first because highest blast radius × cheapest test is the killer test.
 
-Result: acked in 40 minutes, by Marco, not finance. Assumption DISPROVED, and the plan changes before six weeks are spent on it — the alert needs a rota with an owner, which is a different piece of work than the one that was funded. `assumptions.md` records the status, the evidence, and the date; the finding is presented to the FDE as a fact base, not as "the brief was wrong".
+Result: acked in 40 minutes, by Marco, not finance. Assumption DISPROVED, and the plan changes before six weeks are spent on it - the alert needs a rota with an owner, which is a different piece of work than the one that was funded. `assumptions.md` records the status, the evidence, and the date; the finding is presented to the FDE as a fact base, not as "the brief was wrong".
 
 ## Principles
 

package/skills/fde/references/blast-radius.md

@@ -26,7 +26,7 @@ CONTAINED  → Only the module you're changing is affected
              Rollback: revert the PR
              Example: changing a utility function with no external callers
 
-ADJACENT   → 2–5 callers or one downstream system affected
+ADJACENT   → 2-5 callers or one downstream system affected
              Rollback: revert the PR + verify downstream
              Example: changing an API response format used by the frontend