Skip to main content
Platinur uses Evidence for governed dashboards. The Dashboards page is environment-aware: Staging shows staged pages and Production shows the released project.

​
Dashboard cards

Cards are intentionally content-first—there is no preview-image or image section. Each card shows the dashboard name, short description, creation date, and compact actions:
  • open the rendered dashboard;
  • edit its name/description;
  • inspect its Evidence Markdown source;
  • share it;
  • Enhance with AI, which opens a new Staging chat with that dashboard file attached.
Editing the display name or description uses the same side-panel pattern as Share/Schedule. It updates dashboard metadata directly and rebuilds the preview; it is not a generated-code proposal and does not go through Promotions. Literal Evidence bindings such as {inputs.player.value} or data={players} are rejected as metadata so template syntax cannot become a public title or description.

​
Groups and organization

Press Organize to open the dashboard organizer side panel. Create, rename, or remove named groups, then assign each dashboard to a group. The page renders groups as collapsible sections, using the same interaction as Monitoring’s date-grouped run history. Ungrouped dashboards remain available outside named sections. Organization is environment-scoped portal metadata. It changes how cards are arranged without editing Evidence files or creating a Staging proposal.

​
How dashboards are served

Evidence is internal-only. It has no public browser port. Signed-in dashboard routes resolve through Platinur’s authenticated /env/{environment}/... proxy, which checks portal permission before streaming the page and its assets from Evidence. Opening a normal dashboard URL without a portal session returns 401. The page title opens Evidence’s environment landing page. Evidence already provides its native page navigation, so Platinur does not create a second “Dashboards” link list. The Assistant is blocked from editing evidence/pages/index.md; it writes or changes only the requested evidence/pages/<slug>.md page.

​
How the Assistant creates dashboards

The Assistant grounds a dashboard in exact relations that exist in the active governed catalog. It inspects real model contracts and sample shapes before writing query SQL. If the requested filter or grain is not supported by a current serving relation, it may add and validate the missing model in the same Staging change rather than referencing a table that does not exist. Assistant-authored pages must include useful, query-backed content—not a placeholder chart added only to satisfy a compiler. Dashboard validation checks, among other things:
  • named SQL queries resolve to exact governed relations;
  • query columns match the referenced model contract;
  • scalar cards remain valid for zero-row results or use a guaranteed single-row aggregate;
  • requested filters are wired into relevant queries/components;
  • display titles/descriptions do not contain template bindings or component props;
  • the page has meaningful query-backed charts/tables for the request;
  • Evidence can build the current page against the current Staging catalog.
The Assistant asks targeted questions when audience, subject, or decision is too ambiguous to produce a useful page. A successful page is committed to Staging and reviewed in Promotions.

​
Delete a dashboard

Deletion begins only in Staging because a Production dashboard is released code. Open the dashboard’s Edit panel and press Delete. Before confirmation, Platinur shows the dashboard’s group assignment and enabled deliveries. Confirming creates a staged deletion proposal. Applying it:
  • removes the dashboard page from Staging;
  • removes its Staging group assignment;
  • pauses enabled subscriptions that point to it;
  • revokes existing share links for that dashboard.
If the dashboard already exists in Production, it remains live there until the deletion card is included in a release plan. The proposal’s Undo action restores the page, its former group, and only the subscriptions paused by that proposal. Revoked share links stay revoked; mint new ones after Undo. Share links authorize one dashboard in one environment for a fixed lifetime. /share/{token} is the only unauthenticated dashboard route. Recurring subscriptions send a fresh link by email or Slack rather than a rendered image. See Share & schedule.

​
Builds and previews

Staging previews update after a dashboard proposal commits and its Evidence build passes. Production previews update after a release is merged and the Production refresh completes. Build dashboards (or Rebuild dashboards) requests a build for the active environment. Concurrent requests attach to the build already in flight because one Evidence project build covers every page. Heavy compilation runs through Platinur’s shared host build broker: builds are FIFO across accounts and reuse cached, immutable compiler artifacts instead of starting a full compiler per tenant. Account Evidence containers remain the preview servers. Failed source preparation, compilation, or page data appears as a dashboard run in Monitoring with a sanitized, actionable summary.