fdeops 3.7.0 → 3.7.1
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +16 -6
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -1,19 +1,29 @@
|
|
|
1
|
-
#
|
|
1
|
+
# FDEOps
|
|
2
2
|
|
|
3
|
-
**Your AI
|
|
3
|
+
**Your AI agent forgets your client every morning. fdeops remembers.**
|
|
4
4
|
|
|
5
5
|
[](https://www.npmjs.com/package/fdeops)
|
|
6
6
|
[](https://github.com/suboss87/fdeops/actions)
|
|
7
7
|
[](LICENSE)
|
|
8
8
|
[](https://nodejs.org)
|
|
9
9
|
|
|
10
|
-
|
|
10
|
+
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.
|
|
11
|
+
|
|
12
|
+
```
|
|
13
|
+
land discover plan build ship close
|
|
14
|
+
| | | | | |
|
|
15
|
+
+-----------+-----------+---------+----------+---------+
|
|
16
|
+
the fieldbook (.fde/) - one per engagement
|
|
17
|
+
written as a side effect of the work
|
|
18
|
+
```
|
|
19
|
+
|
|
20
|
+
Describe your situation - `@fde` routes to the phase, runs the method, and every artifact lands in that shared memory. Nothing to maintain by hand.
|
|
11
21
|
|
|
12
22
|
---
|
|
13
23
|
|
|
14
24
|
## The problem
|
|
15
25
|
|
|
16
|
-
Your AI
|
|
26
|
+
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.
|
|
17
27
|
|
|
18
28
|
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.
|
|
19
29
|
|
|
@@ -131,9 +141,9 @@ The latest dated `[signal:...]` token per stakeholder drives the trust column in
|
|
|
131
141
|
|
|
132
142
|
<p align="center"><img src="media/terminal-demo.svg" alt="fde CLI - status, scan, dashboard" width="720"/></p>
|
|
133
143
|
|
|
134
|
-
`fde dashboard` 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:
|
|
144
|
+
`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:
|
|
135
145
|
|
|
136
|
-
<p align="center"><img width="
|
|
146
|
+
<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>
|
|
137
147
|
|
|
138
148
|
---
|
|
139
149
|
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "fdeops",
|
|
3
|
-
"version": "3.7.
|
|
3
|
+
"version": "3.7.1",
|
|
4
4
|
"description": "Field kit for engineers embedded in client work - a real CLI (recon, memory, portfolio), one @fde skill with field judgment on top, and hooks that make it automatic. Claude Code plugin and any agent that loads skills.",
|
|
5
5
|
"bin": {
|
|
6
6
|
"fdeops": "bin/install.js",
|