Status Is Not Clearance

Status is not clearance. The field, the tile, the badge, and the "all systems status OK" string are labels on stored or computed values: a historian tag, a CMMS state, a calculated health word, or an alarm bit already held in the system that owns it, compared with the thresholds someone chose. Printing OK on that comparison does not run the asset, release a hold, start work, leave equipment in service, or close a Decision Case. Clearance is a named human decision against observed outcomes, named coverage and assumptions, and refusal when evidence is not enough. Treating the label as clearance is another path to false clearance under the honesty and verification boundary. Sync may surface the status beside a Decision Case when the threshold, the coverage, and the assumptions are named. Surfacing is still a read. A named human decides. Verification stays open until a verified operational outcome is recorded. Direct plant execute stays off.

An OK badge looks like a release. The status field says normal. The tile says in service. The header string says all systems status OK. The meeting treats the label as if the plant had been cleared to run, a hold had been lifted, work had been started, equipment had been left in service, or a Decision Case had been closed. It has not. The screen updated because a query returned a value that met a rule, or because a system stored a word for that comparison. The rule can be a high limit, a low limit, a score band, or a status word. Someone chose those limits. The label does not say who decided, for which mode, or against which observed outcome. The process can sit inside the band and still be unfit for the decision in the room. A sensor can be frozen on a good value. A point can be bypassed. A calculation can store OK without seeing the failure mode the question is about.

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 status label cannot be read as clearance. The Human decision chapter records who accepted, rejected, escalated, or returned. The status field does not record that act.

Status is a label on a value under a threshold

The label has four steps. A source holds a value: a historian tag, a CMMS state, a calculated health score, or an alarm bit. A rule compares that value with limits a person, a procedure, or a configuration chose. A stored word or a renderer maps the comparison to a status field, a status tile, a status badge, or an all systems status OK string when the value sits inside the rule. A person reads the label.

None of those steps is clearance. The comparison can be true and the asset can still be the wrong one to run. The band can have been set for a different operating mode. The word can be a rollup of points that do not include the failure the question is about. The status field can be the last good word the source stored, not a fresh observation of the plant.

A status field, a status tile, a status badge, and an all systems status OK string are the same kind of label. Each one names a stored or computed value under the thresholds someone chose.

Green Is Not Go already treats the color as a rendering rule. Painting the comparison green does not run the asset. This essay is the word that often sits on that same comparison. The tile can be green, gray, or uncolored. The field can say OK, normal, available, or all systems status OK. The string is still a label. Meeting the rule is not clearance to run, release, start work, leave equipment in service, or close a Decision Case.

Dashboard Is Not Control treats the screen as a read. Refreshing, filtering, or drilling into the status tile does not write a setpoint, an isolation, or a work order. The badge on that read is still a read. A status string does not become a command because it says OK.

The threshold was chosen

Status does not arrive from the asset. It arrives from a comparison. The high limit, the low limit, the score band, and the status word that fills the field are settings. They can come from an OEM sheet, a site procedure, a model, or a default left in a configuration. This essay states no OEM limit and no operating threshold. It states that whatever limits are in use were chosen, and that the label only reports the comparison.

A tight band and a loose band can store the same OK when the value sits inside. The badge does not show which band was used. It does not show the mode the band was written for. It does not show the points the rollup left out. Naming the threshold, the coverage, and the assumptions is part of the evidence. Leaving them unnamed and reading the status as clearance skips that record.

A status string can still be the wrong evidence

Telemetry Is Not Truth keeps a stream of tags, sensors, historians, SCADA, and CMMS counters from being stored as the plant decision. A dense feed can compute an all systems status OK string and still be the wrong sensor, the wrong unit, a stale sample, an aliased signal, or a proxy that does not track the failure mode. The label does not correct any of those. It reports that the values which arrived sat inside the thresholds someone chose.

Coverage Is Not Control names the watched set. An all systems status OK string is OK for the points the status was computed from. Equipment that is not in that set is not cleared by the label on the points that are. Coverage of a watched set is not permission to order work, isolate equipment, or change the plant. A status badge for that set is not clearance to run the equipment the set does not watch, and it is not clearance to run the equipment it does watch.

Evidence from the plant beats the label. If the evidence is not enough, the case refuses. A status field does not fill the gap.

