fdeops 3.17.0 → 3.20.0

package/README.md

@@ -10,26 +10,28 @@ Skills encode the workflows, quality gates, and judgment Forward Deployed Engine
 
 ## Commands
 
-Each command loads the same `@fde` skill. You never pick from 31 names.
+One command per stage. Skills load automatically.
 
-| What you're doing | Command | Key principle |
-|-------------------|---------|-----------|
-| First week on site | `/brief` | Name who signs done |
-| Find the real problem | `/discover` | Treat the brief as a hypothesis |
-| Sequence the work | `/plan` | Work backwards from done |
-| Ship to their production | `/ship` | One change they can see, then go live with a rollback you have run |
-| Get the number accepted | `/outcome` | Promised, measured, accepted |
-| Hand off so they run it | `/close` | They operate it without you |
+Six commands map to the embed. Each one loads `@fde`, which opens the skill for that moment: a thin brief pulls land, a wrong brief pulls discover, a Friday number pulls readout. Sprint or programme. Greenfield or brownfield. Any industry. You never pick from 30 names.
+
+| Work | Command | Stage | Principle |
+|------|---------|-------|-----------|
+| Engage | `/brief` | Land | Name who signs done |
+| Diagnose | `/discover` | Discover | Treat the brief as a hypothesis |
+| Align | `/plan` | Plan | Work backwards from done |
+| Deliver | `/ship` | Ship | One visible change, then go live |
+| Realize | `/outcome` | Outcome | Promised, measured, accepted |
+| Transfer | `/close` | Close | They operate it without you |
 
 Also:
 
-| What you're doing | Command | Key principle |
-|-------------------|---------|-----------|
-| Sponsor went quiet | `/trust` | Process gap, or they stopped trusting you |
-| When did we agree? | `/receipts` | A dated line, or it did not happen |
-| After a meeting | `/debrief` | Notes into the record |
-| Prep before the meeting | `/prep` | One page from the record |
-| Friday sponsor update | `/readout` | Promised, measured, accepted |
+| Work | Command | Principle |
+|------|---------|-----------|
+| Diagnose trust | `/trust` | Process gap, or they stopped trusting you |
+| Find the receipt | `/receipts` | A dated line, or it did not happen |
+| Capture the meeting | `/debrief` | Notes into the record |
+| Prepare the meeting | `/prep` | One page from the record |
+| Report the outcome | `/readout` | Promised, measured, accepted |
 
 Skills also activate on English: naming a client, running a POC, changing their checkout, going live, asking what was agreed. A throwaway one-liner in an unbound repo can skip `@fde`. Bound client work cannot.
 
