How transformation metro maps work
RPF's most public-facing surface. Maps legacy roles into future-ready ones along jurisdiction-aware transformation routes. Curated by professional bodies; cited against canonical standards; embeddable everywhere.
The transformation metro map is the visual manifestation of the RPF transformation narrative: define what it takes to transform legacy roles — Architect, Engineer, Facility Manager — into future-ready roles.
Three audiences at once: professional bodies sponsor the canonical chain; org leaders compare against their org's profile; practitioners pick a pathway and run Transform-My-Role.
What a transformation metro map is
A metro map is a graph projection over RPF's Role + Profile + Information Use primitives. Each station is a Role; each line is a transformation route. Lines start at legacy roles (origins), pass through hybrid (transitional) roles, and end at future-ready roles (terminuses).
The map is a query, not a stored entity. Each request assembles fresh from the canonical RPF graph; the content-hash version pins the URL to a specific snapshot for permalink stability.
Three audiences at once
The body audience leads in this doc because they sponsor what others use — but the surface itself serves all three audiences with equal weight.
Sponsor the canonical future-ready chain in your jurisdiction. Your members see your sponsorship on every map view. Your accreditation pathways earn citation-grade visibility on the most public RPF surface.
Compare your org's profile against the canonical future-ready endpoint. Gap-analysis deltas, missing IUs, and material substitutions surface inline — without exposing your org's data publicly.
Pick a station near where you are today; Transform-My-Role takes you the rest of the way. The plan you get is personal, jurisdiction-aware, and citation-anchored.
Your journey through a map
- 1Pick a discipline (Architect, BIM Manager, Facility Manager) and a jurisdiction (BRA, IRL, CAN). The URL carries both.
- 2Read the map left-to-right: legacy roles on the left, future-ready ones on the right. Stops along each line are stop-gates — competency thresholds you must meet to progress.
- 3Click the agent panel chips for citation-backed explanations. The agent never invents IDs — it cites only station / line / IU / source IDs that are on this map.
- 4Choose your next step: Transform-My-Role (practitioner), Gap analysis (org leader), or Sponsor this jurisdiction (body).
Coverage today (9 maps)
Initial coverage targets Architect, BIM Manager, and Facility Manager × jurisdictions BRA (Brazil), IRL (Ireland), CAN (Canada). The curation metadata (line colours, layout hints) is code-canonical; the underlying canonical content (Roles + Profiles + Items) is authored in production via the app UI. Combos without canonical content yet display the sponsorship empty-state CTA.
Embedding the map
Every map exposes an embed URL pinned to the current content-hash version. Use the Copy embed code button on the showcase route to lift an iframe snippet. The embed is print-clean (no Cmd-P chrome bleed) and locale-aware via the URL prefix.
Known limitations
- Panel-validation badges + recognition badges light up only when M19.5 / M19.7 land. Until then the map ships without them — coverage indicators in the meta strip show '0%'.
- Permalink versioning resolves only `latest` today. Explicit `?v=<hash>` URLs against an older hash surface a 'version-shifted' callout and serve latest content. The full snapshot store is a Phase-19 follow-up.
- The agent panel is curated — pre-baked questions with cited answers. Free-form chat lands when the generic agent surface does (Phase 19 metro-map slice).
