Report
What It Models
A report adds a presentation to saved questions. A dashboard combines multiple questions while retaining the sources needed for access checks and change indicators.
Identity and Attributes
Ownership, audience and source versions belong to the stored report. Built-in components remain console code until someone saves a coded copy.
Relationships
Source references protect saved queries from deletion and provide the boundary for sharing. Export files and schedules retain their own execution histories.
Invariants
The invariant rows define audience checks, source replacement and version-aware writes. Catalog visibility alone does not guarantee an executable joined query.
How It Is Stored and Shared
The query service stores report definitions and source rows; console components interpret the layout. Rendering is a separate background workflow.
Open Design Questions
Report approval and runtime coverage remain limited by the recorded reporting and catalog findings.