Framework, protocol, and event-system breadth is part of the finish-line product.
This page makes the execution substrate public from the umbrella surface. It shows the frameworks, protocol fronts, bridge transports, and event-system families that let agents and machines reach the same runtime spine from CLI, service, graph, stream, callback, and coordination environments without inventing a different product each time.
Framework family
The framework lane makes it obvious that the runtime already meets builders where they are. The public story is not just one protocol and one command; it includes serious orchestration and agent-runtime families that can converge back into the same machine-payment and proof spine.
- Featured frameworks: 6
- Framework first-run flows: 1
- Phase 6 ecosystems: 4
- Phase 6 runtime modes: 3
- First surfaced ecosystem: langgraph
Framework lane summary · Phase 6 summary · LangGraph summary · LangChain summary · AutoGen summary · Semantic Kernel summary
Protocol and bridge family
The protocol lane keeps the default runtime path clear while still exposing the breadth that real machine systems need. This is where MCP, A2A, A2C, and the bridge transports live together as one discoverable family.
- Featured protocol fronts: 10
- Protocol first-run flows: 1
- First-party callable fronts: 4
- Launch-default fronts: 1
- Supported bridge protocols: 7
Protocol lane summary · Adapter/protocol truth · MCP lane · A2A lane · A2C lane · Integration protocols
Event-system family
Kafka, NATS, MQTT, and webhook-oriented delivery are not side notes. They are part of the machine-operating substrate that lets the runtime live inside high-frequency, asynchronous, device, and event-driven systems.
- Phase 7 ecosystems: 4
- Event-system lanes: 4
- Event modes: 3
- Stream modes: 3
- Subject modes: 3
- Callback modes: 3
Phase 7 summary · Event systems summary · Kafka summary · NATS summary · MQTT summary · Webhook event bus summary
Why this layer matters
A real 3.0.0 machine stack has to be usable from more than one happy-path shell. This ecosystem surface keeps the public story honest by showing that the runtime already has framework, transport, coordination, and callback depth for real agentic and machine-to-machine environments.
- Agents can reach the runtime from their existing orchestration environment instead of rewriting everything around one custom interface.
- Protocols and event systems stay subordinate to the same runtime, payment, and proof spine rather than forking the product.
- The umbrella site now surfaces execution substrate depth alongside money, proof, support, and release surfaces.
- This keeps the final 3.0.0 bar focused on real capability, not reduced claim language.
Agents · Support · Money-in · Operator shell · Claim · Site map