ACP is an edge adapter for clients that speak the Agent Client Protocol. In the current Fabric architecture, ACP is not the internal source of truth and it is not the protocol that defines service ownership.
Diminuendo may expose ACP-compatible methods and notifications, then map them into Fabric conversation, stream, presentation, runtime, and resource semantics.
Adapter Flow
ACP-compatible client
|
| ACP JSON-RPC
v
Diminuendo ACP sidecar
|
| Fabric semantics and gateway policy
v
Diminuendo core
|
+--> Podium runtime
+--> Ensemble inference
+--> Unison resources
+--> Chronicle workspace authority when enabled
Good Fit
| Fit | Notes |
|---|---|
| Conversation sessions | Thread/turn style clients map naturally to Fabric conversation state |
| Streaming updates | ACP notifications can project Fabric stream events |
| Approvals and user input | Client-side approval flows can map to Fabric presentation/conversation events |
Boundary
ACP should not become a second runtime protocol, inference protocol, workspace protocol, or authorization model. The adapter should preserve Fabric identity and permissions and return explicit unsupported errors when a Fabric concept cannot be represented.
For canonical protocol work, use Fabric Protocol, Fabric Profiles, and Edge Adapters.