The problem right now with something like this is you're trying to nail jello to a wall. People haven't figured out what an agent is yet, and trying to crystalize what people happen to be doing right now means in a few months, you're going to be obsolete.
don't think the "agent" abstraction is stable enough to standardize the behavior/runtime layer yet.
thing I'm trying to test is smaller: is that possible to standardize the outer contract around agents?
what inputs does it accept? what outputs does it promise? what model does it use? what prompt/template does it depend on? what tools can it call? what target should it be built or applied to?
so here it is intentionally not trying to describe the full control loop or become a runtime. it's more like a source-of-truth layer for the parts that are already showing up everywhere, even if the runtime patterns keep changing underneath.
I might be wrong, but my bet is that the runtime layer will keep changing, while the need for reviewable/diffable agent contracts will not.
Claude is a model, an agent is more like the full solution. Some would call Claude Code itself an agent. Agents do things, models are just models until you use them.
The post you replied about is regarding people not knowing what "agent" means, but you also wrote very little, so its hard to gauge what your angle was. Not sure why it was downvoted.
For hosted agents only, a Terraform provider probably makes sense.
The reason I didn’t start there is that Kastor has two paths:
1 - build: compile the spec into framework code, e.g. LangGraph
2 - plan/apply for agents hosted on platforms
Terraform is great for the second path, but awkward as the primary tool for the first one. I want the same agent spec to be able to produce code or manage a remote agent.
So I can imagine a Terraform provider being one target later, but I don’t think Terraform itself is the right tool/place for the whole thing.
Im wondering if you can expand it using TLA+ some how. I like the declarative language that compiles down to langgraph idea. Langgraph or hamilton/burr are two strong contenders for state machines. Maybe mix dbos or Temporal in there and you could almost have something to full declare the whole system
The codegen side is target-agnostic on purpose, LangGraph is just the first target. Burr (thanks for educating about that piece of tech) could be a good N-one, its state/transition model maps onto the spec real pretty.
Vercel's eve made a similar bet btw (files as source of truth, durable execution built in), except it's a runtime with its own platform underneath. With Kastor I want to stay one layer above and emit code for whatever runtime you pick.
Anyways, would love any kind of help to shape the direction, repo discussions and codebase is open :)
UPD: Looked into burr from dagworks deeper, it's actually a good target to support the codegen for, will investigate today and add into the scope of upcoming things.
17 comments
[ 0.47 ms ] story [ 41.9 ms ] threaddon't think the "agent" abstraction is stable enough to standardize the behavior/runtime layer yet.
thing I'm trying to test is smaller: is that possible to standardize the outer contract around agents?
what inputs does it accept? what outputs does it promise? what model does it use? what prompt/template does it depend on? what tools can it call? what target should it be built or applied to?
so here it is intentionally not trying to describe the full control loop or become a runtime. it's more like a source-of-truth layer for the parts that are already showing up everywhere, even if the runtime patterns keep changing underneath.
I might be wrong, but my bet is that the runtime layer will keep changing, while the need for reviewable/diffable agent contracts will not.
For hosted agents only, a Terraform provider probably makes sense.
The reason I didn’t start there is that Kastor has two paths:
1 - build: compile the spec into framework code, e.g. LangGraph
2 - plan/apply for agents hosted on platforms
Terraform is great for the second path, but awkward as the primary tool for the first one. I want the same agent spec to be able to produce code or manage a remote agent.
So I can imagine a Terraform provider being one target later, but I don’t think Terraform itself is the right tool/place for the whole thing.
Vercel's eve made a similar bet btw (files as source of truth, durable execution built in), except it's a runtime with its own platform underneath. With Kastor I want to stay one layer above and emit code for whatever runtime you pick.
Anyways, would love any kind of help to shape the direction, repo discussions and codebase is open :)
Thank you for showing those things!