Capability Call
What It Models
A capability call retains one provider request across attempts and later investigation. It explains who asked, how the account was selected, what was sent at a safe summary level and whether the provider completed the work. Bindings are a facet of this object because they supply the account choice recorded by each execution.
Identity and Attributes
A generated execution identifier locates the call in its monthly partition and accompanies provider idempotency and investigation. The caller’s request key is unique for a capability within a workspace. Binding history continues the numbering at a capability major and scope.
The shared contract defines the requested operation and supported major. A binding selects an account at record, business-unit, application or workspace scope with required features, policy, revision and status. Scope changes append immutable snapshots, retaining up to two hundred recent revisions. Caller attribution includes the application or console actor, subject and selection context. The execution records the binding revision, account, release, deployment and selection explanation. A supplied request key accompanies a canonical-input fingerprint; execution records do not retain an original request for console retry. Synchronous or asynchronous mode is separate from accepted, running, retrying, uncertain, attention or settled status. Attempt records retain timing, outcome, error classification, provider request reference and optional diagnostic reference. Scalar summaries are limited to four kilobytes and exclude secret, personal and payment-instrument information. The response store retains the first answer for replay to an identical request. Derived investigation information shows the next lookup and whether automatic settlement has stopped. Archive reads mark records moved beyond the thirteen-month online retention window.
Relationships
Each served call and each binding name one connection.. Calls and bindings refer to the account without owning its record.. A call retains the release and deployment used and respects accepted installation capabilities.. Execution reads the catalogue and installation without modifying them.. An asynchronous or unanswered call can produce its applicable completion event at settlement.. The event store owns that event, written within the settlement transaction..
Invariants
A capability major and scope have one current binding, and replacing it increases the revision. A binding mutation appends a revision snapshot that application writers cannot alter. Within a workspace and capability, a request key returns its pending execution or retained result and refuses changed input. Provider attempts use the execution identifier for idempotency; work that may have reached the provider is investigated without resending. Safe retries of a money operation stop when the synchronous budget is spent, failing the call without queued continuation and releasing its key. The execution cannot exceed ten attempts, including attempts an operator requests. Settlement commits its result with at most one applicable completion event. An open circuit appears in the selection trace without rerouting the call to a different account. Resolution reads current workspace records within a read-only transaction on every request. A person records an investigation outcome without contacting the provider or reversing its work.
How It Is Stored and Shared
The integrations service owns bindings, execution partitions, attempts, key records, dispatch work and stored responses. Separate key records preserve request uniqueness across monthly partitions. Optional diagnostic payloads and archives use object storage; an application receives results through the gateway and completion events. Custom fields are not enabled.
Open Design Questions
Concurrent admission and the full circuit threshold still lack complete proof. Archived execution expiry is undecided. Investigation uses the account’s current release, so an upgrade during an uncertain call can change the adapter that looks it up.