Who Owns Effect Truth?
The mechanism that performs an action is not automatically the authority that determines what that action means in the durable state it affected.
Effect truth belongs to the semantics of the state that changed — not automatically to the component that executed, stored or displayed the action.
Authority is a decision right, not a physical location.
If the executor does not automatically own effect truth, who does?
Baranes answers with semantic ownership: the domain whose durable or external state was affected owns the authoritative determination under the evidence rules that apply to that effect.
The key word is semantic.
Authority is not physical location
Systems place data wherever it is operationally convenient. A worker writes a status row. A queue records delivery. A database records COMMITTED. A dashboard shows a green indicator. A Ledger may later accept a selected record.
Those mechanisms may be important, but storing or displaying information does not automatically grant authority over the proposition it describes.
RESPONSIBILITY != MODULEREPOSITORY != SEMANTIC OWNERA logical responsibility does not imply one dedicated service. And a repository or data store does not own every semantic fact it happens to contain.
What defines the affected domain
The domain is defined by what durable or external state the action intended to change and what rules make that state meaningful.
Repository effects can depend on repository identity, branch or object state and concurrency conditions. A publication effect can depend on what artifact is externally visible. A host effect can depend on live host state and its own observation rules.
The same shell, API client or SDK could participate in several kinds of action. Reusing an execution mechanism does not merge the semantics of those effects.
Why Baranes does not need one global truth oracle
There are two ways to pursue consistency. One is to centralize every domain’s semantics in one mechanism and ask it to decide everything. The other is to make authority placement consistent: each proposition has a clear owner, relevant evidence reaches that owner, and neighboring mechanisms cannot silently acquire its decision right.
Baranes uses the second model at the logical-architecture level.
“Does every domain need its own microservice?”
No. Semantic ownership is a decision-right boundary, not a service-count prescription. One process may realize several responsibilities; one responsibility may later be realized across several mechanisms.
Boundary / limit
This is a logical architecture claim. It does not prove that Baranes is currently physically implemented across multiple effect domains, and it does not freeze a physical service topology.