fdeops 3.6.1 → 3.7.1

package/README.md

@@ -1,19 +1,29 @@
-# fdeops
+# FDEOps
 
-**Your AI coding agent forgets your client every morning. fdeops remembers.**
+**Your AI agent forgets your client every morning. fdeops remembers.**
 
 [![npm version](https://img.shields.io/npm/v/fdeops)](https://www.npmjs.com/package/fdeops)
 [![CI](https://github.com/suboss87/fdeops/actions/workflows/validate.yml/badge.svg)](https://github.com/suboss87/fdeops/actions)
 [![License: MIT](https://img.shields.io/badge/License-MIT-blue.svg)](LICENSE)
 [![Node](https://img.shields.io/badge/node-%3E%3D18-brightgreen)](https://nodejs.org)
 
-Built for **Forward Deployed Engineers** - engineers embedded at a client, from first meeting to final handoff. Works the same for consultants, agency developers, solutions architects, and fractional CTOs.
+The **second brain for Forward Deployed Engineers** - engineers embedded at a client, from first meeting to final handoff. Works the same for consultants, agency developers, solutions architects, and fractional CTOs.
+
+```
+  land      discover      plan      build      ship      close
+    |           |           |         |          |         |
+    +-----------+-----------+---------+----------+---------+
+          the fieldbook (.fde/) - one per engagement
+             written as a side effect of the work
+```
+
+Describe your situation - `@fde` routes to the phase, runs the method, and every artifact lands in that shared memory. Nothing to maintain by hand.
 
 ---
 
 ## The problem
 
-Your AI coding agent's memory is scoped to a **repo**. Client work isn't: one engagement spans several repos, a dozen stakeholders, and decisions made in meetings your agent never saw. That context lives in rooms, chats, and hallway conversations - nothing writes it down where your tools can use it.
+Your AI agent's memory is scoped to a **repo**. Client work isn't: one engagement spans several repos, a dozen stakeholders, and decisions made in meetings your agent never saw. That context lives in rooms, chats, and hallway conversations - nothing writes it down where your tools can use it.
 
 fdeops adds the missing layer: memory scoped to the **client** - plain markdown at `~/fde-engagements/<client>/.fde/`, written as a side effect of doing the work. Local only, zero dependencies, no network, no telemetry.
 
@@ -41,15 +51,15 @@ fdeops adds the missing layer: memory scoped to the **client** - plain markdown
 **2. Bind your client workspace** - run once, inside the workspace:
 
 ```bash
-fde resume --init acme
+fde resume --init garvey
 ```
 
-fdeops' `--init` creates the engagement memory at `~/fde-engagements/acme/.fde/` (plain markdown, private to your machine) and binds this workspace to it. The hooks read that binding - context auto-loads at session start, auto-captures at session end. That is the whole setup.
+fdeops' `--init` creates the engagement memory at `~/fde-engagements/garvey/.fde/` (plain markdown, private to your machine) and binds this workspace to it. The hooks read that binding - context auto-loads at session start, auto-captures at session end. That is the whole setup.
 
 **3. Work**
 
 ```text
-@fde I just got the brief. New client, payments platform, 3-week timeline.
+@fde I just got the brief. New client, payments platform, they want it live before their Q3 audit.
 ```
 
 `@fde` is the one skill fdeops installs. Describe what's happening; it routes to the right field method and the memory writes itself. Full workflow: [docs/USAGE.md](docs/USAGE.md).
@@ -120,8 +130,8 @@ fde scan                          # day-1 recon + ASK ON DAY 1 questions (works
 fde resume                        # load this workspace's engagement
 fde resume --init <client>        # THE setup step: create + bind an engagement
 fde debrief notes.md              # route meeting notes into memory (also reads stdin)
-fde log decision "descope agreed with Dana"
-fde log contact "Diana gone quiet" --signal amber
+fde log decision "descope agreed with Kowalczyk"
+fde log contact "Denise gone quiet" --signal amber
 fde receipts <term>               # dated search; no hit = a gap in the record, not proof of absence
 fde status                        # portfolio triage across all clients (red > amber > green)
 fde dashboard                     # render every engagement into one offline HTML fieldbook
@@ -131,7 +141,9 @@ The latest dated `[signal:...]` token per stakeholder drives the trust column in
 
 <p align="center"><img src="media/terminal-demo.svg" alt="fde CLI - status, scan, dashboard" width="720"/></p>
 
-<p align="center"><img width="794" height="571" alt="FieldBook" src="https://github.com/user-attachments/assets/349a223e-0c5e-4300-a8fe-9e3bb042cbbe" /></p>
+`fde dashboard (FieldBook)` renders every engagement into one offline HTML fieldbook - engagements sorted by trust, next action and open risks per client, one glance to know where to start:
+
+<p align="center"><img width="1336" height="624" alt="Screenshot 2026-07-08 at 12 45 07" src="https://github.com/user-attachments/assets/5683614c-7730-4a3a-860d-185053a377eb" /></p>
 
 ---
 

package/bin/check.js

@@ -182,8 +182,8 @@ else ok('SECURITY.md')
 
 const exampleFiles = ['reality.md', 'decisions.md', 'delivery.md', 'stakeholders.md']
 for (const f of exampleFiles) {
-  const p = path.join(root, 'examples', 'acme-payments', '.fde', f)
-  if (!fs.existsSync(p)) fail(`examples/acme-payments/.fde/${f} missing`)
+  const p = path.join(root, 'examples', 'garvey-payments', '.fde', f)
+  if (!fs.existsSync(p)) fail(`examples/garvey-payments/.fde/${f} missing`)
 }
 ok('examples walkthrough files')