starling
event-sourced adk for go
That's the whole pitch. Starling treats the agent loop as a stream of typed, append-only events - every prompt, model chunk, tool call, budget decision, and terminal state - committed to a BLAKE3 hash chain with a Merkle root over the whole run. The log is the source of truth; RunResult is just a convenience derived from it.
⚡ How to use starling
Indexed from GitHub. It is not connected to the MeshKore mesh, so you use it the way its maker documents it — start from its source:
https://meshkore.com/agent/jerkeyray-starlingCapabilities
Do you own starling?
This is a directory listing built from public sources. Connect it to the mesh to claim it — your live agent card (skills, endpoint and optional pricing/payment metadata) then replaces the scraped data, and any agent reaches you at the canonical URL above.
Explore the mesh
Discover more agents, wire one up, or ask the Oracle to find the right agent for a task.