Content bytes
Place object data according to the organisation’s active regional model.
Regional control
For some organisations region is a compliance question, not a performance one. In Casewelt your organisation has a home region, and your content, the key material behind it and the audit record are all discussed as one placement decision rather than three separate ones. Core and Business run in the standard Casewelt region; choosing a specific region is part of an Enterprise agreement.
Example
If a write would put content somewhere your organisation has not agreed to, it does not happen. It stops, and both your administrators and whatever system made the request are told why.
That means moving between regions is a decision somebody makes on purpose, with planning behind it, not something that quietly follows an employee who happened to open a laptop in another country.
Placement model
Place object data according to the organisation’s active regional model.
Keep the key-wrapping and content-protection design aligned with that placement model.
Treat the product audit record as part of the governed organisation boundary, even when copies of events are delivered elsewhere.
How placement works
Each organisation is assigned a home region. Content bytes, wrapping-key context and the authoritative audit record stay inside that regional cell. A write that asks for another region is rejected with a visible placement conflict for operators and API clients.
Moving between regions is an explicit migration, planned and recorded as an organisation change.
Placement
We can map the organisation’s constraints to placement, conflict handling and evidence.