Dashboard Is Not Decision

A dashboard — KPI tiles, trend charts, health scores, and red, amber, and green status — can surface plant or maintenance state. Seeing a dashboard is not a Decision Case and not a decision. Sync may show coverage, recommendations, and status. A named human still opens a Decision Case on a question, cites approved evidence, and accepts, rejects, escalates, or returns. A green dashboard, an improved trend, or a cleared alert tile must not be read as authorization, verification of outcome, work-order execution, or plant control.

Reliability work collapses the display because a settled color looks like a settled case. The health score moves. The trend line changes direction. An alert tile clears. The meeting treats the screen as if a question had been decided, work had been authorized, an outcome had been checked, or the plant were under direction. It was not. The screen showed state. No named person had opened a Decision Case on a question, cited approved evidence, and accepted, rejected, escalated, or returned a recommendation.

Sync keeps that split on the signed-in Decision Case. A signed-in user completes the case in a fixed order: Question, Evidence, Recommendation, Human decision, Action, Verification, and Learning. Orville Davis states that order in Field Manual v0. The manuals index lives at /manuals. This essay is why a dashboard cannot be read as the human decision or as verification. The manual is the public contents. The Human decision chapter and the Verification chapter are the two steps this essay keeps apart from the display.

A dashboard surfaces state

A dashboard is a display of plant or maintenance state. A KPI tile shows a number. A trend chart shows how that number moved. A health score summarizes readings into one figure. Red, amber, and green status assigns a color to a condition. Those objects can make a condition visible to a person in the room. They do not open a case, and they do not name who may decide it.

Coverage Is Not Control already places a dashboard with the watched set: sensors, CMMS rows, patrol routes, and the tiles on a screen. Coverage is what is watched. Control authority is permission to order work, isolate equipment, or change the plant. This essay is the next boundary. A display of state is not the Decision Case that would decide what to do about that state.

A watched number is not a question on a case. A green tile is not a named decision.

The number can be current. The color can match a rule someone wrote. The chart can be readable. None of that records a reliability or maintenance question, the evidence cited for it, or a human act on a recommendation.

Seeing a dashboard is not a Decision Case

A Decision Case opens on a reliability or maintenance question a named person can decide. The question is recorded before evidence or recommendation. Question Is Not Decision states that opening. A dashboard does not write the question. A person does, on the signed-in case.

Seeing the dashboard is not that opening. The screen can be up while no case exists. The screen can change while an existing case stays where it was. The display and the case are different records. One shows state. The other holds a question a named person can decide.

Seeing a dashboard is not a Decision Case and not a decision.

Sync may show coverage, recommendations, and status. Showing them puts a view where a person can read it. The view can include what is watched, a proposed next action, and a status beside that proposal. The view is still not the case. A named human still opens a Decision Case on a question. Until that opening is recorded, Sync has shown a display. It has not started the loop.

The decision is a named human act

The human decision comes after a recommendation exists to decide. A recommendation states a proposed next action, the evidence it uses, and the uncertainty it leaves in view. Drafting that proposal leaves authority where it already sits. Recommend Is Not Authorize states that split. A status shown next to the draft does not close it.

A named human still opens the case on a question, cites approved evidence, and accepts, rejects, escalates, or returns. Citing approved evidence means the decision points at the record already on the case: observed fact, assumption, and what is still missing. A health score is not that citation. A trend chart is not that citation. The Human decision chapter publishes the act. The case keeps the person beside the proposal they decided. The person who can accept the operational consequence is still the one who decides.

Until that act is on the case, the display can change and the decision is still absent. A tile that turns green does not accept a recommendation. A tile that turns red does not reject one. Amber does not escalate. A cleared alert does not return the proposal to the person who drafted it. Those are colors and states. The four acts are a named person on the case.

A green tile is not verification

Verification is the check after a named human has authorized an action. It asks whether that action produced the result the decision named, and it names the evidence on the case that would show it. The signed-in case holds that check next to the question, the proposal, and the person who decided. The Verification chapter publishes that step. Verification Is Not Optional states the gate: the case is not closed until the check is recorded.

A green dashboard, an improved trend, or a cleared alert tile must not be read as verification of outcome.

A tile can turn green because a sensor recovered, a threshold moved, a calculation refreshed, or someone cleared the display. A trend can improve for the same kinds of reasons. None of those events records who authorized an action, or whether the authorized action did what it was supposed to do. A dashboard that was never tied to an authorized action has nothing authorized to check. Citing the color as if the outcome were known treats a display as a closed case.

Stage-1 verification is the check written on the case. This edition does not treat a live pull of historian or control-system tags as that check. A dashboard fed by those tags, or by simulated or seeded practice records, is still a display. It is not the verification step. Learning that follows verification inherits the closed case. It does not inherit a tile that changed color.

A cleared display is not authorization, execution, or control

A green dashboard, an improved trend, or a cleared alert tile must not be read as authorization, work-order execution, or plant control.

Authorization is the named human decision on a recommendation. The dashboard sits outside that act. Color does not grant permission to do the work. An improved trend does not either. The recommendation can still be rejected, escalated, or returned after the screen looks calm.

The same display does not execute the work. Action Is Not Execution states the later boundary. An ACTION disposition records work intent after a human decision. It does not write a work order, isolate equipment, or change the plant. ACTION stays locked until authorized execution systems write the work order or isolate the equipment. A cleared alert tile does not unlock it. A dashboard is not a work order.

It also does not control the plant. Sync may show coverage, recommendations, and status. A named human decides. Authorized execution systems write the work order or the isolation. None of that follows from a status color. A Decision Case that stores a reading from a dashboard stores a record of state. That storage is not permission for Sync to order work, isolate equipment, or change the plant.

Where the public statement lives

Field Manual v0 is the public contents of this loop. Start at the manuals index or open Sync Field Manual directly. Human decision is step 04. Verification is step 06. A dashboard is neither step. The display can sit beside the case. It does not replace the named act, and it does not replace the check. Later editions can deepen a chapter. The spine stays in this order.

What this article is not claiming

This is an essay about the Decision Case order, not a customer case study. It names no plant, states no savings figure, and claims no prevented failure. It states no OEM limit and no operating threshold. It does not claim that a dashboard authorizes work, verifies an outcome, executes a work order, or controls a plant.

Stage-1 readiness means a signed-in user can complete the Decision Case — question, evidence, recommendation, human decision, action, verification, and learning — and Field Manual v0 describes that journey. This edition does not describe plant execute, a live connector tag pull, SMTP invite delivery, or automatic revocation of access on expiry as live. It does not describe Sync writing work orders, isolating equipment, or controlling the plant. Simulated or seeded telemetry and assets are practice records. They are not live plant results. Self-guided onboarding is not claimed as a live product path.

The series continues with Alert Is Not Decision, on why seeing, acknowledging, or silencing an alert is not a Decision Case and not a decision. Companion reading: Question Is Not Decision on why recording a reliability or maintenance question is not the human decision, Coverage Is Not Control on why a dashboard in the watched set is not control authority, Recommend Is Not Authorize on why a drafted proposal is not permission, and Verification Is Not Optional on why the case stays open until the check is recorded. A Reliability Assessment asks whether the records can support a conclusion. A Strategic Pilot is a governed proof around one operating decision. The Human decision chapter is the named act. The Verification chapter is the check. A dashboard is neither.