Skip to main content
A professional task may involve several decisions, tools and model calls. Gateway owns the execution of each admitted inference, not the overall promise to finish that task. This separation is important even when the professional behavior and Gateway run inside the same Platform process.

​
Follow a proposed classification

Imagine a professional component preparing an expense classification. It asks Gateway for a structured suggestion, reviews the result and decides whether another authorized action is needed. Gateway can explain the inference: which approved offering was selected, which attempts occurred, what output was validated and what usage is known. The professional’s criterion owner decides whether the classification meets the task’s requirements. Posting a journal, accepting a commitment or charging a customer requires the corresponding owner’s action. A model-generated instruction does not perform those actions.

​
The caller keeps continuity across interruptions

A durable caller records its original invocation before send and retains the answer when replay is required. After restart, it resolves that invocation rather than silently spending another inference to recreate the result. If the task legitimately chooses new work, it uses a distinct stable identity. The earlier uncertainty, cost and responsibility do not disappear. Aggregate task limits still apply. Equal text in two independent turns must not be confused with a repeated delivery of the same turn. A content digest helps check what was requested; it cannot be the sole identity of all business actions.

​
Cancellation follows responsibility

A person viewing the task can disconnect without necessarily cancelling the durable owner. The true owner’s cancellation must, however, propagate to the owned Gateway call under the applicable contract. Gateway closes local work and records the resulting facts. It cannot infer that remote provider computation or billing stopped merely because the viewer or local transport closed.

​
How to read AccelMars’s names

Guild/Platform names the current reviewed caller arrangement. Interim Guild commitments remain Guild-owned. Work/Execution describes target ownership after an accepted implemented transfer; it must not be drawn as already active alongside the current owner. CRL describes the composed responsibility commitments around continuity, correction and accountable professional behavior. It is not another model-execution service. TENURE is the delivery program, not a runtime actor with its own cancellation authority. These distinctions prevent a diagram from transferring responsibility that the implementation has not actually transferred.

​
A transfer must preserve unfinished obligations

Moving a caller or storage boundary must preserve original invocation identities, active commitments, saved results and unresolved notification or money obligations. Copying current rows while losing a replay fence can make old work appear new. The new owner needs an accepted handoff, compatible interfaces and evidence that the old responsibilities remain covered. Renaming a module or publishing a new diagram is not that handoff. See Restarting without repeating the work and The owners of a payment for two concrete consequences.