@@ -95,67 +97,69 @@ Requires Node.js >= 18. Override: `FDEOPS_ENGAGEMENT`. See [docs/install.md](doc
 
 ## All 30 Skills
 
-The commands above are the entry points. Under the hood, `@fde` activates these 30 skills, each a structured workflow with steps, an artifact, and a checkpoint. You never pick one by name. Full detail: [docs/skills-reference.md](docs/skills-reference.md).
+The catalog. 30 skills spanning the embed. Not prompts - structured workflows with steps, an artifact, and a checkpoint. Type English or a slash command. `@fde` activates the right skill. You never pick one by name.
+
+Full detail: [docs/skills-reference.md](docs/skills-reference.md).
 
-### Land - Brief and trust
+### Land - Engage
 
-| Skill | What It Does | Use When |
+| Skill | What it does | Use when |
 |--------|--------------|----------|
-| [land](skills/fde/references/land.md) | Interrogate the brief, map stakeholders, define success | New client, first meeting, just got the brief |
-| [audit](skills/fde/references/audit.md) | Verify claims, find the load-bearing wall | Taking over, previous consultant left |
-| [who-decides](skills/fde/references/who-decides.md) | Who decides, who blocks, who escalates | Need to know who matters |
-| [earn-trust](skills/fde/references/earn-trust.md) | Observer → trusted; navigate AI policy | Need access or credibility |
-| [hold-scope](skills/fde/references/hold-scope.md) | Scope receipts; the accumulation conversation | "Also can you…", timeline unchanged |
+| [land](skills/fde/references/land.md) | Interrogate the brief | New client, first meeting, just got the brief |
+| [audit](skills/fde/references/audit.md) | Verify inherited claims | Taking over, previous consultant left |
+| [who-decides](skills/fde/references/who-decides.md) | Map decision rights | Need to know who matters |
+| [earn-trust](skills/fde/references/earn-trust.md) | Earn access | Need access or credibility |
+| [hold-scope](skills/fde/references/hold-scope.md) | Hold scope | "Also can you…", timeline unchanged |
 
-### Discover - Find the real problem
+### Discover - Diagnose
 
-| Skill | What It Does | Use When |
+| Skill | What it does | Use when |
 |--------|--------------|----------|
-| [discover](skills/fde/references/discover.md) | Question first, then repo + workaround | Brief feels wrong, shadow processes |
-| [test-assumptions](skills/fde/references/test-assumptions.md) | Untested assumptions by blast radius | Brief feels too neat |
-| [score-use-cases](skills/fde/references/score-use-cases.md) | Value × urgency × alignment / complexity | Everything is P0 |
-| [poc](skills/fde/references/poc.md) | Kill the killer assumption in a day | POC, spike, need to de-risk |
+| [discover](skills/fde/references/discover.md) | Frame the problem | Brief feels wrong, shadow processes |
+| [test-assumptions](skills/fde/references/test-assumptions.md) | Test assumptions | Brief feels too neat |
+| [score-use-cases](skills/fde/references/score-use-cases.md) | Score use cases | Everything is P0 |
+| [poc](skills/fde/references/poc.md) | Validate the solution | POC, spike, need to de-risk |
 
-### Plan - Sequence the work
+### Plan - Align
 
-| Skill | What It Does | Use When |
+| Skill | What it does | Use when |
 |--------|--------------|----------|
-| [plan](skills/fde/references/plan.md) | Backwards from done, Kill if on each PR | What order, what is done |
-| [business-case](skills/fde/references/business-case.md) | Cost of nothing → investment → return | Defend budget or timeline |
-| [three-options](skills/fde/references/three-options.md) | Three genuine options | "What should we do?" |
-| [pick-three](skills/fde/references/pick-three.md) | Pick three from twenty urgents | Everything is urgent |
+| [plan](skills/fde/references/plan.md) | Sequence the work | What order, what is done |
+| [business-case](skills/fde/references/business-case.md) | Build the business case | Defend budget or timeline |
+| [three-options](skills/fde/references/three-options.md) | Generate options | "What should we do?" |
+| [pick-three](skills/fde/references/pick-three.md) | Prioritize three | Everything is urgent |
 
-### Ship - On their repo, then live
+### Ship - Deliver
 
-| Skill | What It Does | Use When |
+| Skill | What it does | Use when |
 |--------|--------------|----------|
-| [ship](skills/fde/references/ship.md) | One change they can see (greenfield or brownfield), proven on their staging, then go live | Building, updating, or going live |
-| [what-breaks](skills/fde/references/what-breaks.md) | Impact from contained → irreversible | Touching shared infrastructure |
-| [rescue](skills/fde/references/rescue.md) | Production fire or trust fire | Down, or they went quiet |
-| [review](skills/fde/references/review.md) | Did we only build what we agreed | Before merge, scope creep |
-| [rollback](skills/fde/references/rollback.md) | Test the escape route before 2am | "We can always revert" |
+| [ship](skills/fde/references/ship.md) | Deliver the increment | Building, updating, or going live |
+| [what-breaks](skills/fde/references/what-breaks.md) | Assess impact | Touching shared infrastructure |
+| [rescue](skills/fde/references/rescue.md) | Resolve the incident | Down, or they went quiet |
+| [review](skills/fde/references/review.md) | Review the change | Before merge, scope creep |
+| [rollback](skills/fde/references/rollback.md) | Rehearse rollback | "We can always revert" |
 
-### Outcome - Get the number accepted
+### Outcome - Realize
 
-| Skill | What It Does | Use When |
+| Skill | What it does | Use when |
 |--------|--------------|----------|
-| [readout](skills/fde/references/readout.md) | Promised → measured → accepted | Friday, sponsor update |
-| [demo-prep](skills/fde/references/demo-prep.md) | One number, five hard questions | Demo or exec walkthrough |
-| [debrief](skills/fde/references/debrief.md) | Meeting notes into the record | Just left a meeting |
-| [board-memo](skills/fde/references/board-memo.md) | Board / sponsor's boss | Justify continued investment |
-| [dashboard](skills/fde/references/dashboard.md) | Portfolio, trust-ordered | All my customers |
-| [ingest](skills/fde/references/ingest.md) | Pull text you confirm | Transcript, Notion, Slack |
-| [connect](skills/fde/references/connect.md) | Wire a source MCP | Connect Granola |
+| [readout](skills/fde/references/readout.md) | Report the outcome | Friday, sponsor update |
+| [demo-prep](skills/fde/references/demo-prep.md) | Prepare the demo | Demo or exec walkthrough |
+| [debrief](skills/fde/references/debrief.md) | Capture the meeting | Just left a meeting |
+| [board-memo](skills/fde/references/board-memo.md) | Brief the board | Justify continued investment |
+| [dashboard](skills/fde/references/dashboard.md) | View the portfolio | All my customers |
+| [ingest](skills/fde/references/ingest.md) | Ingest sources | Transcript, Notion, Slack |
+| [connect](skills/fde/references/connect.md) | Connect a source | Connect Granola |
 
-### Close - They run it
+### Close - Transfer
 
-| Skill | What It Does | Use When |
+| Skill | What it does | Use when |
 |--------|--------------|----------|
-| [close](skills/fde/references/close.md) | Handoff that survives you | Wrapping up |
-| [runbook](skills/fde/references/runbook.md) | Runbook, confidence scoring | They must operate without you |
-| [switch-clients](skills/fde/references/switch-clients.md) | Switch without bleed | 2+ clients |
-| [encode-pattern](skills/fde/references/encode-pattern.md) | If you did it twice, encode it | It will apply again |
-| [red-team](skills/fde/references/red-team.md) | Stress-test before they do | "Poke holes in this" |
+| [close](skills/fde/references/close.md) | Transfer operations | Wrapping up |
+| [runbook](skills/fde/references/runbook.md) | Write the runbook | They must operate without you |
+| [switch-clients](skills/fde/references/switch-clients.md) | Switch engagements | 2+ clients |
+| [encode-pattern](skills/fde/references/encode-pattern.md) | Encode the pattern | It will apply again |
+| [red-team](skills/fde/references/red-team.md) | Challenge the plan | "Poke holes in this" |
 
 Overlays (on signal, not on request): [ai](skills/fde/references/ai.md) · [artifacts](skills/fde/references/artifacts.md) · [fintech](skills/fde/references/fintech.md) · [healthcare](skills/fde/references/healthcare.md) · [gov](skills/fde/references/gov.md) · [eval-pack](skills/fde/references/eval-pack.md)
 
@@ -174,7 +178,7 @@ One skill. One reference file per situation. One folder per client.
   skills/fde/SKILL.md          hosts load this one file
            │  routes. you never pick a skill by name
            ▼
-  references/land.md           one workflow, then stop
+  references/land.md           one skill, then stop
            │
            ▼
   fde CLI (local)              dates, gates, redacts. no network
@@ -183,11 +187,13 @@ One skill. One reference file per situation. One folder per client.
   ~/fde-engagements/<client>/.fde/
 ```
 
-- **Process, not prose.** Each reference is a workflow with an artifact and a checkpoint, not a tip sheet.
-- **Ground loop.** Name → characterise → prove where they live → go live → log. The workspace compiles; `@fde` stays.
-- **You confirm.** Nothing is written until you say so.
-- **Progressive disclosure.** `SKILL.md` is the entry point. One `references/*.md` loads when routed.
-- **Local CLI.** Writes and status cost zero model tokens. The AI coding agent runs it.
+**One skill routes.** Hosts load `@fde`. It reads the situation and opens one `references/*.md`. Slash commands and English both land here. You never pick a skill by name.
+
+**Evidence, not memory.** Promised → measured → accepted. A dated line in `.fde/`, or it did not happen. Nothing is done on vibes.
+
+**Confirm before write.** Local CLI: git and files, no network. `.fde/` on your laptop. The AI coding agent runs the command. You confirm. Then it is on the record.
+
+**Progressive disclosure.** `SKILL.md` is the entry. One skill file loads when routed. Writes and status cost zero model tokens.
 
 Change hosts, install `@fde` on the new one, bind if needed, keep talking. The record is not inside any vendor.
 
@@ -263,9 +269,9 @@ fdeops/
 
 ## Why FDEOps?
 
-AI coding agents are built for a repo, not for a client. They forget the sponsor, the promise, who can say yes, and whether anyone accepted the number. Monday morning they start from the ticket again.
+AI coding agents are built for a repo, not for a client. Left alone they skip who signs done, whether the brief is true, and whether anyone accepted the number. Monday morning they start from the ticket again.
 
-FDEOps is what you take on site. One `@fde` skill runs the embed from discovery to signed outcome: POC, their codebase, go-live, eval when a model judges, promised → measured → accepted. A local CLI dates every decision. `.fde/` is markdown on your laptop. You confirm; then it is on the record.
+FDEOps is the catalog you take on site. One `@fde` skill runs the embed from discovery to signed outcome: POC, their codebase, go-live, eval when a model judges, promised → measured → accepted. A local CLI dates every decision. `.fde/` is markdown on your laptop. You confirm; then it is on the record.
 
 ---
 
@@ -304,6 +310,7 @@ Local only - `git` + files, no network, no telemetry. Plain markdown. The model
 
 ## Principles
 
+- **One map** - any scale, greenfield or brownfield, any industry. Overlays carry the vertical
 - **The artifact is the memory** - producing the work and recording it are one action
 - **Ground loop** - name the change, characterise their code, prove it on their staging, go live, log the outcome
 - **Skills, not autonomy** - the kit says what to check; judgment stays yours

package/adapters/AGENTS.md

@@ -6,7 +6,7 @@ You are the AI coding agent for a **Forward Deployed Engineer (FDE)** - the huma
 
 When the FDE types **`@fde`**, names a client, pastes meeting notes, asks what was agreed, or describes embed work (quiet sponsor, brief feels wrong, Friday update) - load the skill. If `fde resume` says NO ENGAGEMENT: ask the client name once, then **you** run `fde resume --init <slug>`. Never tell them to type it.
 
-Do **not** load `@fde` for a one-line typo in an unbound repo. On a bound client, stay on `@fde` for POC, small PRs, characterisation, proof on their staging, eval, and go-live.
+Do **not** load `@fde` for a one-line typo in an unbound repo. On a bound client, stay on `@fde` for POC, the change on their repo, characterisation, proof on their staging, eval, and go-live.
 
 - Skill (single source of truth): `~/.claude/skills/fde/SKILL.md`
 - **Never ask the FDE to pick a skill.** Read the situation, route silently, do the work.

package/adapters/GEMINI.md

@@ -6,7 +6,7 @@ Context for Gemini CLI when assisting a **Forward Deployed Engineer (FDE)** - th
 
 When the FDE types **`@fde`**, names a client, pastes meeting notes, asks what was agreed, or describes embed work (quiet sponsor, brief feels wrong, Friday update) - load the skill. If `fde resume` says NO ENGAGEMENT: ask the client name once, then **you** run `fde resume --init <slug>`. Never tell them to type it.
 
-Do **not** load `@fde` for a one-line typo in an unbound repo. On a bound client, stay on `@fde` for POC, small PRs, characterisation, proof on their staging, eval, and go-live.
+Do **not** load `@fde` for a one-line typo in an unbound repo. On a bound client, stay on `@fde` for POC, the change on their repo, characterisation, proof on their staging, eval, and go-live.
 
 - Skill (single source of truth): `~/.claude/skills/fde/SKILL.md`
 - **Never ask the FDE to pick a skill.** Read the situation, route silently, do the work.

package/adapters/LOCAL-LLM.md

@@ -4,7 +4,7 @@ Use fdeops with **any local model** - Ollama, LM Studio, llama.cpp, vLLM, Open W
 
 ## Why it works
 
-fdeops is a SKILL.md file + markdown memory + a Node.js CLI. It calls no external API. The AI does the methodology; the CLI does the mechanics. Any model that can read a markdown system prompt can run fdeops.
+fdeops is a SKILL.md file + markdown memory + a Node.js CLI. It calls no external API. The AI does the skills; the CLI does the mechanics. Any model that can read a markdown system prompt can run fdeops.
 
 ## Setup
 
@@ -62,12 +62,12 @@ The model reads SKILL.md, routes to the right skill, and produces artifacts in y
 
 ## Model size recommendations
 
-The methodology is detailed (30 skills, routing logic, evidence format, memory contract). Larger models handle it better:
+The kit is detailed (30 skills, routing logic, evidence format, memory contract). Larger models handle it better:
 
 | Model class | Experience |
 |-------------|-----------|
 | **7-8B** (Llama 3.1 8B, Mistral 7B, Qwen 2.5 7B) | Handles individual skills (readout, log, land). May struggle with complex routing or multi-skill sessions. Good for the CLI-heavy workflow where you invoke skills explicitly. |
-| **13-34B** (Llama 3.1 13B, Mixtral 8x7B, Qwen 2.5 32B, DeepSeek-R1 32B) | Good across all domains. Routes correctly, follows memory contract, writes structured artifacts. Recommended minimum for full methodology use. |
+| **13-34B** (Llama 3.1 13B, Mixtral 8x7B, Qwen 2.5 32B, DeepSeek-R1 32B) | Good across all domains. Routes correctly, follows memory contract, writes structured artifacts. Recommended minimum for full use. |
 | **70B+** (Llama 3.1 405B, DeepSeek V3, Qwen 2.5 72B) | Full capability. Handles regulated overlays, switch-clients, board-memo pyramid, runbook handoff. |
 
 ## The CLI works without ANY model
@@ -105,6 +105,6 @@ ollama run my-fde-model --system "$(cat skills/fde/SKILL.md)"
 ## Tips for local models
 
 - **Context window matters.** SKILL.md + references can be large. Use a model with at least 8K context; 32K+ is ideal for loading skill references on demand.
-- **Temperature 0.2-0.4 works best.** The methodology is structured - lower temperature keeps routing accurate and artifacts consistent.
+- **Temperature 0.2-0.4 works best.** The skills are structured - lower temperature keeps routing accurate and artifacts consistent.
 - **Use the CLI for mechanics.** Don't ask the model to do what the CLI already does deterministically. Use `fde scan` for repo recon, `fde log` for memory writes, `fde receipts` for searching. Let the model handle judgment, routing, and artifact drafting.
-- **Explicit skill invocation.** If a smaller model struggles with routing, you can invoke skills directly: "@fde run the discover phase" or "@fde use hold-scope." The model skips routing and goes straight to the method.
+- **Explicit skill invocation.** If a smaller model struggles with routing, you can invoke skills directly: "@fde run the discover phase" or "@fde use hold-scope." The model skips routing and goes straight to the skill.

package/adapters/README.md

@@ -2,7 +2,7 @@
 
 **One brain, thin adapters.** fdeops has a single source of truth - the `@fde` skill at `skills/fde/SKILL.md` and the `fde` CLI. Each AI coding tool discovers it through a small pointer file in the place that tool already looks. No forked logic, no five copies to maintain - every adapter says the same thing: *route via `@fde`, read/write `.fde/` memory, talk like a peer, never touch what isn't yours.*
 
-**Switching tools:** the fieldbook does not live in the agent. It lives at `~/fde-engagements/<client>/.fde/`. Point a new tool at a bound workspace, drop adapters (or install the skill/plugin for that tool), and the same client record opens. Auto session hooks are Claude Code-first; elsewhere load via `@fde` / `fde resume`. See [README § How it works](../README.md#how-it-works).
+**Switching tools:** the fieldbook does not live in the agent. It lives at `~/fde-engagements/<client>/.fde/`. Point a new tool at a bound workspace, drop adapters (or install the skill/plugin for that tool), and the same client record opens. Auto session hooks are Claude Code-first; elsewhere load via `@fde` / `fde resume`. See [README § How Skills Work](../README.md#how-skills-work).
 
 ## What goes where
 

package/adapters/copilot-instructions.md

@@ -6,7 +6,7 @@ You are the AI coding agent for a **Forward Deployed Engineer (FDE)** - the huma
 
 When the FDE types **`@fde`**, names a client, pastes meeting notes, asks what was agreed, or describes embed work (quiet sponsor, brief feels wrong, Friday update) - load the skill. If `fde resume` says NO ENGAGEMENT: ask the client name once, then **you** run `fde resume --init <slug>`. Never tell them to type it.
 
-Do **not** load `@fde` for a one-line typo in an unbound repo. On a bound client, stay on `@fde` for POC, small PRs, characterisation, proof on their staging, eval, and go-live.
+Do **not** load `@fde` for a one-line typo in an unbound repo. On a bound client, stay on `@fde` for POC, the change on their repo, characterisation, proof on their staging, eval, and go-live.
 
 - Skill (single source of truth): `~/.claude/skills/fde/SKILL.md`
 - **Never ask the FDE to pick a skill.** Read the situation, route silently, do the work.

package/adapters/cursor.fde.mdc

@@ -11,7 +11,7 @@ You are the AI coding agent for a **Forward Deployed Engineer (FDE)** - the huma
 
 When the FDE types **`@fde`**, names a client, pastes meeting notes, asks what was agreed, or describes embed work (quiet sponsor, brief feels wrong, Friday update) - load `@fde`. If `fde resume` says NO ENGAGEMENT: ask the client name once, then **you** run `fde resume --init <slug>`. Never tell them to type it.
 
-Do **not** load `@fde` for a one-line typo in an unbound repo. On a bound client, stay on `@fde` for POC, small PRs, characterisation, proof on their staging, eval, and go-live.
+Do **not** load `@fde` for a one-line typo in an unbound repo. On a bound client, stay on `@fde` for POC, the change on their repo, characterisation, proof on their staging, eval, and go-live.
 
 - Skill (single source of truth): `~/.claude/skills/fde/SKILL.md` (or the copy this install placed)
 - **Never ask the FDE to pick a skill.** Read the situation, route silently, do the work.

package/bin/check.js

@@ -57,7 +57,7 @@ for (const dir of fs.readdirSync(path.join(root, 'skills'))) {
 ok('skills structure')
 
 if (fs.existsSync(path.join(root, 'skills', 'fde', 'archive'))) {
-  fail('skills/fde/archive must not exist - unrouted methods are dead code')
+  fail('skills/fde/archive must not exist - unrouted skills are dead code')
 } else ok('no archived skill dump')
 
 // v3: one skill + phase references (progressive disclosure)
@@ -164,7 +164,7 @@ ok(`router dispatch (${mentioned.length} reference targets verified) + memory co
     documentedRows++
     documented.add(m[1])
     // A link nobody followed is the same unverifiable claim this gate exists for:
-    // the target must exist, and it must be the method the text names.
+    // the target must exist, and it must be the skill the text names.
     if (m[2] !== `${m[1]}.md`) {
       fail(`docs/skills-reference.md links [${m[1]}] at references/${m[2]}`)
     } else if (!fs.existsSync(path.join(root, 'skills', 'fde', 'references', m[2]))) {
@@ -172,13 +172,13 @@ ok(`router dispatch (${mentioned.length} reference targets verified) + memory co
     }
   }
   if (documented.size !== documentedRows) {
-    fail(`docs/skills-reference.md lists ${documentedRows} method rows for ${documented.size} methods - a duplicate row inflates the count`)
+    fail(`docs/skills-reference.md lists ${documentedRows} skill rows for ${documented.size} skills - a duplicate row inflates the count`)
   }
   const undocumented = [...routed].filter(name => !documented.has(name))
   if (undocumented.length) {
     fail(`SKILL.md routes skill(s) missing from docs/skills-reference.md: ${undocumented.join(', ')}`)
   }
-  // and the other direction: a documented method nothing routes to is a method
+  // and the other direction: a documented skill nothing routes to is a skill
   // the agent can never reach, advertised anyway.
   const unrouted = [...documented].filter(name => !routed.has(name))
   if (unrouted.length) {
@@ -187,7 +187,7 @@ ok(`router dispatch (${mentioned.length} reference targets verified) + memory co
   for (const rel of ['docs/skills.md', 'docs/skills-reference.md']) {
     const body = read(rel)
     // `-` is a word boundary, so \bscore\b matches inside `score-use-cases`:
-    // a method could disappear from the docs behind a hyphenated sibling.
+    // a skill could disappear from the docs behind a hyphenated sibling.
     const absent = [...documented].filter(name => !new RegExp(`(?<![\\w-])${name}(?![\\w-])`).test(body))
     if (absent.length) fail(`${rel} does not list skill(s): ${absent.join(', ')}`)
     const claims = [...body.matchAll(/(\d+)\s+skills/g)].map(m => Number(m[1]))
@@ -201,16 +201,23 @@ ok(`router dispatch (${mentioned.length} reference targets verified) + memory co
 
   const refDir = path.join(root, 'skills', 'fde', 'references')
   const extra = fs.readdirSync(refDir).filter(f => f.endsWith('.md') && !mentioned.includes(f))
-  if (extra.length) fail(`unrouted reference file(s) - dead method: ${extra.join(', ')}`)
+  if (extra.length) fail(`unrouted reference file(s) - dead skill: ${extra.join(', ')}`)
   else ok('no unrouted reference files')
 
-  // The on-site change loop lives in ship.md. A sibling method is a split.
+  // The on-site change loop lives in ship.md. A sibling skill is a split.
   for (const dead of ['small-prs.md', 'thin-slices.md', 'implement.md']) {
     if (fs.existsSync(path.join(refDir, dead))) {
       fail(`${dead} must not exist - that craft lives in ship.md`)
     }
   }
-  ok('ship is one method (no implement / small-prs / thin-slices sibling)')
+  ok('ship is one skill (no implement / small-prs / thin-slices sibling)')
+
+  if (/^### Prove\b/m.test(read('skills/fde/SKILL.md'))) {
+    fail('SKILL.md must not use Prove as a stage heading - the public stage is Outcome')
+  } else ok('SKILL.md stage heading is Outcome')
+  if (/\b31 names\b|\b31 skills\b/.test(read('README.md'))) {
+    fail('README must not advertise 31 skills')
+  } else ok('README skill count is 30')
 }
 
 const install = read('bin/install.js')
@@ -349,6 +356,18 @@ for (const rx of derivativeFraming) {
 if (/docs\/internal|PMF_360/i.test(readme)) {
   fail('README must not link docs/internal or PMF_360')
 }
+if (!/One command per stage/.test(readme) || !/Skills load automatically/.test(readme)) {
+  fail('README must formulate Commands as: one command per stage, skills load automatically')
+}
+if (!/Not prompts/.test(readme)) {
+  fail('README catalog must say skills are not prompts')
+}
+if (/\b(30|31|37)\s+methods\b|\broutes methods\b|\bphase methods\b|\bfield methods\b|\bengagement methods\b/.test(readme)) {
+  fail('README must call the catalog skills, not methods')
+}
+if (/\broutes methods\b|\bphase methods\b|\bengagement methods\b/.test(usage)) {
+  fail('docs/USAGE.md must call them skills, not methods')
+}
 ok('README tone')
 
 if (fs.existsSync(path.join(root, '.codex')) || fs.existsSync(path.join(root, '.opencode'))) {

package/bin/fde.js

@@ -740,11 +740,11 @@ function appendLogEntry(eng, type, entry, opts = {}) {
 // degrading to "nothing found" rather than guessing when the shape does not
 // match. Never fabricate a number, a name, or a signal that is not in the text.
 
-const PHASES = ['land', 'discover', 'plan', 'ship', 'prove', 'close']
-const PHASE_ALIASES = { build: 'ship' } // legacy SDLC name; public map is ship
+const PHASES = ['land', 'discover', 'plan', 'ship', 'outcome', 'close']
+const PHASE_ALIASES = { build: 'ship', prove: 'outcome' } // legacy names; public map is ship / outcome
 const PHASE_LABELS = {
   land: 'Land', discover: 'Discover', plan: 'Plan',
-  ship: 'Ship', prove: 'Prove', close: 'Close',
+  ship: 'Ship', outcome: 'Outcome', close: 'Close',
 }
 function canonicalPhase(phase) {
   const p = String(phase).toLowerCase()
@@ -1412,7 +1412,7 @@ function cmdLog(args) {
   const eng = resolveEngagement({ forWrite: true })
   if (!eng) { console.error('no engagement - run: fde resume --init <name>'); process.exit(2) }
 
-  // fde log phase <land|discover|plan|ship|prove|close> - advances portfolio phase
+  // fde log phase <land|discover|plan|ship|outcome|close> - advances portfolio phase (prove → outcome)
   if (type === 'phase') {
     const phase = canonicalPhase((text || '').toLowerCase().trim())
     if (!PHASES.includes(phase)) {
@@ -2237,7 +2237,7 @@ function collectDoctorIssues(eng) {
     }
   }
   const success = readClean(eng, 'success.md')
-  if (!firstLine(success, 80)) issues.push('success.md has no stated done-definition - fill before plan/build')
+  if (!firstLine(success, 80)) issues.push('success.md has no stated done-definition - fill before plan/ship')
   const ctxMd = readClean(eng, 'context.md')
   if (!sectionBody(ctxMd, 'Next action', { lastNonEmpty: true })) {
     issues.push('no ## Next action in context.md - Monday morning has nothing to drive')
@@ -2278,7 +2278,7 @@ function collectDoctorIssues(eng) {
   }
   // Failure-path (exception-led operating map): required once past discover.
   // Land seeds; discover fills; plan+ without a real break→owner row is wallpaper.
-  if (/^(plan|ship|prove|close)$/.test(s.phase) && !hasOperatingMapContent(eng)) {
+  if (/^(plan|ship|outcome|close)$/.test(s.phase) && !hasOperatingMapContent(eng)) {
     issues.push(
       `phase is ${s.phase} with empty operating map - fill terrain.md ## Operating map (exception-led): break → who notices → workaround → evidence`
     )
@@ -3324,7 +3324,7 @@ function printUsage() {
   fde triage               TRIAGE block only (hooks / Cursor session entry)
   fde log <type> <text>    append decision|risk|delivery|contact (contact takes --signal red|amber|green; delivery "a|b|c" writes the value ledger; --force to allow secret-like text)
   fde log risk --retire    move matching open-risk bullets to ## Retired
-  fde log phase <phase>    set engagement phase (land|discover|plan|ship|prove|close)
+  fde log phase <phase>    set engagement phase (land|discover|plan|ship|outcome|close)
   fde log --undo           remove the last CLI log/debrief entry from memory
   fde debrief [file]       meeting notes → memory (prefixed lines; --dry-run; --force)
   fde debrief --smart      heuristic propose (prints decision:/risk:/delivery:/contact:/next:); --apply after confirm

package/bin/lib/trust.js

@@ -98,9 +98,11 @@ function createTrustApi(deps) {
     if (!m) return '?'
     const raw = m[1].replace(/\*/g, '').trim()
     if (!raw || /\|/.test(raw) || /^unset$/i.test(raw) || /^[\[(]/.test(raw)) return '?'
-    const one = raw.toLowerCase().match(/^(land|discover|plan|build|ship|prove|close)\b/)
+    const one = raw.toLowerCase().match(/^(land|discover|plan|build|ship|prove|outcome|close)\b/)
     if (!one) return '?'
-    return one[1] === 'build' ? 'ship' : one[1]
+    if (one[1] === 'build') return 'ship'
+    if (one[1] === 'prove') return 'outcome'
+    return one[1]
   }
 
   function countOpenRisks(eng) {

package/mcp/fdeops-ingest/package.json

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

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "fdeops",
-  "version": "3.17.0",
+  "version": "3.20.0",
   "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.17.0",
+  "version": "3.20.0",
   "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

@@ -7,7 +7,7 @@ description: Keeps the engagement record for client work. Use when they name a c
 
 ## Purpose
 
-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.
+The **engagement record** for one client, from first meeting to signed outcome. One skill; six stages (land → close). Same map at any scale, on greenfield or brownfield, in any industry (overlays). You route; they never pick a skill. Confirm, then write `.fde/`. The workspace still compiles and commits. `@fde` does not leave.
 
 ## When to use
 
@@ -77,7 +77,7 @@ Writes need a bind (`FDEOPS_ENGAGEMENT` or registry). Never install fdeops on in
 
 ## The memory contract
 
-1. **On entry:** `fde resume` only. Pull other `.fde/` files when the method needs them.
+1. **On entry:** `fde resume` only. Pull other `.fde/` files when the skill needs them.
 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>`.
@@ -107,83 +107,83 @@ CLI is local (`git` + files, no network). You see their code only when they poin
 
 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.
+New embed: sprint / standard / programme changes depth, not which skills 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.
 
 ## Routing - 6 stages
 
-Read **one** reference and follow it. Do not improvise from memory.
+Work names (engage, diagnose, align, deliver, realize, transfer) are the same map. Read **one** reference and follow it. Do not improvise from memory.
 
 ### Land
 
 | You hear | Skill | Reference |
 |----------|-------|-----------|
-| Starting fresh, new customer, first meeting, just got the brief | land | `references/land.md` |
+| Engage, onboarding, starting fresh, new customer, first meeting, just got the brief, set product strategy, define success metrics, scope the brief | land | `references/land.md` |
 | Taking over, previous consultant left, joining mid-project | audit | `references/audit.md` |
-| Need to understand who matters, who decides, who blocks quietly | who-decides | `references/who-decides.md` |
+| Need to understand who matters, who decides, map decision rights, who blocks quietly | who-decides | `references/who-decides.md` |
 | Need to earn access, navigate AI policy, build credibility | earn-trust | `references/earn-trust.md` |
-| "Also can you…", scope expanding, timeline unchanged | hold-scope | `references/hold-scope.md` |
+| "Also can you…", scope expanding, timeline unchanged, hold scope, scope the brief after kickoff | hold-scope | `references/hold-scope.md` |
 
 ### Discover
 
 | You hear | Skill | Reference |
 |----------|-------|-----------|
-| 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…" | test-assumptions | `references/test-assumptions.md` |
-| Multiple use cases competing, "we want to do everything" | score-use-cases | `references/score-use-cases.md` |
-| Need to validate a direction, prototype, demo to de-risk, **POC**, spike, killer assumption | poc | `references/poc.md` |
+| Diagnose, don't know the real problem, brief feels wrong, shadow processes, frame discovery, understand the problem space, data not ready, data estate, catalog the data | discover | `references/discover.md` |
+| The brief feels too neat, assumptions untested, "we just need…", test assumptions | test-assumptions | `references/test-assumptions.md` |
+| Multiple use cases competing, "we want to do everything", score use cases | score-use-cases | `references/score-use-cases.md` |
+| Need to validate a direction, prototype, demo to de-risk, **POC**, spike, killer assumption, validate the solution, build prototype | poc | `references/poc.md` |
 
 ### Plan
 
 | You hear | Skill | Reference |
 |----------|-------|-----------|
-| Break this down, what order, sequence the build | plan | `references/plan.md` |
-| Sponsor needs justification, need to defend budget or timeline | business-case | `references/business-case.md` |
-| Significant decision, multiple approaches, "what should we do?" | three-options | `references/three-options.md` |
-| 20 things are "urgent," need to pick the 3 that matter | pick-three | `references/pick-three.md` |
+| Align, break this down, what order, sequence the build, plan the roadmap, create user stories, write the tasks | plan | `references/plan.md` |
+| Sponsor needs justification, need to defend budget or timeline, build the business case | business-case | `references/business-case.md` |
+| Significant decision, multiple approaches, "what should we do?", generate solutions, generate options | three-options | `references/three-options.md` |
+| 20 things are "urgent," need to pick the 3 that matter, prioritize three | pick-three | `references/pick-three.md` |
 
 ### Ship
 
 | You hear | Skill | Reference |
 |----------|-------|-----------|
-| What could go wrong, touching shared infrastructure, need to assess impact | what-breaks | `references/what-breaks.md` |
-| Production down, urgent - OR stakeholder gone quiet, trust slipping | rescue | `references/rescue.md` |
-| Start building, update their checkout, first module, visible progress, their tests, POC follow-through, ready to deploy, going live, pre-flight | ship | `references/ship.md` |
-| Review this change, is it safe, does it match what we agreed | review | `references/review.md` |
+| What could go wrong, touching shared infrastructure, need to assess impact, assess impact, provision, IaC, shared infra | what-breaks | `references/what-breaks.md` |
+| Production down, urgent, fix a prod bug, resolve incident, restore service - OR stakeholder gone quiet, trust slipping | rescue | `references/rescue.md` |
+| Deliver, start building, update their checkout, first module, visible progress, their tests, POC follow-through, ready to deploy, going live, pre-flight, deliver the increment, build the increment, create the launch plan, design their UI | ship | `references/ship.md` |
+| Review this change, review the pull request, 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 |
-| "We can always revert" - need to actually test the escape route | rollback | `references/rollback.md` |
+| "We can always revert" - need to actually test the escape route, rehearse rollback | rollback | `references/rollback.md` |
 
-### Prove
+### Outcome
 
 | You hear | Skill | Reference |
 |----------|-------|-----------|
-| Weekly update due, "need to send the sponsor something" | readout | `references/readout.md` |
-| Demo coming up, show-and-tell, exec walkthrough | demo-prep | `references/demo-prep.md` |
-| Just out of a meeting, raw notes, "they said…", "debrief" | debrief | the debrief verb (above) + `references/debrief.md` |
+| Realize, weekly update due, "need to send the sponsor something", report the outcome | readout | `references/readout.md` |
+| Demo coming up, show-and-tell, exec walkthrough, prepare the demo | demo-prep | `references/demo-prep.md` |
+| Just out of a meeting, raw notes, "they said…", "debrief", user interviews, workshop notes, capture the meeting | debrief | the debrief verb (above) + `references/debrief.md` |
 | Make sure we're up to date, pull what's relevant, fetch from Granola/Slack/Gmail/transcript | ingest | `references/ingest.md` (capability check → stage → propose → confirm → apply) |
 | Connect a new MCP / connect Granola Slack or Notion / what can you pull | connect | `references/connect.md` (+ `mcp/recipes/`) |
 | Prep me for a meeting / walk-in brief / "what should I know before I talk to…" | - | run `fde prep "<label>"`, present in plain language |
-| Sponsor's boss needs a summary, board update, justify continued investment | board-memo | `references/board-memo.md` |
-| Status across all my customers | dashboard | `references/dashboard.md` |
+| Sponsor's boss needs a summary, board update, brief the board, justify continued investment | board-memo | `references/board-memo.md` |
+| Status across all my customers, view the portfolio | dashboard | `references/dashboard.md` |
 
 ### Close
 
 | You hear | Skill | Reference |
 |----------|-------|-----------|
-| Juggling 2+ customers, losing track, context-switching | switch-clients | `references/switch-clients.md` |
-| Wrapping up, handoff, making yourself replaceable | close | `references/close.md` |
-| Engagement ending, team needs to operate without you | runbook | `references/runbook.md` |
-| Something worked well and will apply to future engagements | encode-pattern | `references/encode-pattern.md` |
-| "Red-team this," "stress-test my plan," poke holes, what am I missing | red-team | `references/red-team.md` |
+| Juggling 2+ customers, losing track, context-switching, switch engagements | switch-clients | `references/switch-clients.md` |
+| Transfer, wrapping up, handoff, making yourself replaceable, transfer operations | close | `references/close.md` |
+| Engagement ending, team needs to operate without you, write the runbook | runbook | `references/runbook.md` |
+| Something worked well and will apply to future engagements, encode the pattern | encode-pattern | `references/encode-pattern.md` |
+| "Red-team this," "stress-test my plan," poke holes, challenge the plan, what am I missing | red-team | `references/red-team.md` |
 | "What did we agree about X?", scope dispute, receipts | - | run `fde receipts <term>`, answer with dates |
 
 **Overlays - activate alongside any skill on signal, don't wait to be told:**
 
 | Signal | Overlay |
 |--------|---------|
-| AI, ML, LLM, model, embeddings, RAG, agents, fine-tuning, inference, drift | `references/ai.md` |
+| AI, ML, LLM, model, embeddings, RAG, agents, fine-tuning, inference, drift, train the model | `references/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` |
@@ -195,7 +195,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.
+- Same six stages at any scale. Overlays carry the industry. Greenfield and brownfield change the first move inside ship, not the map.
 - Ground loop on a bound client: name → characterise → prove on their staging → go live → log. Do not hand their repo to a generic coding pack.
+- Do not call a change done until the signer in `success.md` can reject it on staging they operate.
 - 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."

package/skills/fde/references/ai.md

@@ -38,7 +38,7 @@ 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 skill: `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.
@@ -47,7 +47,7 @@ When any slice touches a model, embeddings, RAG, or an agent: create or update `
 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; poc/build grows goldens; ship requires Verdict SHIP and a receipt in `delivery.md` → `## Ship receipts`. Non-AI work skips this file entirely.
+**When to write:** plan seeds the pack; poc/ship grows goldens; ship requires Verdict SHIP and a receipt in `delivery.md` → `## Ship receipts`. Non-AI work skips this file entirely.
 
 ## RAG architecture (retrieval-augmented generation)
 

package/skills/fde/references/audit.md

@@ -1,4 +1,4 @@
-# audit - taking over mid-engagement
+# audit - Verify inherited claims
 
 **Enter when:** picking up someone else's work - previous consultant left, joining mid-project, half-done system.
 
@@ -9,7 +9,7 @@
 Before forming any opinion:
 
 1. **Inherit the paper.** Any previous `.fde/`, docs, README claims, ADRs, ticket history the FDE can export. Read it all - the previous FDE's decisions are evidence, not verdicts.
-2. **Run the discover scans** (see `discover.md` method part 1: churn, test gaps, "temporary" grep, AI components). On a takeover, add:
+2. **Run the discover scans** (see `discover.md` part 1: churn, test gaps, "temporary" grep, AI components). On a takeover, add:
 ```bash
 git log --format="%an" | sort | uniq -c | sort -rn | head   # who actually built this
 git log --since="60 days ago" --format="%ad %s" --date=short | head -20  # what was happening when they left

package/skills/fde/references/board-memo.md

@@ -1,4 +1,4 @@
-# board-memo - the story that gets the next phase funded
+# board-memo - Brief the board
 
 **Enter when:** the sponsor's boss needs a summary, a board update mentions the engagement, the FDE needs to justify continued investment, or a quarterly review is approaching.
 

package/skills/fde/references/business-case.md

@@ -1,4 +1,4 @@
-# business-case - the economics that get the sponsor to say yes
+# business-case - Build the business case
 
 **Enter when:** the sponsor needs justification for the next phase, the FDE needs to defend budget or timeline, a feature decision needs cost/benefit evidence, or poc produced a direction that needs funding.
 

package/skills/fde/references/close.md

@@ -1,4 +1,4 @@
-# close - handoff and pattern extraction
+# close - Transfer operations
 
 **Enter when:** the engagement is ending - the customer team must run this without the FDE.
 

package/skills/fde/references/connect.md

@@ -1,4 +1,4 @@
-# connect - wire a source MCP in plain language
+# connect - Connect a source
 
 **Enter when:** the FDE says "I want to connect a new MCP", "connect Granola / Slack / Notion", "how do I pull from …", or a pull request fails because no source tools exist.
 

package/skills/fde/references/dashboard.md

@@ -1,4 +1,4 @@
-# dashboard - the portfolio view
+# dashboard - View the portfolio
 
 **Enter when:** the FDE runs several customers and asks "where am I across everything?"
 
@@ -8,7 +8,7 @@ The visual artifact is rendered by code, not by you. `fde dashboard` reads every
 
 ## Method (you do this work)
 
-0. **First move: `fde status`** - instant heuristic triage (trust-first ordering) across every engagement. Use it as the index; then deep-read only the folders that are red/amber or that the FDE asks about, and apply the full card method below.
+0. **First move: `fde status`** - instant heuristic triage (trust-first ordering) across every engagement. Use it as the index; then deep-read only the folders that are red/amber or that the FDE asks about, and apply the full card below.
 1. **Find the engagements:** `~/fde-engagements/*/.fde/` (primary) · workspace `./.fde/` if present · paths the FDE names. Read each folder **separately** - never merge two customers.
 2. **Per engagement, read the card the way a human would:**
    - Name, phase, week

package/skills/fde/references/debrief.md

@@ -1,4 +1,4 @@
-# debrief - capture the meeting before it evaporates
+# debrief - Capture the meeting
 
 **Enter when:** the FDE just left a meeting/call and dumps raw notes, a transcript, or "they said…". Highest-frequency moment in FDE life. Capture within the hour.
 

package/skills/fde/references/demo-prep.md

@@ -1,4 +1,4 @@
-# demo-prep - the demo is the heartbeat of the engagement
+# demo-prep - Prepare the demo
 
 **Enter when:** a demo, show-and-tell, or exec walkthrough is coming. FDE engagements live demo-to-demo; a flat demo costs more than a slipped task.
 

package/skills/fde/references/discover.md

@@ -1,4 +1,4 @@
-# discover - find the real problem, map the terrain
+# discover - Frame the problem
 
 **Enter when:** the brief feels wrong, the real problem is unclear, shadow processes are suspected, or any phase found that the map is missing.
 
@@ -105,7 +105,7 @@ The real spec is what people **do** when the system fails - not what the slide d
 - **The hesitation.** When someone says "well, there's also this other thing we do…" - stop them, ask them to finish. The main story is what they're comfortable explaining; the hesitation is the real problem.
 - **"Which part of the codebase do you least want to touch?"** The answer is unanimous and it's the load-bearing wall. Check it against your churn scan - when the human answer and the churn data agree, that's your first map landmark.
 - **Shadow AI.** Someone pasting data into ChatGPT to cope = a real unmet need + an uncontrolled data risk. Note both.
-- **Exception-led operating map.** For each real break (not the slide-deck process): what fails, who notices first, what they do today, and which artifact is trusted in that moment. Prefer exceptions over happy-path swimlanes - the workaround is the operating system. Write rows under `terrain.md` → `## Operating map (exception-led)`. If the section is missing on an older engagement, add it; never regenerate the rest of terrain. When AI is in play, also fill `## Intelligence placement` (deterministic vs LLM judgement vs human approve). **`fde doctor` requires at least one filled exception row before plan/build/ship/close** - empty map after discover is a hygiene fail, not optional polish.
+- **Exception-led operating map.** For each real break (not the slide-deck process): what fails, who notices first, what they do today, and which artifact is trusted in that moment. Prefer exceptions over happy-path swimlanes - the workaround is the operating system. Write rows under `terrain.md` → `## Operating map (exception-led)`. If the section is missing on an older engagement, add it; never regenerate the rest of terrain. When AI is in play, also fill `## Intelligence placement` (deterministic vs LLM judgement vs human approve). **`fde doctor` requires at least one filled exception row before plan/ship/outcome/close** - empty map after discover is a hygiene fail, not optional polish.
 
 ## Method - part 3: workshop facilitation
 
@@ -171,7 +171,7 @@ Score every candidate use case before anything gets prototyped:
 **Complication:** <what forces a decision now>
 **Question:** <one decision-shaped sentence>
 **Answer-space:** confirm brief / descope / rescope / pause - and what a yes looks like
-**Implication for build:** <first small PR>
+**Implication for build:** <first change they can see>
 **Validated with:** <who, when>
 ```
 

package/skills/fde/references/earn-trust.md

@@ -1,4 +1,4 @@
-# earn-trust - earning commit access one move at a time
+# earn-trust - Earn access
 
 **Enter when:** new engagement where you don't have full access yet, trust is thin, the customer said "let's start small," or you need to navigate "we don't trust AI-generated code."
 

package/skills/fde/references/encode-pattern.md

@@ -1,4 +1,4 @@
-# encode-pattern - if you did it twice, encode it
+# encode-pattern - Encode the pattern
 
 **Enter when:** the engagement is closing and reusable patterns exist, a technique worked well and will apply to future clients, the FDE notices themselves doing the same thing on a second engagement, or close identified a pattern worth preserving.
 
@@ -48,7 +48,7 @@ The difference between a 5-year FDE and a 15-year FDE is not talent - it's encod
 | **Repeatable?** | Applies to a class of situations, not just this one | Only worked because of a unique circumstance |
 | **Falsifiable?** | You can tell when the pattern is working or not | No way to measure whether applying it helped |
 
-**4. Classify by stage.** Patterns sort into the same stages as the methods:
+**4. Classify by stage.** Patterns sort into the same stages as the skills:
 
 | Stage | Pattern type | Example |
 |--------|-------------|---------|
@@ -56,7 +56,7 @@ The difference between a 5-year FDE and a 15-year FDE is not talent - it's encod
 | **Discover** | Investigative / analytical | "The cron-job discovery checklist for legacy systems" |
 | **Plan** | Structural / strategic | "The three-option presentation for nervous sponsors" |
 | **Ship** | Technical / safety | "The Strangler Fig on financial transaction code" |
-| **Prove** | Operational / process | "The regulated-environment change-approval timeline buffer" |
+| **Outcome** | Operational / process | "The regulated-environment change-approval timeline buffer" |
 | **Close** | Knowledge / handoff | "The 2am document format that actually gets used" |
 
 **5. Version and evolve.** Patterns are living documents:

package/skills/fde/references/eval-pack.md

@@ -1,4 +1,4 @@
-# eval-pack - prove the system before it acts
+# eval-pack - Gate the model before it acts
 
 **Enter when:** the work touches AI/LLM/agents/RAG, or they need to POC a model, or ship/close is blocked because there is no evidence the non-deterministic path is safe. Activate alongside `ai.md`, `poc`, or `ship` - not instead of them.
 

package/skills/fde/references/hold-scope.md

@@ -1,4 +1,4 @@
-# hold-scope - holding the line without losing the relationship
+# hold-scope - Hold scope
 
 **Enter when:** "also can you…" mid-build, a stakeholder adds requirements without adjusting timeline, the FDE feels scope creeping but can't name it, or `success.md` no longer matches what's being asked.
 

package/skills/fde/references/ingest.md

@@ -1,4 +1,4 @@
-# ingest - pull large artifacts into the fieldbook loop
+# ingest - Ingest sources
 
 **Enter when:** the FDE wants to catch the engagement up from external sources - "make sure Acme is up to date," "pull what's relevant," "grab today's Granola and Denise's last email." Raw transcripts and long emails that are too big to paste usefully.
 

package/skills/fde/references/land.md

@@ -1,4 +1,4 @@
-# land - first 48 hours
+# land - Interrogate the brief
 
 **Enter when:** new customer, first meeting, just got the brief, nothing started yet.
 

package/skills/fde/references/pick-three.md

@@ -1,4 +1,4 @@
-# pick-three - when 20 things are "urgent," pick the 3 that matter
+# pick-three - Prioritize three
 
 **Enter when:** a transformation engagement with a long list of initiatives, the customer's roadmap has more items than weeks, competing teams want different things, or the FDE needs to recommend what to do *first* across a complex programme.
 

package/skills/fde/references/plan.md

@@ -1,4 +1,4 @@
-# plan - sequence the work
+# plan - Sequence the work
 
 **Enter when:** scope is understood and the work needs breaking down - a slice, a phase, or the whole delivery.
 

package/skills/fde/references/poc.md

@@ -1,8 +1,10 @@
-# poc - kill or confirm a direction in a day
+# poc - Validate the solution
 
 **Enter when:** a direction needs validating before committing real build time - POC, spike, show something, de-risk, pick between use cases. The output is something a sponsor can reject in a room this week, not a polished product.
 
-**Read first:** `context.md`, `reality.md`. Load `terrain.md` only if the prototype touches the existing codebase.
+**Read first:** `context.md`, `reality.md`. Load `terrain.md` only if the prototype touches the existing codebase. If `terrain.md` **Data estate** has a Blocker source this prototype needs, stop - that is discover, not a day's demo.
+
+A green check on synthetic data is not a validated solution. The person who can say no has to see it on evidence they already believe.
 
 ## Method (you do this work)
 

package/skills/fde/references/readout.md

@@ -1,4 +1,4 @@
-# readout - the sponsor update that keeps the engagement alive
+# readout - Report the outcome
 
 **Enter when:** the weekly update is due, an exec asks "where are we," or the FDE says "I need to send Dana something." This artifact decides renewals; engineers underinvest in it.
 

package/skills/fde/references/red-team.md

@@ -1,4 +1,4 @@
-# red-team - adversarial stress-test of your plan, position, or deliverable
+# red-team - Challenge the plan
 
 **Enter when:** the FDE says "red-team this," "stress-test my thinking," "poke holes in this," "what am I missing," "challenge my plan" - or anytime they are about to walk into a high-stakes conversation (sponsor meeting, accumulation conversation, handoff, go-live) and want their blind spots exposed first.
 

package/skills/fde/references/rescue.md

@@ -1,4 +1,4 @@
-# rescue - production fire, trust fire, or wrong-brief mid-build
+# rescue - Resolve the incident
 
 **Enter when:** production is down, something's bleeding - OR a stakeholder went quiet, confidence is slipping, or three weeks into the build the brief turned out to be wrong. Trust fires get the same urgency as outages.
 
@@ -13,7 +13,8 @@ Open by narrowing time, like a human: "Walk me through the last couple hours - d
 git log --since="6 hours ago" --format="%ad %an %s" --date=relative
 ```
 
-**The sequence:**
+**The sequence:** no fix until the cause is named. A symptom patch is the second incident.
+
 1. **Stabilise first.** Roll back? Disable the broken path? Route around it? Buy time before diagnosing. The instinct to fix fast causes the second incident.
 2. **Name the unknowns.** "We don't know if the queue is corrupted / if this hits all users / if the cache is stale." Written down. Named unknowns are safer than assumed knowns.
 3. **Assume maximum blast radius.** The unrecognised integration in the stack trace is load-bearing until proven otherwise.

package/skills/fde/references/review.md

@@ -1,4 +1,4 @@
-# review - two stages, always in order
+# review - Review the change
 
 **Enter when:** a change needs review before merge - "is this safe," "does it match what we agreed."
 

package/skills/fde/references/rollback.md

@@ -1,4 +1,4 @@
-# rollback - test the escape route before you need it
+# rollback - Rehearse rollback
 
 **Enter when:** a deploy is planned for the next 48 hours, the FDE says "we can always revert," a previous rollback failed or took too long, or the engagement involves regulated/critical systems.
 

package/skills/fde/references/runbook.md

@@ -1,4 +1,4 @@
-# runbook - making yourself replaceable is the goal
+# runbook - Write the runbook
 
 **Enter when:** the engagement is entering its final phase, the customer team needs to operate without the FDE, a new FDE is taking over, or the sponsor asks "what happens when you leave?"
 

package/skills/fde/references/score-use-cases.md

@@ -1,4 +1,4 @@
-# score-use-cases - pick the right battle, not the interesting one
+# score-use-cases - Score use cases
 
 **Enter when:** multiple potential use cases compete for attention, the customer says "we want to do everything," a transformation engagement needs a starting point, or the FDE needs to recommend which problem to solve first.
 

package/skills/fde/references/ship.md

@@ -1,4 +1,4 @@
-# ship - on their site, then live
+# ship - Deliver the increment
 
 **Enter when:** you are writing or updating on their codebase, they need to see something real, or you are going live.
 
@@ -12,7 +12,7 @@ Do not ask them to pick a mode. Name where you are, then start at the matching s
 
 If going live, opening question: **has anyone actually *run* the rollback, or is it still a slide?** If only planned, that's today's work - say so plainly.
 
-A same-day throwaway that kills an assumption is `poc`. This method is the real change on a repo they will own, then production.
+A same-day throwaway that kills an assumption is `poc`. This skill is the real change on a repo they will own, then production.
 
 ## Field (name it once, then the same loop)
 
@@ -25,6 +25,10 @@ A same-day throwaway that kills an assumption is `poc`. This method is the real
 
 Skip POC only when the killer assumption already lives in the repo (typical brownfield). If the bet is unproven, `poc` first.
 
+**Done means:** the signer in `success.md` can reject this on staging they operate. A green check on your laptop is not delivery. Do not start the next change until this one is rejectable.
+
+If `terrain.md` **Data estate** lists a **Blocker** this change depends on: stop. That is discover, not ship. Do not build a path they cannot feed.
+
 ## Method - one change they can see
 
 One change = one thing a user can do, with a test, that you can revert on its own. Not "all the APIs, then all the UI." Not a 2,000-line dump. A PR is how this often lands. It is not the job. The job is the change they can see.

package/skills/fde/references/switch-clients.md

@@ -1,4 +1,4 @@
-# switch-clients - juggling engagements without dropping any
+# switch-clients - Switch engagements
 
 **Enter when:** the FDE is running 2+ engagements simultaneously, context-switching is causing mistakes or delays, a new customer is being onboarded while existing engagements are active, or the FDE says "I'm losing track."
 

package/skills/fde/references/test-assumptions.md

@@ -1,4 +1,4 @@
-# test-assumptions - pressure-test the brief before building on it
+# test-assumptions - Test assumptions
 
 **Enter when:** the brief feels too neat, the customer is very confident about the solution (not the problem), someone says "we just need…" about a complex system, or discover surfaced contradictions between what was said and what the codebase shows.
 

package/skills/fde/references/three-options.md

@@ -1,4 +1,4 @@
-# three-options - three paths, not one recommendation
+# three-options - Generate options
 
 **Enter when:** a significant technical or strategic decision needs to be made, the FDE is asked "what should we do?", the team is stuck between approaches, or a fork in the engagement requires the sponsor's input.
 

package/skills/fde/references/what-breaks.md

@@ -1,4 +1,4 @@
-# what-breaks - know what breaks before you touch it
+# what-breaks - Assess impact
 
 **Enter when:** about to make a change on a system you don't fully understand, touching a high-churn module from `terrain.md`, modifying shared infrastructure (auth, database, messaging), or the FDE asks "what could go wrong?"
 

package/skills/fde/references/who-decides.md

@@ -1,4 +1,4 @@
-# who-decides - reading the room before it reads you
+# who-decides - Map decision rights
 
 **Enter when:** new stakeholders appear, signals shift mid-engagement, a meeting felt off but you can't say why, or it's been two weeks and the map hasn't been updated.
 

package/templates/.fde/terrain.md

@@ -9,7 +9,7 @@
 ## Operating map (exception-led)
 
 <!-- How work actually runs when the happy path fails. Fill in discover; leave blank until heard/seen.
-     fde doctor requires ≥1 real exception row before plan/build/ship/close. -->
+     fde doctor requires ≥1 real exception row before plan/ship/outcome/close. -->
 
 | Exception / break | Who notices first | What they do today (workaround) | System of record then | Blast if wrong | Evidence |
 |-------------------|-------------------|---------------------------------|-----------------------|----------------|----------|