Who it is for
For an international body
Shared on purpose, never by accident
A record several states can rely on cannot be one database they all write to. Each needs its own room, and the shared part has to move deliberately.
designed01 the claimA shared record without a shared database
Each member holds its own room and its own keys. What is shared is exported and imported as a signed package, so nothing crosses a border implicitly.02 what you would ask itQuestions in your own language
What do all of us agree on, and exactly where do we differ?Which member reported this, and when did the rest learn it?What did the shared record hold before this revision?03 what is true todayWhat answers right now
The public record answers now and reads the same for every member, with the evidence and both dates behind each line.04 what is being builtWhat is coming, and what proves it
Rooms owned by an organisation are being built now. The signed package that moves a record between them is designed, with the enclave it runs inside.05 where your data sitsYour room, and its walls
One room per member, exchanging nothing implicitly. A package says what it carries, who signed it, and when.06 how it is installedThe shapes this comes in
Dedicated - your cloud, your region, or your own data centre.Enclave - your air-gapped network, public knowledge carried in by signed package.07 what it refusesWhat it will not do
Nothing is ever erased, and a correction is a new dated line. No telemetry leaves unless you allow it, no model touches your content unless your own policy names it, and an answer says which date its public knowledge is from. An installation of your own calls nothing home.08 one way to startOne conversation, no form
Mail an engineer and a person replies, usually within two days. Nothing here routes through a queue.