Reusable System Above the Visual Layer

The central design-system concept recovered from multiple discussions is:

A scalable Power BI system is not merely a Figma library of chart drawings. It defines:

• Approved native components and explicitly approved exceptions.
• Approved configurations for tables, matrices, cards, slicers, navigation and common charts.
• Variants for density, comparison type, hierarchy and state.
• Page archetypes and templates.
• Reusable section/composition patterns.
• Interaction semantics: filter vs highlight vs none; drill; drillthrough; tooltip; reset; view switching.
• Navigation architecture and back behavior.
• Formatting standards and semantic tokens.
• Accessibility requirements.
• Developer mapping and implementation notes.
• Data/measure expectations and formatting conventions.
• Definition of Ready and exception governance.

The system should therefore be read from the top down:

Foundations
  ↓
Component configurations
  ↓
Section patterns
  ↓
Page archetypes / templates
  ↓
Report architecture / flows
  ↓
PBIP starter + implementation standards