ChannelObserver

Sees exactly what was sent to the model — the same array that becomes the request body. A gateway records what the agent DID: which tools it called, what came back, which gate stopped it. It records nothing about what the agent was GIVEN — the tools it was offered, the conversation it received, the model it was asked of. That asymmetry is why debugging an agent has meant putting a proxy in front of the endpoint and reading the wire by hand. This is the seam that removes the proxy. It hands over the payload at the point of serialization, so a consumer can record what travelled instead of rebuilding what should have travelled. The distinction is the whole point: a view that reconstructs from code eventually disagrees with the wire, and then it is not a view of the system — it is a second, quieter opinion about it. Implementations MUST NOT throw and MUST NOT be slow. Observing a channel may not change it.

abstract public function observe(string $uri, array $payload): void

Hands over one outbound call at the moment it is serialized. Called once per request, with the payload that becomes the body — not a copy assembled alongside it. A consumer that records this is recording what travelled.

Parameters