Role Paths

This page gives tech leads, architects, platform teams, and contributors a shared but role-specific way into the same system.

Why role paths help

Different readers care about different questions, but they should still move through one coherent narrative instead of treating the site as unrelated sections.

Role-based entry points

Role	Start here	Then read	Then use
Tech lead	Decision Brief	Project Overview	Adoption Path
Architect	Site Blueprint	Information Graph	Rules Evidence Library
Platform / DevEx	Site Blueprint	Adoption Path	Rules Evidence Library
Contributor	Project Overview	Information Graph	Rules Evidence Library

First actions

1. Tech leads: use the homepage and brief as a 15-minute alignment memo.
2. Architects: map rules/, docs, and publishing into a clear system boundary.
3. Platform teams: translate the adoption path into a pilot and governance loop.
4. Contributors: add new evidence without collapsing the shell back into a raw catalog.

Shared ownership

The strongest rollout is one where tech leads back the value case, architects define structure, platform teams maintain the loop, and contributors keep the evidence current.

Return to the adoption path