fdeops 3.15.0 → 3.15.2

package/AGENTS.md

@@ -1,6 +1,6 @@
 # AGENTS.md - working in the fdeops repository
 
-This repository **is** fdeops — the engagement record for Forward Deployed Engineers. One `@fde` skill, the `fde` CLI for deterministic work, and per-customer memory in `.fde/` as a side effect of the work (you still confirm judgment).
+This repository **is** fdeops - the engagement record for Forward Deployed Engineers. One `@fde` skill, the `fde` CLI for deterministic work, and per-customer memory in `.fde/` as a side effect of the work (you still confirm judgment).
 
 ## If you are helping use fdeops in an engagement
 

package/README.md

@@ -2,7 +2,7 @@
 
 **Forward deployed engineering skills for AI coding agents.**
 
-Skills encode the workflows, quality gates, and judgment Forward Deployed Engineers use on someone else's site. Packaged so an AI coding agent follows them consistently — and writes a dated record you can defend. The host agent still writes the TypeScript.
+Skills encode the workflows, quality gates, and judgment Forward Deployed Engineers use on someone else's site. Packaged so an AI coding agent can run the embed end-to-end: discovery, POC, slice, on-site proof, eval, signed outcome. The workspace still compiles and commits. `@fde` does not leave.
 
 ```text
   LAND              DISCOVER           PLAN              SHIP               PROVE              CLOSE
@@ -10,27 +10,34 @@ Skills encode the workflows, quality gates, and judgment Forward Deployed Engine
  │  Brief │ ───▶ │ Reality│ ───▶ │ Sequence│───▶ │  Live  │ ───▶ │ Signed │ ───▶ │  They  │
  │  Trust │      │ Terrain│      │  Align │      │  slice │      │   off  │      │   run  │
  └────────┘      └────────┘      └────────┘      └────────┘      └────────┘      └────────┘
-  /brief           /discover          /plan             /ship              /got              /close
+  /brief           /discover          /plan             /ship            /outcome           /close
 ```
 
 ---
 
 ## Commands
 
-6 slash commands that map to the engagement. Each one loads `@fde`. You never pick a method.
+Each command loads the same `@fde` skill. You never pick from 31 names.
 
-| What you're doing | Command | Principle |
+| What you're doing | Command | Key principle |
 |-------------------|---------|-----------|
-| Land the embed | `/brief` | Brief and trust before code |
+| Land the embed | `/brief` | Who signs done |
 | Find the real problem | `/discover` | Brief is a hypothesis |
 | Plan the sequence | `/plan` | Backwards from done |
-| Ship a slice | `/ship` | Pre-flight, then live |
-| Prove what they got | `/got` | Promised → measured → accepted |
-| Close the embed | `/close` | They can run it without you |
+| Ship a slice | `/ship` | Live with a rollback |
+| Prove the outcome | `/outcome` | Promised, measured, accepted |
+| Close the embed | `/close` | They run it without you |
 
-Also: `/debrief` (after a meeting) · `/prep` (walk-in) · `/quiet` (sponsor silent) · `/agreed` (scope dispute) · `/status` (Friday readout).
+Four tells the map does not cover:
 
-`@fde` plus English activates the same skill automatically. Ordinary TypeScript, unit tests, and git commits stay in the host agent.
+| What you're doing | Command | Key principle |
+|-------------------|---------|-----------|
+| Sponsor went silent | `/quiet` | Process or trust |
+| Scope dispute | `/agreed` | Dated receipts, or a gap |
+| After a meeting | `/debrief` | Notes into the record |
+| Walk-in / Friday | `/prep` `/status` | One page, then the ledger |
+
+Skills also activate on English: naming a client, running a POC, slicing a feature, asking what was agreed. A throwaway one-liner in an unbound repo can skip `@fde`. A client slice cannot.
 
 ---
 
@@ -67,7 +74,7 @@ Hooks load where you left off. Slash commands match the map above.
 npx skills add suboss87/fdeops --skill fde
 ```
 
-Or `npx fdeops adapters .` — [adapters/](adapters/README.md).
+Or `npx fdeops adapters .`. See [adapters/](adapters/README.md).
 
 </details>
 
@@ -86,19 +93,19 @@ Fallback if the agent cannot bind:
 npx fdeops resume --init acme   # ~/fde-engagements/acme + bind this checkout
 ```
 
