Legal Entities Disclosure

Every operator legal entity behind a Sovern marketing surface, auto-projected from the canonical registry. The substrate admits the six-entity structure as a closed first-class registry; actual incorporations are owned by the stewardship operator + counsel.

Generated from lib/registry/marketing-surface-legal-entities-registry.ts · 6 registered entities

Six surfaces, six operators (§II-4)

Each of the six public marketing surfaces (foundation, digital, technology, services, ventures, cloud) binds to exactly one operator legal entity. The URL-segment policy (entityKey === surface) keeps the host-routing shape coherent — visiting /terms, /privacy, or /dpa on a surface resolves to that surface's operator.

Operators

foundationSovern Foundation

surface: foundation · legal form: TBD · jurisdiction: TBD · registered address: TBD

digitalSovern Digital

surface: digital · legal form: TBD · jurisdiction: TBD · registered address: TBD

technologySovern Technology

surface: technology · legal form: TBD · jurisdiction: TBD · registered address: TBD

servicesSovern Services

surface: services · legal form: TBD · jurisdiction: TBD · registered address: TBD

venturesSovern Ventures

surface: ventures · legal form: TBD · jurisdiction: TBD · registered address: TBD

cloudSovern Cloud

surface: cloud · legal form: TBD · jurisdiction: TBD · registered address: TBD

Substrate role vs operator role

The substrate's responsibility is to admit the six-entity structure as a closed first-class registry — the data shape, the URL-segment policy (entityKey === surface), the footer operator-display rendering, and the registry-iterated trust page. The substrate does not incorporate the entities, draft their substantive Terms / Privacy / DPA copy, or sign on their behalf. Substantive legal content is authored by the stewardship operator + counsel and rendered through the existing /terms, /privacy, /dpa, and /trust/sub-processors route shells.

TBD fields

legalForm, jurisdiction, and registeredAddress are nullable at v1 — operator counsel populates them post-incorporation through a §II amendment. The UI renders "TBD" until the registry row is populated.