# Dashboard and passive TV: shared views, not source authority
> Checked · 20 October 2026 · Wiki version 2026.10.20.2
The staff dashboard and passive TV surfaces make a shared operating picture visible. They consume projections; they do not become the authoritative writer for company state.
## Purpose
Help a reader use operational screens responsibly by distinguishing a helpful display from the source record, freshness evidence, and accepted decision behind it.
## Diagram text alternative
Provider and company data are written and prepared by the mini. Cloud distribution provides protected projections to the staff dashboard and passive TV, where viewers use the display to locate evidence rather than write it.
## Current / proposed status
- Current: Checked — the handoff documents dashboard and TV as staff-facing views; current screen values remain dated examples.
- Proposed: Show freshness and evidence labels near high-consequence projections, and verify the source before acting on an exception.
## Safe example
### A responsible screen read
A tile may show a turnover as “in progress” or a source as “fresh”. Before making a decision, open the relevant record through approved access, check the observation window and evidence label, then follow the named exception or verifier path.
## Responsibilities
- The dashboard helps staff orient to operational priorities.
- Passive TV supports awareness without asking every viewer to operate the mini.
- The source record and authorised verifier remain responsible for a decision.
- A technical contributor checks browser and mobile rendering for UI changes.
## Checklist
- Read the observation time and evidence label before using a screen value.
- Use screens to locate the relevant record, not to overwrite it.
- Keep passive TV views projection-only; do not add write controls by assumption.
- Test visible status treatment on narrow screens and keyboard navigation when changing UI.
## The staff dashboard is the usual entry point
**Status:** Checked
Staff who need company information should ask for approved dashboard access first. The dashboard is designed to provide shared views without making every teammate an infrastructure operator or giving them SSH access to the office mini.
Use an operational overview to find today’s arrivals, departures, turnovers, and exceptions. Then follow the appropriate record and responsible person. A visible green or completed label is a clue to inspect the evidence, not permission to skip it.
**Current / proposed status**
- Current: Checked — the role of the staff view is documented; live availability and values require approved access and current verification.
- Proposed: Keep write and approval controls tied to explicit role and record boundaries.
**Expected outcome**
Routine staff work begins on the least-privileged surface that can answer the question.
**Meaningful tests**
- Run browser and mobile checks for any dashboard UI change.
- Verify keyboard users can reach search, navigation, page contents, and contextual work controls.
## Passive TV is for awareness, not unattended authority
**Status:** Checked
A passive TV view can help a shared space notice the operating day without turning the screen into a control room. It should consume a projection and retain the same caution about dated observations, source freshness, and accepted decisions.
Do not infer that a passive display can change company state, contact a provider, or confirm a readiness result. Those actions remain with the authorised record and operating process.
**Current / proposed status**
- Current: Checked — passive TV is described as a consuming view in the documented system shape.
- Proposed: Keep display-only behavior explicit and test readability at the intended viewing distance.
**Expected outcome**
Shared awareness improves without blurring write or approval authority.
**Meaningful tests**
- Check passive-TV content has no assumed write action.
- Check text equivalents remain available for every visual diagram.
## Confidence comes from source freshness and evidence, not screen activity
**Status:** In progress
The handoff defines freshness as a complete read of the relevant source window followed by a successful publication. A dashboard opening, refreshing, or repainting only proves that a screen changed; it does not prove the provider information is current.
For a turnover, a cleaning job marked completed is not automatically a verified property-ready decision. The screen should direct the reader to observation time, evidence label, and responsible review.
**Current / proposed status**
- Current: In progress — current provider freshness must be verified live; the wiki does not claim it is current.
- Proposed: Exercise stale, incomplete, and successful source cases and make their different display states clear.
**Expected outcome**
Users can ask the source and evidence questions before acting on a dashboard status.
**Meaningful tests**
- Use freshness fixtures for complete, stale, and failed source publications.
- Use a completed-cleaning fixture with missing verification and assert it is not ready.
## Related pages
- [Provider → data → replica: one writer, protected projections](/systems/data-replicas/) — Providers remain authoritative for their own transactions. The main mini writes internal company state; Cloudflare protected replicas and the Vercel staff PWA consume projections rather than replacing the master record.
- [Turnover readiness: evidence before a ready decision](/workflows/turnover-evidence/) — A turnover prepares a property between stays. Assignment, cleaning completion, evidence, verification, and readiness are separate states that must refer to the same confirmed property.
- [Screenshots tour: dated examples, safer next questions](/reference/screenshots-tour/) — These sanitized screenshots are a visual orientation to the installed app captured on 20 October 2026. They are not mockups, credentials, or current operational proof.
## Source pointers
- Handoff / pages/infrastructure.html
- Handoff / pages/app-tour.html
- Handoff / START-HERE.html
## Context export
- Page context: ./exports/systems--dashboard-and-tv.context.json