Role archetypes across jurisdictions
The role_archetype enum is jurisdiction-agnostic — every jurisdiction supports legacy / future-ready / hybrid as the same three categories. The substantive jurisdiction angle is which disciplines have a canonical future-ready role published today, and the sponsorship pointer for jurisdictions still queued behind a body.
The canonical-per-jurisdiction rule
RPF does not maintain a single global canonical future-ready role per discipline. Each supported jurisdiction publishes its own, sponsored by a body active in that market. The role-diff surface always lines up an org-forked role against the canonical future-ready in the org's jurisdiction. If the org's jurisdiction has no canonical future-ready role for that discipline yet, the catalogue shows the sponsorship CTA in the browse-filter empty state — not a fallback to a global canonical.
Why per-jurisdiction?
Future-ready competence is shaped by local standards, local procurement language, local regulatory drivers, and local sponsoring bodies. A canonical that averaged across all jurisdictions would lose the citation-grounded credibility that is RPF's defensibility.
Brazil (BR)
The BFB collaboration is the sponsoring activity for the Brazilian canonical future-ready roles. Architect, BIM Manager, and Facility Manager future-ready roles are queued for publication, with Portuguese (pt-BR) variants required on every item. Items cite ABNT NBR ISO 19650 in place of ISO 19650 where applicable.
Ireland (IE)
The Irish canonical future-ready roles are queued behind a sponsoring body — today the catalogue offers the sponsorship CTA on every Architect / BIM Manager filter-by-future-ready empty state in Ireland. Items will cite IS EN ISO 19650 in place of ISO 19650 where applicable.
Canada (CA)
The Canadian canonical future-ready roles are queued behind a sponsoring body. Both English (en) and French (fr) variants are required on every published item. Items may substitute CSA Z250 for ISO 19650 in some contexts.
Other jurisdictions
Jurisdictions without a canonical future-ready role for a discipline see the sponsorship CTA on every browse-filter empty state. Sponsorship is the path: a body funds the canonical's development, attribution is permanent on the published role, and the first org-fork lights up the role-diff surface for that jurisdiction.
