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.

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.