Read and write remain separate responsibilities
- State changes stay bound to a valid local ownership boundary.
- Cluster-wide read views are handled as explicitly distributed operations.
- Partially unavailable sources are not silently presented as a complete result.
- Commands without clearly resolvable ownership are not redirected to an implicit global path.
Public boundary
The website explains the consistency and responsibility distinction at architecture level.
What this page explicitly does not claim: The public framing stays limited to distributed views, ownership and result semantics.