Composition Patterns

This page helps you decide which rule combination to validate before browsing category pages.

Return to the executive context

• Project Mission
• System Overview
• Academy Path

Base pattern

• General + primary stack
• Start with General and the page for your main stack.

Expansion pattern

• Primary stack + security / data / platform
• Add Security, Data, or Platform when delivery risk grows.

Upgrade signals

• Repeated instructions should become project-specific rules.
• Repeated review boundaries are a signal to formalize a team baseline.
• Governance belongs in the academy and guide layers, while rule pages remain the evidence layer.