[stuartaxelowen]

Notes are options. Sometimes options for taking action later, sometimes as reference for related action. The bet when writing a note is that its risk adjusted return for those avenues is higher than the opportunity cost.

I also have similar thoughts on turning writing into action and re-entrance, would be interested to hear your thoughts:

https://blog.sao.dev/2025-threads/

This has proven to work well for me, but I’m chafing with git and agentic coding abstractions and looking for a unifying concept. Agent of empires doesn’t feel quite right, but is in the right direction.

[item007]

I read your post — the `thread` file structure (Bet / Context / Next steps / DoD / Log) is a really clean “re-entrance artifact” for both humans and agents.

One thought: it also gives you a natural closed-loop signal — Log + DoD changes are the feedback, not vague “AI memory”. A tool could surface notes as *options* only when a thread is active, then write back only via diffs to `Next steps` / `Log` (human-approved), keeping it deterministic.

For the git/agentic abstraction itch: what do you want as the single source of truth — the thread file, issues, or git events?