Prepare the right document for each audience
A translated notice and a notice prepared for another market are not interchangeable. Wildo models each publication variant as a language paired with its intended jurisdiction set.
This gives document preparation a clear audience contract. Adding a language or market is an explicit change, rather than permission to assemble every possible combination.
Example — Add a new audience without changing the existing one
An operator prepares one English variant for a defined regional audience. A second market gets its own declared combination, allowing the document and its review to follow that specific audience.
For engineers
Keep locale and jurisdiction together
This is the actual typed publication declaration in Wonder Todos, shown without its surrounding design commentary:
export const applicationDocumentPublicationSpecification = ApplicationDocumentPublicationSpecificationSchema.parse({
schemaVersion: 1,
authorityRef: "document-publication-variant-authority:wonder-todos",
authorityVersion: 2,
variants: [{ locale: "en-GB", jurisdictionRefs: ["jurisdiction:eu", "jurisdiction:is", "jurisdiction:li", "jurisdiction:no"] }],
});
The family is exported by the application’s specification companion exports. The authorityRef and version identify the declaration being reviewed; variants is a set of exact combinations, not two independent lists to cross-multiply.
Validate identity before using it
ApplicationDocumentPublicationSpecificationSchema checks shape, uniqueness and canonical ordering. validateApplicationDocumentPublicationSpecification additionally checks canonical language tags and jurisdiction references through the shared jurisdiction validator. Candidate jurisdiction validation uses that same vocabulary, so aliases and invalid regional shapes cannot acquire a second identity at another boundary.
Keep publication authority explicit
The declaration states intended variants. Content creation, review and publishing are distinct activities; a valid variant does not itself release a notice. The intended delivery contract uses only the declared combinations and the corresponding reviewed content. Preserve that pairing in the application’s publication process, and record audience changes deliberately in version control. The code above is the declaration contract, not a document-serving endpoint.