The autonomy direction: agents that run on events, not human prompts.
- internal/harness/agent-flow: a runnable, deterministic demo — a
user.created broker event drives a Flow that hands off to a registered
agent (FlowAgent), which creates a workspace and sends a welcome over
real RPC. Only the LLM is mocked; passes under -race.
- blog/21: 'When the Event Is the Prompt' — the shift from agents you
talk to, to agents that act on their own; where microagents become
real; and the honest bar autonomy raises (guardrails, observability,
durable/resumable execution — the next things to build).
Co-authored-by: Claude <noreply@anthropic.com>
* docs: group README features by section (AI / Framework / DX)
The features table repeated 'AI' down the Category column. Split into
three grouped tables — AI, Framework, Developer experience & deployment —
dropping the repetitive column. Adds a Guardrails row (MaxSteps,
ApproveTool).
* test: flow-to-agent end-to-end in the harness
Proves 'Flow triggers, Agent reasons': a workflow with FlowAgent hands an
event to the registered conductor agent over RPC, which plans, creates
tasks, and delegates to comms — the whole chain over real RPC with only
the LLM mocked. Deterministic (shared in-memory registry, no sleeps),
passes under -race.
* blog: 'The Evolution of Microservices' (#19)
A technical history of distributed-systems eras — the monolith's
coordination cost, the distributed-systems tax, containers and
declarative orchestration, the service mesh, and the modular-monolith
correction — establishing the durable unit (named, typed, discoverable,
independently deployable) that every runtime wave required. Then the
technical argument for agents: an LLM tool call needs exactly a service
interface, so the caller shifts from deterministic code to a reasoner
that composes typed capabilities from intent, with the honest caveats
(non-determinism, cost, guardrails). Not a product pitch.
---------
Co-authored-by: Claude <noreply@anthropic.com>
* rename coordinator agent to conductor in example and docs
* add plan & delegate integration harness
Runs the real go-micro stack end to end — services, registry, RPC, the
agent loop, store, and delegate-first routing — with only the LLM mocked
by a deterministic provider. Proves discovery, tool execution, plan
persistence, and agent-to-agent delegation over RPC work without an API
key; swap the provider to run the same flow against a live model.
* test: deterministic CI integration test + provider flag for harness
- main_test.go: TestPlanDelegateEndToEnd drives the full real stack
(services, RPC, agent loop, store, delegate-first routing) over a
shared in-memory registry — no mDNS, no sleeps. Asserts 3 tasks
created via RPC, plan persisted to the store, and delegation reaching
the comms agent (notify called once). Passes under -race, ~0.03s.
- main.go: add -provider flag (defaults to mock) and key detection so the
same harness runs against a live model with no code change.
* chore: gitignore built harness/example binaries
---------
Co-authored-by: Claude <noreply@anthropic.com>
Asim Aslam