# Screenshots tour: dated examples, safer next questions

> Checked · 20 October 2026 · Wiki version 2026.10.20.2

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.

## Purpose
Help a reader recognise key surfaces and ask the right next question without copying private records or over-interpreting a dated screen.

## Diagram text alternative
Operations overview points to readiness and evidence questions. Planning navigation points to record and permission questions. Data health points to freshness and identity questions. Reports and admin views point to review and careful action boundaries.

## Current / proposed status
- Current: Checked — only the approved sanitized JPG captures are included; all are described as dated examples.
- Proposed: Replace or add screenshots only through an approved sanitisation and documentation review, with current-date captions.

## Safe example
### Read a screen without overclaiming
If an operations card says a cleaning task is completed, ask whether evidence and verifier acceptance are also present. If data health says a source is recent, ask whether the relevant source window was read completely and published successfully.

## Responsibilities
- Readers treat screenshots as visual orientation only.
- Documentation maintainers retain captions, dates, alt text, and sanitisation boundaries.
- Operators open approved live records for current facts.
- Contributors run browser and mobile checks if screenshot layout changes.

## Checklist
- Read the screenshot date and caption before using it as an example.
- Never infer a live value, access right, or accepted decision from a screenshot.
- Use local approved JPGs only; do not embed external media or private captures.
- Check alt text and responsive display on desktop and mobile.

<a id="operations-overview"></a>

## Operations overview: locate today’s work, then inspect support

**Status:** Checked

The operations overview screenshot shows a shared daily picture: arrivals, departures, turnovers, and exceptions. Use it to orient the operating day, then follow the relevant record and responsible person.
A cleaning job marked complete is not automatically a verified property-ready decision. Read the observation time and evidence label before treating a visual status as current or accepted.

**Current / proposed status**
- Current: Checked — this is a dated installed-app example captured on 20 October 2026, not a statement of current values.
- Proposed: Keep a caption and source boundary if the image is ever replaced with a newly approved sanitized capture.

**Expected outcome**
The screen helps a reader find a task without erasing the evidence and verifier questions.

**Meaningful tests**
- Check local image path, descriptive alt text, and dated caption.
- Check the turnover page remains the focused link for evidence and readiness details.

<a id="planning-navigation"></a>

## Planning navigation: recognise modules without exposing private values

**Status:** Checked

The planning navigation crop points to finance, owners, goals, revenue and pricing, and roadmap records. It intentionally omits individual financial values and private records.
Computed values should not be edited as if they were ordinary fields. Confirm the source, permission, and review boundary before proposing a change to inputs or using a displayed number in a decision.

**Current / proposed status**
- Current: Checked — the capture is intentionally limited to navigation and has no private financial detail.
- Proposed: Maintain the no-private-values boundary for future visual documentation.

**Expected outcome**
Readers can recognise where planning work lives without mistaking a screenshot for access or authorisation.

**Meaningful tests**
- Check the planning image contains no textual claim of live financial data.
- Check responsive CSS keeps the narrow navigation crop legible.

<a id="data-health"></a>

## Data health, reports, and admin: inspect confidence before acting

**Status:** In progress

The data-health screenshot helps illustrate why source labels and identity confidence matter. It is a dated example, so it cannot prove current freshness or reconciliation. Use it to ask whether the relevant source window was read completely and published successfully.
Report and admin screens can contain high-consequence actions or internal information. Treat them as carefully scoped surfaces: current approval, record context, and a reviewed change path matter more than a familiar layout.

**Current / proposed status**
- Current: In progress — provider freshness and all live acceptance labels require current evidence, not a screenshot.
- Proposed: Add a newly sanitized dated capture only when it improves a specific safe question and preserves access boundaries.

**Expected outcome**
A reader uses visual cues to investigate confidence rather than making a completion claim.

**Meaningful tests**
- Check no screenshot caption claims live health, freshness, or completed acceptance.
- Check search and visual controls remain keyboard-operable with images present.

<a id="screen-care"></a>

## Screens are an invitation to ask the next question

**Status:** Checked

A screen can show what to investigate. It cannot make a provider source fresh, make an identity confirmed, or make a verifier accept a result. Use labels, dates, and record links as signals to follow the process described elsewhere in the wiki.
The only copied images in this site are the approved sanitized JPGs in this tour. No internal evidence, QA artifacts, databases, credentials, or private logs are included.

**Current / proposed status**
- Current: Checked — the visual documentation boundary is explicit and uses only approved local assets.
- Proposed: Keep screenshots visual and explanatory; keep sensitive operational material in its authorised system.

**Expected outcome**
The tour stays shareable inside the intended audience without becoming an evidence or credential archive.

**Meaningful tests**
- Check the public asset tree contains only the five approved JPG screenshots for this tour.
- Check generated exports have no runtime-log or private-evidence references.

## Related pages
- [Dashboard and passive TV: shared views, not source authority](/systems/dashboard-and-tv/) — 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.
- [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.

## Source pointers
- Handoff / pages/app-tour.html
- Handoff / START-HERE.html

## Context export
- Page context: ./exports/reference--screenshots-tour.context.json