-Requires Node.js >= 18. Override: `FDEOPS_ENGAGEMENT` — [docs/install.md](docs/install.md). Try the loop: `npx fdeops demo`.
+Requires Node.js >= 18. Override: `FDEOPS_ENGAGEMENT`. See [docs/install.md](docs/install.md). Try the loop: `npx fdeops demo`.
 
 </details>
 
 ---
 
-## All 31 Methods
+## All 31 Skills
 
-The commands above are the entry points. One `@fde` skill routes to these 31 methods — each a structured workflow with an artifact and a checkpoint. You never pick a method by name. Full detail: [docs/skills-reference.md](docs/skills-reference.md).
+The commands above are the entry points. Under the hood, `@fde` activates these 31 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).
 
-### Land
+### Land - Brief and trust
 
-| Method | 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 |
@@ -106,38 +113,38 @@ The commands above are the entry points. One `@fde` skill routes to these 31 met
 | [trust-engineering](skills/fde/references/trust-engineering.md) | Observer → trusted; navigate AI policy | Need access or credibility |
 | [scope-defense](skills/fde/references/scope-defense.md) | Scope receipts; the accumulation conversation | "Also can you…", timeline unchanged |
 
-### Discover
+### Discover - Find the real problem
 
-| Method | What it does | Use when |
+| Skill | What It Does | Use When |
 |--------|--------------|----------|
 | [discover](skills/fde/references/discover.md) | Repo + workaround + the real problem | Brief feels wrong, shadow processes |
 | [assumption-audit](skills/fde/references/assumption-audit.md) | Untested assumptions by blast radius | Brief feels too neat |
 | [use-case-scoring](skills/fde/references/use-case-scoring.md) | Value × urgency × alignment / complexity | Everything is P0 |
-| [sketch](skills/fde/references/sketch.md) | Kill the killer assumption in a day | Need to de-risk a direction |
+| [sketch](skills/fde/references/sketch.md) | Kill the killer assumption in a day | POC, spike, need to de-risk |
 
-### Plan
+### Plan - Sequence the work
 
-| Method | What it does | Use when |
+| Skill | What It Does | Use When |
 |--------|--------------|----------|
 | [plan](skills/fde/references/plan.md) | Backwards from done, PR-sized | What order, what is done |
 | [business-case](skills/fde/references/business-case.md) | Cost of nothing → investment → return | Defend budget or timeline |
 | [options-analysis](skills/fde/references/options-analysis.md) | Three genuine options | "What should we do?" |
 | [initiative-triage](skills/fde/references/initiative-triage.md) | Pick three from twenty urgents | Everything is urgent |
 
-### Ship
+### Ship - Go live
 
-| Method | What it does | Use when |
+| Skill | What It Does | Use When |
 |--------|--------------|----------|
-| [incremental-build](skills/fde/references/incremental-build.md) | Vertical slices, visible every 2–3 days | Large feature on their codebase |
+| [incremental-build](skills/fde/references/incremental-build.md) | Vertical slices, on-site proof | Building on their codebase |
 | [blast-radius](skills/fde/references/blast-radius.md) | Impact from contained → irreversible | Touching shared infrastructure |
 | [rescue](skills/fde/references/rescue.md) | Production fire or trust fire | Down, or they went quiet |
 | [ship](skills/fde/references/ship.md) | Intent vs diff, pre-flight, rollback | Going live |
 | [review](skills/fde/references/review.md) | Did we only build what we agreed | Before merge, scope creep |
 | [rollback-drill](skills/fde/references/rollback-drill.md) | Test the escape route before 2am | "We can always revert" |
 
-### Prove
+### Prove - Outcome
 
-| Method | What it does | Use when |
+| Skill | What It Does | Use When |
 |--------|--------------|----------|
 | [status](skills/fde/references/status.md) | Promised → measured → accepted | Friday, sponsor update |
 | [demo-prep](skills/fde/references/demo-prep.md) | One number, five hard questions | Demo or exec walkthrough |
@@ -147,9 +154,9 @@ The commands above are the entry points. One `@fde` skill routes to these 31 met
 | [ingest](skills/fde/references/ingest.md) | Pull text you confirm | Transcript, Notion, Slack |
 | [ingest-connect](skills/fde/references/ingest-connect.md) | Wire a source MCP | Connect Granola |
 
-### Close
+### Close - They run it
 
-| Method | What it does | Use when |
+| Skill | What It Does | Use When |
 |--------|--------------|----------|
 | [close](skills/fde/references/close.md) | Handoff that survives you | Wrapping up |
 | [handoff-engineering](skills/fde/references/handoff-engineering.md) | Runbook, confidence scoring | They must operate without you |
