Co.PropertyTeam wikiCo.Property20 October 2026
Press slash to search. Arrow keys select a result.
Internal knowledge
Browse the wiki

Systems

Dashboard & passive TV

Checked

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.

Download page Markdown
Interactive mapSelect a node to read its explanation. Use Work on this beside the section to prepare a change.
Dashboard and passive TV: shared views, not source authority diagramProvider 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.Source records — Provider → data → replica: one writer, protected projectionsSource recordsMain mini — The Mac mini: authoritative writer and local operating coreMain miniProtected projection — Provider → data → replica: one writer, protected projectionsProtected projectionStaff dashboard — Dashboard and passive TV: shared views, not source authorityStaff dashboardPassive TV — Dashboard and passive TV: shared views, not source authorityPassive TV
Source observations become protected projections for staff and passive TV.Solid · information flow
Read the diagram as text

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.

  • Source records → Provider → data → replica: one writer, protected projections
  • Main mini → The Mac mini: authoritative writer and local operating core
  • Protected projection → Provider → data → replica: one writer, protected projections
  • Staff dashboard → Dashboard and passive TV: shared views, not source authority
  • Passive TV → Dashboard and passive TV: shared views, not source authority
What it does

Help a reader use operational screens responsibly by distinguishing a helpful display from the source record, freshness evidence, and accepted decision behind it.

Responsibility

The dashboard helps staff orient to operational priorities.

Next step

Read the observation time and evidence label before using a screen value.

The staff dashboard is the usual entry point

Checked

Staff who need company information should ask for approved dashboard access first.

Read the details

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
Checked — the role of the staff view is documented; live availability and values require approved access and current verification.
Proposed next state
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.
Checks to include when changing this section
  • 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

Checked

A passive TV view can help a shared space notice the operating day without turning the screen into a control room.

Read the details

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
Checked — passive TV is described as a consuming view in the documented system shape.
Proposed next state
Keep display-only behavior explicit and test readability at the intended viewing distance.
Expected outcome
Shared awareness improves without blurring write or approval authority.
Checks to include when changing this section
  • 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

In progress

The handoff defines freshness as a complete read of the relevant source window followed by a successful publication.

Read the details

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
In progress — current provider freshness must be verified live; the wiki does not claim it is current.
Proposed next state
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.
Checks to include when changing this section
  • Use freshness fixtures for complete, stale, and failed source publications.
  • Use a completed-cleaning fixture with missing verification and assert it is not ready.

Apply with care

A concrete safe example

Example, responsibilities & checklist

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

  1. Read the observation time and evidence label before using a screen value.
  2. Use screens to locate the relevant record, not to overwrite it.
  3. Keep passive TV views projection-only; do not add write controls by assumption.
  4. Test visible status treatment on narrow screens and keyboard navigation when changing UI.
Expected outcome

A teammate can use the display to find the right record without treating a repaint as proof of current or accepted data.

Traceability without sensitive material

Source pointers and exports

This page expands the approved handoff into plain-language guidance. It does not include runtime logs, credentials, databases, private evidence, internal QA artifacts, or developer planning history.

Documentation references
  • Handoff / pages/infrastructure.html
  • Handoff / pages/app-tour.html
  • Handoff / START-HERE.html
Page MarkdownPage context JSON