FCoP 3.0: A filesystem-native pattern for making agent behavior observable
Hey Cursor community,
I’ve been thinking about a problem many of us hit when working with agents:
you can’t govern what you can’t observe.
In normal chat-based agent workflows, a lot of important behavior disappears into context. The agent reasons, decides, maybe hands something to another agent, but unless that action lands somewhere durable, there is nothing to inspect later.
The pattern I’ve been experimenting with is simple:
make agent behavior land as files.
Not as a database, not as middleware, not as a hidden runtime state. Just Markdown files with lifecycle semantics. A task is a file. A report is a file. A review is a file. The directory position tells you whether something is inbox, active, under review, done, or archived.
The idea is not to slow agents down. It is to make their speed observable.
The sentence I keep coming back to is:
Speed is not the problem. Unobservable speed is the problem.
You don’t build a brake. You build a track.
I’m sharing this as an open-source experiment, not as a product pitch. The part I’m most interested in is the pattern itself: filesystem-native observability for agent collaboration.
Full write-up:
Curious if anyone else is exploring similar patterns.
How are you making agent behavior observable in your own workflows?