01must proveConfirmed | Dashboards are reports without a single direct saved-query source, reject that direct source field, and differ from other report kinds that require it. | validation | service, database | test |
02must proveConfirmed | Dashboard saves record up to fifty distinct widget sources in first-widget order and reject larger source sets without writing. | calculation | service | test |
03must proveConfirmed | Every widget source must be visible to the author, and an inaccessible source produces a refusal locating its widget. | validation | service | test |
04must proveConfirmed | Dashboard audiences cannot exceed any source audience, with the first narrower source in widget order identified. | policy | service | test |
05must proveConfirmed | A query used by a dashboard source cannot be deleted while that dependency remains. | policy | service, database | test |
06must proveConfirmed | Dashboard change warnings reflect source-definition changes rather than source renames alone. | calculation | service | test |
07must proveConfirmed | For a source the reader cannot see, dashboard source metadata returns only identity and change state, withholding its name. | policy | service | test |
08must proveConfirmed | A dashboard with sources passes catalog filtering when at least one visible source has an accessible base dataset; a dashboard without sources also passes. | policy | service | observed |
09must proveConfirmed | Widgets run their own saved queries as the viewer, apply narrowing dashboard filters and fail independently when a source is unavailable. | policy | service, console | documented |
10must proveConfirmed | Platform preserves dashboard layout content exactly and interprets only widget source-query identities. | invariant | service | test |