Every client's spec, generated from mr-content
Nothing here is maintained by hand. Each page is rendered from the repo at a known commit, so there is no second copy to keep in step and nothing to forget to update.
Where to start
| Spec | Browse by region, client and pathway. Shows what each pathway actually contains, which items are inherited and from where, and warns you before you edit a machine-generated file. Export any pathway as CSV. |
| Repo health | Pathways that cannot be resolved at all, traced back to the one file that needs fixing rather than the many that are affected by it. |
| Requests | The front door for change requests: raise, triage, track to live. Needs the API deployed — see the runbook. |
How the numbers are produced
The snapshot does not re-implement how a pathway resolves. It imports mr-content-script and
asks it, the same way the journeysreport command does, so the spec shown here and
the content the pipeline uploads come from the same code and cannot drift apart. Clone chains,
removeActivities before addActivities, recursive
contentFolder imports, {{ clip }} expansion and
fixedContent are all resolved by the repo's own logic, not by a lookalike.