Make the places you serve explicit
Where the operator is established and where the product serves people shape the questions its documents must address. Wildo records that reach explicitly rather than guessing it from a currency, language or address.
The declaration can be compared with the reach of registered sources. This supports focused research and review without confusing source coverage with compliance.
Example — Expand into another market deliberately
An application adds a country to its operating declaration and records why it serves that market. Its document workflow can then evaluate that reach, instead of silently reusing the assumptions of the previous market.
For engineers
Record the reason beside each jurisdiction
This is the operating declaration from Wonder CRM. It illustrates the configuration shape, not a recommendation about any application’s legal position.
operatingJurisdictions: {
jurisdictions: [
{
jurisdictionSlug: 'eu',
basis: 'the operator is established in France and subscribing teams and their members are in the EU',
},
{
jurisdictionSlug: 'gb',
basis: 'teams established in the United Kingdom subscribe and store their customer records here',
},
],
},
The schema requires a nonempty jurisdiction list and a reason per place, and rejects duplicates. Canonical region spelling matters: aliases should not create two identities for one place. A subdivision means a place inside its root; broader regimes are represented by their component places.
Read coverage as source reach
assessAssuranceJurisdictionCoverage compares the declared places with active registered sources. composeOperatingJurisdictionCoverageBrief carries that result into drafting context. It distinguishes law-backed coverage, guidance-only coverage and uncovered reach. Those states say what source material the framework carries; none establishes that the application meets the source’s requirements.
Keep publication and operating scope connected
Operating reach answers where the product acts. A public-document variant answers which exact language and jurisdiction combination a document is prepared for. Use the same canonical jurisdiction vocabulary in both. A reviewer still determines the requirements and statements appropriate to the operator’s actual activities.