Clearance is a named decision

Run, release, start work, leave in service, and close a Decision Case are decisions. Each one needs a named person who can accept the operational consequence, a record of what was observed, the coverage and assumptions that bound the evidence, and a refusal when that evidence is not enough. The status string is none of those records.

Human Decision Is Not Optional states the act. A named person accepts, rejects, escalates, or returns the recommendation. Until that act is recorded, the case is still a proposal. An all systems status OK string does not imply the act. The system does not accept the recommendation because a badge says OK.

Alert Is Not Decision states the other side of the same rule. A threshold breach, a red tile, or a pager page can surface that something crossed a limit. Seeing it, acknowledging it, or silencing it is not a decision. A status of OK is the label on the inside of the rule. The absence of an alert is not clearance. Returning a field to OK because an alert cleared is not authorization, not verification of outcome, and not plant control.

A quiet board is not clearance either. Silence Is Not Clearance states that boundary for no reply, no alert, and an empty inbox. Status OK is not a stronger form of quiet. Quiet is the absence of a message. The status string is an affirmative label applied when a value met a rule. Quiet and OK can both be true while the decision to run, release, or start work has not been made.

What the Decision Case may store

Evidence may cite what a status field held when the source, the time, the threshold, the coverage, and the assumptions are named. That citation is a record of a read and a comparison. It is not a record that the asset was cleared to run, that work was released, or that the case was closed. 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. A practice status that says OK is not a customer plant release.

A recommendation may say investigate because of what the status showed, or it may say the label is not enough. The proposal states a next action, the evidence it uses, and the uncertainty it leaves in view. Drafting it does not change the plant. Recommend Is Not Authorize states that split. A named person accepts, rejects, escalates, or returns. The act records who decided. It still does not start work because a badge says OK.

If the named person approves work, the case may store the intent. The Action chapter records that intent. Action Is Not Execution keeps that intent off the plant. ACTION stays locked until authorized execution systems write the work order or isolate the equipment. A status field does not unlock it. Sync does not write the work order. Sync does not start the asset. Sync does not release a hold. The systems that already hold execution authority write the work order or the isolation. Authorized execution systems perform that write. Direct plant execute stays off.

Verification asks whether the authorized action did what the decision named. The Verification chapter publishes the check. Verification Is Not Optional states the gate: the case stays open until the check is recorded. The check is the observed outcome, not a later status badge. A field that returns to OK after someone else operated the plant is not the check, and it does not close a Decision Case. Sync must not auto-close, auto-authorize, or treat status clearance as Learning credit.

Learning Requires a Verified Outcome states what a later case may inherit. Learning keeps the closed case. It does not keep a status word. A later question that cites an all systems status OK string as if the plant had been cleared is citing a label.

Sync may surface a status beside approved evidence when the threshold, coverage, and assumptions are named. Sync refuses false precision. Sync refuses when evidence is insufficient. A named human still decides.

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. Evidence may hold what a status field showed and which threshold stored the word. Human decision may hold who accepted the consequence. Verification may hold the observed outcome. None of those steps is a status badge. The Honesty boundaries keep this edition from treating a label as clearance. 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 status field runs an asset, releases a hold, starts work, leaves equipment in service, closes a Decision Case, or controls a plant. It does not claim that Sync executes plant work.

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, starting equipment, releasing a hold, 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 Ready Is Not Cleared, on why a green ready flag, a ready checklist, a ready-to-start badge, or a system ready, crew ready, or parts ready string is a readiness label under the thresholds someone chose, and why that label is not clearance to run, release, start work, leave equipment in service, or close a Decision Case. Companion reading: Green Is Not Go on why a green tile is a display under a threshold and not permission to go, Silence Is Not Clearance on why no reply and an empty inbox are not authorization, Alert Is Not Decision on why a rule crossing is not the decision, Dashboard Is Not Control on why a dashboard reads a value and does not write the plant, Telemetry Is Not Truth on why a stream of tags is not truth for the plant decision, Coverage Is Not Control on why the watched set is not permission to order work, Verification Is Not Optional on why the case stays open until the check is recorded, and Human Decision Is Not Optional on why a named person still has to accept, reject, escalate, or return. 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 records the act. The status label does not.