@grove_research Congrats. It'll be very interesting to see where you take this.
If you want to add "more structure" on atproto, see if `atseq` pushes your buttons: https://t.co/Czsne5fBJv
in my experience, agent skills can totally remain relevant over time / across model generations, *as long as they are more spec than step-by-step instructions*
eg: specifying a good format for a doc output, a good flow for interviewing a human
"When people communicate face to face, they externalize their models so they can be sure they are talking about the same thing. Even such a simple externalized model as a flow diagram or an outline... serves as a focus for discussion." https://t.co/7c3graf5qa
I'm continuing to build out "fold over a sequenced log" experiments, because they're a really nice foundation for applications where the users are people and agents.
Here are four infrastructure variants so far.
And this category of "situational apps": I think it's a natural evolution of https://t.co/Qwxb7qAn6z.
Unlike "multi-sided platforms" (ebay, uber, doordash...) where the situation is repeatable: so many of our daily interactions are multi-sided but *unique*. Agents can help!
And this category of "situational apps": I think it's a natural evolution of https://t.co/Qwxb7qAn6z.
Unlike "multi-sided platforms" (ebay, uber, doordash...) where the situation is repeatable: so many of our daily interactions are multi-sided but *unique*. Agents can help!
I'm continuing to build out "fold over a sequenced log" experiments, because they're a really nice foundation for applications where the users are people and agents.
Here are four infrastructure variants so far.
The sequencer isn't "global". Next experiment may incorporate the interesting "CTEG" work by Simon Foldvik - I think by tracking causal dependencies (as gitseq does) we can efficiently implement cross-partition transactions.
https://t.co/0Ym6AuHGo1