Agentic Surfaces
Surfaces
T9

Cross-border & Sovereignty

8 surfaces
9.1
Interaction design

Jurisdiction disclosure when data is processed

At the submit step, a three-part flag and label names where the data is processed, whose law can reach it, and whether it stays onshore, in place of text buried in a privacy policy.

Review and submit your application

Housing transfer · 14 fields completed. Nothing is sent until you submit.

Where your data goes
Processed in
Australia
Government data centers, Sydney and Canberra
Whose law can reach it
Australian jurisdiction
The operator is an Australian entity, and your data is held under Australian jurisdiction.
Stays onshore
Yes
No copy leaves the country, including for backup or support
Submitting accepts the processing described above.

If any part changes (a new processor, an offshore backup) the badge changes with it, at the same spot, before the next submission. The privacy policy elaborates; it does not substitute.
9.2
Interaction design

Data-sovereignty tiers for sensitive interactions

A "doorway" view leads with a plain-language verdict that the protection is already set to match the task, states it as a positive, and demotes whose law can compel the data to an opt-in detail instead of a color-only alarm.

Preview the disclosure for a different task
General feedback
Standard protection applies to your feedback.

General feedback. Standard protection applies to your feedback. General feedback reveals little about you. A standard assistant is suitable. Protection for this task: Standard.
9.3
Service design

AI system transparency registers

At the point of use, a single line names the system, its hosting jurisdiction, and its register record: 'powered by [Model X], hosted in [Jurisdiction Y], registered under [record Z]'.

Can I get an extension on my rates payment?
Yes. Payment plans of up to six months are available. I can set one up now, and a person reviews it before it takes effect.

The chip appears wherever the system operates, not on a separate transparency page.
9.5
Interaction design

Cross-border data transfer as a design obligation

An agent-queryable status flag resolves the standard-clauses, adequacy, or negative-list legal basis into a plain 'valid transfer basis exists' assurance at the submit step.

User sees assurance
High sensitivity · specialist referral abroad

Your referral goes to a clinic in Ireland under a legally binding data agreement, checked 15 Jul, 09:41 and current until 2028.

Routine · library card renewal

Nothing is shown. The same check ran and passed.

System checks gate
Pre-transfer check · every outbound commit
check_transfer_basis(
  destination: "EU (processor, Dublin)",
  data_class:  "health-adjacent"
)
→ {
  basis:   "standard contractual clauses",
  status:  "valid",
  renewed: "2026-02-11",
  expires: "2028-02-11"
}
Valid transfer basis exists. The commit proceeds.
On status: "invalid" the transfer does not happen: the data stays where it is, and the task moves to an onshore path automatically, before anything is sent.
9.6
Service design

Sector-specific data residency

A sector residency rule, such as My Health Records Act s77 or APRA CPS 234, becomes a pre-routing constraint plus a plain-language assurance, for example 'processed within Australia in accordance with the My Health Records Act'.

User sees assurance
Preview a different kind of data the task touches

Processed within Australia, in accordance with the My Health Records Act.

One plain sentence tells the user where the task happened. They don’t need to know the statute to know the protection applied.

System routes request
Routing constraintEvaluated before any request is placed
Sector ruleMy Health Records Act 2012 (Cth) s 77 — records must not be held or processed outside Australia
Routing constraintonshore_only
On no compliant routeThe task does not run. It queues for an onshore window or a human path.

The system follows the law as a hard rule. The assurance line is generated from this logic.
9.7
Interaction design

Sovereign AI model selection and disclosure

A food-origin-style provenance label names the provider, training jurisdiction, hosting jurisdiction, and governing law, shown at the point of AI interaction.

Preview two systems in the same service
AI provenance
Kestrel-2 · benefits assessments
ProviderNational AI facility (public)
Trained inAustralia, on curated government corpora
Hosted inAustralia · government-assured data centers
Governing lawAustralian law only
Fully domestic: one legal system answers for every layer.

A contested decision eventually asks four things: which system decided, who built it, where it ran, and under whose law. The label answers them at the moment of use, not later in discovery.
9.8
Policy design

Concentration-risk and supply-chain disclosure

A per-layer sovereignty BOM card shows each component's jurisdictional exposure, drawn from the same supply-chain mapping behind an SBOM and concentration-risk oversight.

Benefits-inquiry assistant · sovereignty bill of materials
Authenticated oversight view
Every layer that touches user data, with the jurisdiction that can reach it
ModelMeridian AIUS provider · onshore deploymentUSForeign exposure
Inference hostingCoretide Cloud (AU region)US parent · Sydney regionUSForeign exposure
Data storageGovernment data centersAustraliaAUDomestic
OrchestrationCoretide Cloud servicesUS parent · managed serviceUSForeign exposure
Operational supportFollow-the-sun vendor supportUS and IndiaUS·INForeign exposure
Concentration flag: 4 of 5 layers carry foreign exposure, 3 of them through one provider group

Model, hosting, and orchestration all trace back to Coretide or its parent. One legal or commercial event abroad would affect all three layers at once. Recorded mitigations: a portable model contract, and an onshore fallback for orchestration now under test.

Built from the same supply-chain mapping a software bill of materials starts from, and extended from components to jurisdictions. A querying agent receives the summary counts; the per-vendor map is released only to authenticated oversight bodies.

An unmapped dependency cannot be debated, priced, or replaced. The manifest lists every layer, so each one can be.
9.9
Interaction design

Context-triggered disclosure

A pre-processing checkpoint discloses in proportion to data sensitivity, escalating to the user only when the data classification and the infrastructure tier diverge.

Preview a matched or mismatched classification
Renew your parking permit

Your details are complete. Renew for 12 months.

Data protection matched to this task

The checkpoint ran. Routine data on standard infrastructure is a match, so it resolves to a single line, without interruption.

Every escalation is also logged for the service team. A mismatch that reaches one user is a routing gap to fix for everyone.