You (human FDE) bring judgment on site; your AI coding agent loads fdeops skills and .fde/ memory on your laptop-under your control.
Agent = AI software only. See README § Who this is for.
- fdeops runs on your machine - not on servers or CI you do not operate.
- Default notes path:
~/fde-engagements/<name>/.fde/, created byfde resume --init <name>. - Bind each workspace once with
fde resume --init <name>- the registry then resolves the right engagement for every session and hook automatically. (FDEOPS_ENGAGEMENTremains as an advanced override: install.md.) - Only
@fde- routing is automatic. - Notes are confidential - same care as work papers; never commit raw
.fde/to shared git.
node bin/install.js # once per machine (skills + hooks)
cd <client-workspace>
fde resume --init <engagement-name> # once per workspaceWork in your normal workspace. In the AI chat, type @fde with what is happening now.
| Engagement | Memory | Work (examples) |
|---|---|---|
| Project A | ~/fde-engagements/project-a/.fde/ |
repo, VPN, or paired env |
| Project B | ~/fde-engagements/project-b/.fde/ |
separate workspace |
Portfolio: tell @fde “show my portfolio” - it reads every engagement folder separately and generates the dashboard.
| Situation | Action |
|---|---|
| No code access yet | Land + discover; fill brief.md, stakeholders.md |
| Extra files forbidden in workspace | Notes only under ~/fde-engagements/ - the registry binding lives outside the workspace, so nothing is added to their tree |
Can't run fde resume --init in an environment |
Set FDEOPS_ENGAGEMENT=... (env var or one line in an allowed CLAUDE.md) as the override |
| Taking over from someone else | Tell @fde you're taking over - it runs the audit method and writes ground truth into your .fde/ |
| Trust problem vs outage | Say which in the @fde message |
npm run check