agentfootprint
Version:
The explainable agent framework — backtrack a wrong answer to the exact context that caused it (evidence, not guesses). Built on footprintjs.
24 lines • 1.29 kB
JavaScript
;
/**
* protocolAdapter — the port a wire protocol implements to speak for a run.
*
* OUR side of the port is the run's typed event stream, exactly as the record
* serves it (every listener's view: the placeholder wherever a redaction policy
* selected a value), and how the run settled. A protocol adapter turns that
* into its own events; a framing strategy (`stream.ts` · `SseFraming`) turns
* each of those into bytes. AG-UI (`agentfootprint/ag-ui`) is one adapter; a
* future protocol is one more, with no change to the runner, the event stream
* or the framing seam.
*
* An adapter reads the SERVED stream only. That is the whole redaction story
* for every protocol at once: what a policy hides never reaches an adapter, so
* no adapter can put it on a wire.
*
* A host that serves a protocol over a request (`streamHandler`) asks one more
* thing of it — {@link ProtocolAdapter}: read a request as UNTRUSTED input, and
* plan the turn from it and from what the SERVER holds for the conversation.
* The request decides nothing the server owns: who is calling, which thread is
* theirs, what was said before, what a paused run is waiting on.
*/
Object.defineProperty(exports, "__esModule", { value: true });
//# sourceMappingURL=protocolAdapter.js.map