Loading Help…
An interactive map of every RPF entity and relationship — hover a box to preview it, click to pin it, and jump straight to that surface in RPF.
Boxes are the real entities (solid borders) and derived views (dashed). Arrows are the relationships as they exist in the schema — unchanged by the July 2026 naming cleanup, which retired most aliases (shown struck-through in the inspector). Hover or tap a box; click through to open that surface in RPF.
Both draw nodes along a path — but they chart different edge types over different time horizons. The AFD is the score for performing the work; the metro map shows how the performers themselves change.
| AFD — draws a Flow | Metro map — draws Transformations | |
|---|---|---|
| Nodes are | Activities — tasks and decisions | Roles — stations on a line |
| Edges mean | “then” — control flow within one process | “becomes” — succession across the market |
| Time horizon | Hours → months (trigger to outcome) | Years → decades (legacy → future-ready) |
| Grain | One flow, one scenario, a small cast | A whole discipline × jurisdiction |
| Data | Its own tables — nodes, edges, information uses, statement bindings, L1–L4 granularity | A derived view over roles (succession links + archetypes) — no tables of its own |
| Mode | Editable, forkable, versioned working document | Curated, read-only panorama |
| Only it can show | Branching & conditions, step-level responsibility handoffs, the information payload of each step, panel-verifiable edges | A role becoming another role, interchanges (a role shared by two disciplines), market whitespace (a legacy role with no future-ready terminus), jurisdiction comparison |
They meet at the Role: a metro station is the entity whose flows the AFDs describe — giving a natural zoom stack: metro (market) → role (identity) → lineage (composition) → flow + AFD (operation).
A metro edge is an argument: click “becomes” to open the diff and see exactly what changes — the items and the process — when one role becomes the next.
