Skip to main content

Concepts · 5 of 5

Governed invocation

Under v1alpha2 an admitted invocation is audited before it is dispatched, and a write learns the attempt it produced, so a lost answer is uncertain rather than silently retried.

contracts/service/v1alpha2/semantics.md, contracts/service/compatibility.md, contracts/operations/v1alpha1/semantics.md, crates/connectors-host/tests/http_audit_anchor.rs, crates/connectors-conformance/tests/client_v1alpha2.rs

Governed invocation

A service host whose service configuration names a private state directory (urn:connectors:config:v2:service) also serves POST /v1alpha2/invoke, the first v1alpha2 binding. Without state, that route answers unavailable and only the /v1/* routes are served. Describe stays on GET /v1/describe, and the request carries that descriptor's revision.

What the binding adds​

  • An audit anchor before dispatch. Every admitted invocation is recorded in the host's execution audit before the connector is called, and the answer carries audit_ref and audit_status. An anchor that cannot be written refuses the call before any connector work.
  • The attempt a write produced. An operation that writes gets an attempt record before its one dispatch, and the answer's mutation names it: attempt: {instance, id}, the original_request_id, replayed: false and the classification (applied on success). Reads carry no mutation.
  • Uncertainty kept. A write whose answer is lost after dispatch is outcome_unknown with its attempt, and it is not dispatched again. A refusal before dispatch carries no attempt.

Retained audit observations are held in memory and are lost when the host restarts.

The advanced contract exercises let you lose a response and watch the attempt stay uncertain, in a fictional in-memory model.