3. **Atomic admission seam, not another scheduler.** Add a small server-only `RunAdmission` interface in orchestration V2. V2 resolves the authoritative owner from the target thread and any originating owned session, independently of caller-supplied fields. Work or assistant adapters resolve durable fence/configuration references from that binding. Every run-creating or promoting command validates the resolved owner, compares current SQL authority, and binds the admitted run in the same transaction as its existing receipt/events/outbox. Caller references can only narrow or match this authority, never remove it. Replays return the recorded result; revoked authority cannot authorize a different command. Before provider start, queued runs recheck current permission/lifecycle and the retained assignment fence, then use the admitted configuration snapshot. The interface performs SQL-only checks inside the transaction; no model, provider, Git or network effects there. Keep domain-specific checks in their domain adapters and composition, avoiding V2 importing Work modules. Unowned ordinary paths retain upstream behavior. Owned inference is denied while disabled/archived/revoked, including internal continuation and wake paths; pure result recording, archive retention, cleanup and cancellation may proceed without starting inference. Owner lookup and checks are mandatory inside the serial V2 commit and again at provider start, not merely in ThreadManagementService. A durable domain intention can retry the same command; V2 owns effect retries and native recovery. Unproved native starts/stops remain uncertain and retain reservations until reconciliation.
0 commit comments