Coverage Is Not Control

Coverage is not control. Sensors, CMMS rows, dashboards, patrol routes, and the claim “we monitor everything” describe what is watched. They are not control authority over work, isolation, or change. Sync may show coverage and recommend. A named human decides. Authorized execution systems write the work order or the isolation. A Decision Case that records a coverage gap or a recommended coverage action must not be read as Sync controlling the plant.

Reliability work collapses the two because a full picture looks like authority. The sensor is online. The CMMS has a row. The dashboard shows the asset. A patrol route reaches the area. Someone says the plant is monitored. Later a gap appears — a missing point, a stale row, a route that stops short — and the recommendation says add coverage. The meeting treats the system that showed the gap as if it now controls the work. It does not. Coverage was a view. Control authority was never transferred.

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 coverage record cannot be read as control of the plant. The manual is the public contents.

Coverage is the watched set

Plant coverage is the set of things the organization can point at. A sensor on the asset. A row in the CMMS. A tile on a dashboard. A patrol route a person walks. “We monitor everything” is a claim about that set. It says the view is broad. It does not name who may order work, who may isolate equipment, or who may change the plant.

A coverage gap is the same kind of record. A point is missing. A row is stale. A route does not reach the asset. The dashboard does not show the condition someone expected to see. Recording the gap names what is not watched. It does not create authority to close it.

A watched asset is not an authorized job. An unwatched asset is not a work order.

On the Decision Case, coverage belongs with evidence: observed fact, assumption, and what is still missing. The Evidence chapter publishes that step. Stage-1 evidence is the record held on the case. A live connector that pulls historian or control-system tags sits outside this edition. Simulated or seeded telemetry and assets are practice records. They are not customer plant coverage, and they are not control authority.

Control authority is permission to act on the plant

Control authority over work, isolation, or change sits with the people and the systems that already hold it. A work order is written in the system the site already uses to authorize maintenance — the customer’s CMMS or EAM, or the equivalent system of record. Isolation is the site’s existing practice for taking equipment out of service, under the people who already hold operating authority. A change to the plant follows the same authority.

A screen that displays sensors does not hold those authorities. A CMMS row does not hold them by existing. A patrol route does not hold them by being drawn. Neither does a Decision Case that stores any of those records.

Sync may show coverage and recommend. A named human decides. Authorized execution systems write the work order or the isolation.

Showing coverage puts the watched set, or the gap in it, where a person can read it. Recommending 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. That split is the subject of Recommend Is Not Authorize.

A named person accepts, rejects, escalates, or returns the proposal. That act is the human decision. It records who decided. It still does not write a work order, isolate equipment, or change the plant. Authority to accept a coverage recommendation is not authority for software to control the plant. Read the two steps as separate chapters: Recommendation and Human decision.

A recorded coverage action is not plant control

If the named person approves work to add a sensor, correct a CMMS row, extend a patrol route, or isolate equipment, the Decision Case may store that intent. The write still belongs to authorized execution systems and to the people who already operate them. Sync does not perform it.

Action Is Not Execution states that boundary for the ACTION disposition. Recording work intent on the case does not write a work order, isolate equipment, or dispatch work. ACTION remains locked until authorized execution systems write the work order or isolate the equipment. A coverage recommendation does not unlock that disposition. A dashboard that shows the gap is not a work order. A patrol route is not an isolation.

The Action chapter publishes the step. Direct plant execute stays off. The product does not dispatch unsupervised work to equipment. Work that follows the decision moves through the customer’s systems of record and the people who already hold operating authority.

A Decision Case that records coverage gaps or recommended coverage actions must not imply that Sync controls the plant.

The case stores the gap, or the proposed coverage action, beside the question and the evidence. That storage is a record. It is not control. Sync may have shown what was watched and may have recommended what to do next. A named human decided whether that recommendation stood. The plant changes only when authorized execution systems write the work order or the isolation.

The case does not absorb the historian, the CMMS, the permit, or the plant by recording a gap. This edition does not describe a live copy of an execution-system write returning into the case. When an authorized execution system does write the work order or record the isolation, that write is still their record.

A coverage record is not a verified outcome

Showing that a sensor exists, that a row exists, or that a route exists does not record whether a later action did what it was supposed to do. Verification Is Not Optional states the next gate. After a named human authorizes an action, the loop is not closed until verification is recorded. A coverage gap that was never turned into executed work has nothing executed to check. A work order that was written and never checked is still an open case.

Learning Requires a Verified Outcome states what a later case is allowed to inherit. Learning keeps the closed case. It does not keep a hoped-for outcome, a recommendation that was never authorized, or an action that was never verified. A coverage display is a further record that does not count. A later question that cites “we monitor everything” as if the plant were under control is citing a view. Unless verification holds an observed outcome, there is nothing verified to pass forward.

Evidence still has to be reconstructable. Evidence Lineage Is Not Optional asks whether a later reviewer can rebuild the proposal. The same reviewer should be able to tell coverage from control authority, and a recommended coverage action from the work order or the isolation that would carry it out. A lesson that merges them is a story about control the case does not hold.

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. Coverage shown on the case sits with evidence. A recommended coverage action, once a person decides, sits with the action step. Neither step is control of the plant. 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 Sync monitors a customer plant, and it does not claim that showing coverage controls one.

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 Question Is Not Decision, on why recording a reliability or maintenance question is not the human decision. Companion reading: Action Is Not Execution on why a recorded ACTION disposition is not plant execution, 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 Evidence chapter is where a coverage record belongs. It is not a grant of control.