# Object authority is not global Domain authority Implemented 2026-09-14. An Object UUID remains a global identity, but a broad Domain capability must not authorize another Domain's Object simply because the caller knows its UUID. Read, Revision/history/projection, save and link checks reuse the same Object resolver. Broad Domain/Object-wildcard grants are considered only when the current Domain has a live semantic binding. A separately issued **exact Object grant** remains an intentional exceptional delegation, including an unbound Object. Without such a grant, foreign-only and unknown-origin unbound Objects fail closed. One readable local Path can still authorize Object reads. HTTP purge is stricter: all aliases must belong to this Domain and be individually deletable, with the complete binding set revalidated in the delete transaction. ## Create → save → bind The Object creation API now calls `CreateObjectInDomain`. Creation and insertion of `object_origins(object_uuid, domain_uuid, created_at)` are atomic. While an Object has **no live bindings anywhere**, this provenance permits the creating Domain's normal capability checks, preserving the separate create/save/bind API. It supplies scope, not a capability: a user still needs the requested grant. Once bindings exist, provenance is not a substitute for a current local binding. Moving the last binding to another Domain therefore removes the creating Domain's broad access. Explicit exact Object grants are not changed by moving Paths; revocation of those grants has its own authority lifecycle. Existing UUIDs and Paths are not rewritten. No unknown legacy unbound Object is silently assigned to the default Domain. Such objects require an exact grant or trusted local administrative recovery; this is a deliberate security boundary. New API-created provenance is not a claim that every historical CLI/import/Page creation recorded ownership. A future verified provenance migration must account for ambiguous multi-Domain history and asset references. Regression tests cover foreign reads/Revisions/saves/binds, wildcard versus exact grants, the API create/save/bind sequence, relocation, and unknown unbound Objects. Concurrent grant or namespace revocation during an already-authorized write still requires policy-version/transaction fencing across all write routes; the separate recursive mutation snapshot fixes do not imply that wider gate is complete.