Jido governed execution is owned by jido_integration.
Do not add a Jido adapter to the :inference package. :inference owns the
semantic contract and adapter behaviour. Jido Integration owns durable run
records, route selection, leases, credential references, replay, review packets,
and platform projections.
Governed inference is still required platform scope. The ownership boundary is
package placement: :inference keeps standalone semantic contracts, and
jido_integration implements the governed adapter that carries authority refs,
credential handles or leases, target grants, and redacted evidence.
The intended dependency direction is:
jido_integration
-> depends on :inference
-> implements a Jido-owned module satisfying Inference.AdapterThat lets standalone applications use direct adapters while governed deployments opt into Jido:
application
-> Inference.Client
-> Jido-owned Inference.Adapter implementation
-> Jido Integration inference runtimeThe Jido-owned adapter should map:
Inference.Requestinto Jido inference request/command contracts;- Jido durable result and review ids back into
Inference.Response; - Jido route, policy, credential, replay, and review metadata into
redacted
Inference.Tracemetadata. - universal auth authority refs, connector or provider account refs, lease refs, and target refs into redacted trace metadata without raw credential material.
Shared Contract Checklist
When changing shared request or response semantics used by governed adapters:
- preserve
Inference.Client.defaults; - preserve adapter-owned
Inference.Request.options; - prove request-level options override client defaults;
- keep adapter-internal compatibility options out of provider/runtime option bags unless the adapter documents that forwarding;
- propagate provider-reported usage, cost, finish reason, object output, and tool-call fields when the runtime reports them;
- do not invent provider-reported values;
- run this package's full gate and the governed adapter owner's gate.