Factory docs, home
Page navigation

Scope: Decoded EV2b routing through the actual private subscription host. Build review records accepted snapshots and current verification gates. No live MCP transport or application delivery is qualified.

Intelligence: none — Exact method routing, bounded JSON and fixed host error projection need no model judgement or new authority.

The caller binds one actual ProviderSubscriptionHost and Product. Authenticated principal/session/Product arrive outside params; fixed mcp-principal role reaches EV2's current authority checks. Constructor captures three methods without invoking ports. Dispatch copies descriptor-safe plain JSON, calls one method once and unwraps only the approved wire receipt. Attempt tokens remain private. No store, Journal, clock, retry, response cache, HTTP listener, SDK or delivery sender is added.

The caller owns raw UTF-8/duplicate-member/batch limits, authenticated routing, active request IDs, private logging policy, cancellation of response channels and quiet host maintenance. Reusing an ID does not replay a mutation; lost/late output remains attached to the original request/session. Host timeout is not terminal proof. Native Promise rejection is observed; generic thenables and accessor values are refused. The installed contract defines exact byte/depth/ID/result limits and unchanged wireError categories.

Runtime imports the existing subscription host, canonical JSON vocabulary, shared Promise observation and native Promise recognition. Neutral public types depend on actual subscription declarations. Original EV1/EV2/runtime/receipt/policy bytes remain protected. Current verification is recorded in build review. Real client metadata, authenticated service, callback delivery, final publication review, CI and live qualification remain separate gates.

Native fulfilment data is observed within the original descriptor traversal's shared identity set, depth and object-count bound. Observation-only faults cannot change the fixed refusal or an already completed host effect; a fulfilled Promise is never permission or a valid JSON value. Correction coverage separates actual binding/request/context refusals across both caller stores from instrumented completed acknowledgements.

Source: docs/agents/provider-events-rpc.md