@@ -163,36 +170,33 @@ Optional pull: you add the source MCP; we **pull** on request. [mcp/recipes/](mc
 
 ---
 
-## How it works
+## How Skills Work
 
-Every method follows the same anatomy:
+One skill. One reference file per situation. One folder per client.
 
 ```
-┌─────────────────────────────────────────────┐
-│  @fde  (one skill)                          │
-│                                             │
-│  ┌─ Frontmatter ─────────────────────────┐  │
-│  │ name: fde                             │  │
-│  │ description: Use when [client work]   │  │
-│  └───────────────────────────────────────┘  │
-│                                             │
-│  Commands load it. English loads it.        │
-│  You confirm. Then .fde/ is written.        │
-└─────────────────────────────────────────────┘
-         │
-         ▼
-  references/<method>.md     fde CLI (local)
-  one file, then stop        dating, gates, redaction
+  /brief   or   "@fde this is Acme"
+           │
+           ▼
+  skills/fde/SKILL.md          hosts load this one file
+           │  routes. you never pick a skill by name
+           ▼
+  references/land.md           one workflow, then stop
+           │
+           ▼
+  fde CLI (local)              dates, gates, redacts. no network
+           │  after you confirm
+           ▼
+  ~/fde-engagements/<client>/.fde/
 ```
 
-- **Process, not prose.** Methods are workflows with an artifact and a checkpoint.
+- **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 → 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, receipts, status. Zero model tokens. The AI coding agent runs it.
-
-The record lives at `~/fde-engagements/<client>/.fde/` — not inside any vendor. Change hosts, install `@fde` on the new one, bind if needed, keep talking.
+- **Local CLI.** Writes and status cost zero model tokens. The AI coding agent runs it.
 
-**Words used here, once:** *engagement* - one client's body of work, one folder. *Fieldbook* - that folder (`.fde/`), the record itself. *Brief vs reality* - what they said the problem was, and what it turned out to be. *Terrain* - their systems and org as you actually found them. *Trust signal* - green / amber / red on one relationship. *Receipts* - the dated line proving something was agreed. *Vault* - the Obsidian copy `fde vault` generates to read it all in one window.
+Change hosts, install `@fde` on the new one, bind if needed, keep talking. The record is not inside any vendor.
 
 ---
 
@@ -200,36 +204,76 @@ The record lives at `~/fde-engagements/<client>/.fde/` — not inside any vendor
 
 ```
 fdeops/
-├── skills/fde/                 # the one skill
-│   ├── SKILL.md                #   router
-│   └── references/             #   31 methods + overlays
-├── .claude/commands/           # slash commands (each loads @fde)
-├── bin/fde.js                  # local CLI — git + files, no network
-├── hooks/                      # session-start / session-stop / pre-compact
-├── adapters/                   # Cursor, Gemini, Copilot, Codex pointers
-├── templates/.fde/             # memory files created on bind
-└── docs/                       # usage, schema, install
+├── skills/fde/                            # the one skill hosts load
+│   ├── SKILL.md                           #   router
+│   └── references/                        #   31 skills + overlays (you never pick)
+│       ├── land.md                        #   Land
+│       ├── audit.md
+│       ├── stakeholder-radar.md
+│       ├── trust-engineering.md
+│       ├── scope-defense.md
+│       ├── discover.md                    #   Discover
+│       ├── assumption-audit.md
+│       ├── use-case-scoring.md
+│       ├── sketch.md
+│       ├── plan.md                        #   Plan
+│       ├── business-case.md
+│       ├── options-analysis.md
+│       ├── initiative-triage.md
+│       ├── incremental-build.md           #   Ship
+│       ├── blast-radius.md
+│       ├── rescue.md
+│       ├── ship.md
+│       ├── review.md
+│       ├── rollback-drill.md
+│       ├── status.md                      #   Prove
+│       ├── demo-prep.md
+│       ├── debrief.md
+│       ├── exec-narrative.md
+│       ├── dashboard.md
+│       ├── ingest.md
+│       ├── ingest-connect.md
+│       ├── close.md                       #   Close
+│       ├── handoff-engineering.md
+│       ├── multi-customer-ops.md
+│       ├── pattern-extract.md
+│       ├── red-team.md
+│       ├── ai.md                          #   overlays (on signal)
+│       ├── artifacts.md
+│       ├── eval-pack.md
+│       ├── fintech.md
+│       ├── healthcare.md
+│       └── gov.md
+├── .claude/commands/                      # slash commands (each loads @fde)
+│   ├── brief.md
+│   ├── discover.md
+│   ├── plan.md
+│   ├── ship.md
+│   ├── outcome.md
+│   ├── close.md
+│   ├── quiet.md
+│   ├── agreed.md
+│   ├── debrief.md
+│   ├── prep.md
+│   └── status.md
+├── .claude-plugin/                        # Claude Code marketplace
+├── bin/                                   # local CLI: git + files, no network
+├── hooks/                                 # session-start / session-stop / pre-compact
+├── adapters/                              # Cursor, Gemini, Copilot, Codex pointers
+├── templates/.fde/                        # memory files created on bind
+├── examples/                              # fictional walkthroughs
+├── mcp/                                   # optional ingest + source recipes
+├── evals/                                 # routing checks
+└── docs/                                  # usage, schema, install
 ```
 
 ---
 
-## Why this exists
-
-### 1. The brief is wrong
-
-The most common failure on an embed is building the portal they asked for. Ops has been running a spreadsheet for two years. `/brief` then `/discover` — who in their company would have to agree it worked?
+## Why FDEOps?
 
-### 2. They went quiet
+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.
 
-A sponsor who stops answering is not a Jira gap. It is a trust color. `/quiet` — process vs trust, then a dated signal in the record.
-
-### 3. When did we agree?
-
-Arguments from memory lose. `/agreed` searches dated receipts. No hit is a gap, not proof.
-
-### 4. What did they get?
-
-A number only you agree with is claimed, not delivered. `/got` reads promised → measured → accepted out loud.
+FDEOps is what you take on site. One `@fde` skill runs the embed from discovery to signed outcome: POC, slice, on-site proof, 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.
 
 ---
 
@@ -252,19 +296,15 @@ Schema: [docs/schema.md](docs/schema.md). Local HTML: `npx fdeops dashboard`.
 
 ## Who this is for
 
-| You are | What this is |
-|---------|----------------|
-| **Forward Deployed Engineer** | Client work that has to survive Monday morning |
-| **Consultant / contractor on site** | The engagement stops resetting every morning |
-| **Solutions architect** | Politics and architecture in the same record |
-| **Agency, 3–5 clients** | One `.fde/` each — they stop blurring |
-| **Fractional CTO on client work** | System of record for the embed, and the billable trail |
+You embed with a customer and an AI coding agent. Take this on the ground. Discovery through signed outcome lives in `@fde`. One `.fde/` per client so they do not blur.
+
+If you only write code in your own repo with no client record to defend, you do not need this kit.
 
 ---
 
 ## Your data stays yours
 
-Local only — `git` + files, no network, no telemetry. Plain markdown. The model sees client code only when you point the AI coding agent at it. `<private>` is redacted from CLI, dashboard, and hooks. Nothing is written until you confirm. `~/fde-engagements` is in `$HOME`; iCloud/Dropbox is an NDA incident waiting.
+Local only - `git` + files, no network, no telemetry. Plain markdown. The model sees client code only when you point the AI coding agent at it. `<private>` is redacted from CLI, dashboard, and hooks. Nothing is written until you confirm. `~/fde-engagements` is in `$HOME`; iCloud/Dropbox is an NDA incident waiting.
 
 [PRIVACY.md](PRIVACY.md) · [SECURITY.md](SECURITY.md)
 
@@ -272,20 +312,21 @@ Local only — `git` + files, no network, no telemetry. Plain markdown. The mode
 
 ## Principles
 
-- **The artifact is the memory** — producing the work and recording it are one action
-- **Methods, not autonomy** — the kit says what to check; judgment stays yours
-- **Brief is a hypothesis** — discover before building the wrong thing
-- **Evidence on every claim** — these files get defended in the room
-- **One customer, one folder** — context never bleeds
+- **The artifact is the memory** - producing the work and recording it are one action
+- **Ground loop** - name the slice, characterise their code, prove it where they live, log the outcome
+- **Skills, not autonomy** - the kit says what to check; judgment stays yours
+- **Brief is a hypothesis** - discover before building the wrong thing
+- **Evidence on every claim** - these files get defended in the room
+- **One customer, one folder** - context never bleeds
 
 ---
 
 ## Contributing
 
-**[Subash Natarajan](https://www.linkedin.com/in/subashn/)**. [Issues](https://github.com/suboss87/fdeops/issues) · [CONTRIBUTING.md](CONTRIBUTING.md)
+**[Subash Natarajan](https://www.linkedin.com/in/subashn/)**. [Issues](https://github.com/suboss87/fdeops/issues) · [Discussions](https://github.com/suboss87/fdeops/discussions) · [CONTRIBUTING.md](CONTRIBUTING.md) · [Code of Conduct](CODE_OF_CONDUCT.md)
 
-Methods should be **specific** (actionable steps), **verifiable** (an artifact in `.fde/`), and **minimal**. The `fde` CLI stays local-only.
+Skills should be **specific** (actionable steps), **verifiable** (an artifact in `.fde/`), and **minimal**. The `fde` CLI stays local-only.
 
 ## License
 
-MIT — use these skills on client work.
+MIT - use these skills on client work.

package/adapters/AGENTS.md

@@ -4,9 +4,9 @@ You are the AI coding agent for a **Forward Deployed Engineer (FDE)** - the huma
 
 ## Entry
 
-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.
+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 ordinary code edits, TypeScript, unit tests, refactors, or git commits.
+Do **not** load `@fde` for a one-line typo in an unbound repo. On a bound client, stay on `@fde` for POC, slices, characterisation, on-site proof, 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

@@ -4,9 +4,9 @@ Context for Gemini CLI when assisting a **Forward Deployed Engineer (FDE)** - th
 
 ## Entry
 
-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.
+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 ordinary code edits, TypeScript, unit tests, refactors, or git commits.
+Do **not** load `@fde` for a one-line typo in an unbound repo. On a bound client, stay on `@fde` for POC, slices, characterisation, on-site proof, 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

@@ -62,7 +62,7 @@ The model reads SKILL.md, routes to the right skill, and produces artifacts in y
 
 ## Model size recommendations
 
-The methodology is detailed (31 methods, routing logic, evidence format, memory contract). Larger models handle it better:
+The methodology is detailed (31 skills, routing logic, evidence format, memory contract). Larger models handle it better:
 
 | Model class | Experience |
 |-------------|-----------|

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 it works](../README.md#how-it-works).
 
 ## What goes where
 
@@ -31,4 +31,4 @@ Defaults to the current directory if no path is given. Existing files are never
 
 ## The principle
 
-The adapter only tells the tool **where the brain is and how to behave**. All the method - the 31 methods, the overlays, the memory contract - lives once in `skills/fde/SKILL.md`. Update the brain, every platform gets it. That's why fdeops feels native in whatever the FDE already uses, without five things to keep in sync.
+The adapter only tells the tool **where the brain is and how to behave**. All 31 skills, the overlays, and the memory contract live once in `skills/fde/SKILL.md`. Update the brain, every platform gets it. That's why fdeops feels native in whatever the FDE already uses, without five things to keep in sync.

package/adapters/copilot-instructions.md

@@ -4,9 +4,9 @@ You are the AI coding agent for a **Forward Deployed Engineer (FDE)** - the huma
 
 ## Entry
 
-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.
+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 ordinary code edits, TypeScript, unit tests, refactors, or git commits.
+Do **not** load `@fde` for a one-line typo in an unbound repo. On a bound client, stay on `@fde` for POC, slices, characterisation, on-site proof, 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

@@ -9,9 +9,9 @@ You are the AI coding agent for a **Forward Deployed Engineer (FDE)** - the huma
 
 ## Entry
 
-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.
+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 ordinary code edits, unit tests, refactors, or git commits.
+Do **not** load `@fde` for a one-line typo in an unbound repo. On a bound client, stay on `@fde` for POC, slices, characterisation, on-site proof, 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.
@@ -21,7 +21,7 @@ Do **not** load `@fde` for ordinary code edits, unit tests, refactors, or git co
 
 Read and write engagement files under the workspace's bound engagement: run `fde resume` to resolve it (binding created once with `fde resume --init <name>`; default `~/fde-engagements/<name>/.fde/`). `FDEOPS_ENGAGEMENT` (expand `~`) overrides when set. Use `./.fde/` only when the engagement approves it and it is gitignored.
 
-**On every session entry (before other work):** run `fde triage` (fallback `node ~/.claude/fdeops/fde.js triage`, then `fde resume`). Lead with that TRIAGE block — trust, phase, open risks, next action, record owner/hash. Do not invent stakeholders or status.
+**On every session entry (before other work):** run `fde triage` (fallback `node ~/.claude/fdeops/fde.js triage`, then `fde resume`). Lead with that TRIAGE block - trust, phase, open risks, next action, record owner/hash. Do not invent stakeholders or status.
 
 You run the CLI for deterministic work - `fde scan | log | debrief | prep | doctor | receipts | status | dashboard` - instead of improvising shell or handing commands to the human.