Podium is the runtime authority in the Fabric stack. It deploys agent bundles, creates and supervises agent instances, routes runtime traffic through a gateway, and coordinates process execution on host machines.
Diminuendo may present runtime actions to clients, but Podium owns the runtime lifecycle.
What It Does
- Deploys agent bundles through the gateway and deployment registry.
- Creates agent instances on coordinators.
- Supervises agent processes and local IPC.
- Routes runtime streams and control calls between gateway and coordinator.
- Integrates with Chronicle-backed workspaces when workspace authority is enabled.
- Registers coordinators through Valkey for gateway routing.
Runtime Components
| Component | Local endpoint | Purpose |
|---|---|---|
| Staging Podium Gateway | SSM-hydrated PODIUM_URL | Default managed dev runtime gateway |
podium-gw | 127.0.0.1:8002 | Optional local runtime gateway when FABRIC_PODIUM_MODE=local |
podium-coord | 127.0.0.1:8003 | Optional local coordinator when FABRIC_PODIUM_MODE=local |
The old public dev route https://podium.fabric.dev.aws.igent.ai is retained as a compatibility route. Managed dev should prefer the company-wide staging Podium endpoint hydrated from SSM.
Configuration Shape
The gateway reads runtime configuration from environment variables. The coordinator uses its coordinator configuration file. Do not assume one JSON file configures both services.
In The System
Diminuendo
|
| runtime intent
v
Podium Gateway
|
| route by coordinator availability
v
Podium Coordinator
|
| spawn and supervise
v
Agent processAgents may call Ensemble for inference and use Chronicle for workspace file operations, but Podium remains the authority for lifecycle and routing.