Decision Brief

This page is the shortest path for tech leads evaluating whether the rule library should be treated as an organizational engineering asset.

Why it matters

A large rule catalog is not the investment case. The investment case is a reviewed, reusable, and expandable knowledge system.

• Organizational asset: shared rules capture naming, testing, structure, and review expectations.
• Lower coordination cost: teams stop re-explaining the same constraints in every session.
• Compounding reuse: strong rule patterns can move from one repository to the next.

How the system is organized

1. rules/ remains the source asset library.
2. Whitepaper, architecture, and playbook pages explain value, structure, and action.
3. The rules area becomes an evidence library instead of the homepage default.
4. Resources connect the internal narrative to upstream docs and related references.

Where to start

Role	First stop	Second stop	Third stop
Tech lead	Decision Brief	Project Overview	Adoption Path
Architect	Site Blueprint	Information Graph	Role Paths
Platform / DevEx	Site Blueprint	Adoption Path	Rules Evidence Library

Next step

If the organizational case is valid, continue into the overview and architecture pages before choosing rule combinations.

Continue to the overview