Green Is Not Go

Green is not go. The color is a rendering rule applied to a stored or computed value: a historian tag, a CMMS state, a calculated health score, or an alarm bit already held in the system that owns it, compared with the thresholds someone chose. Painting that comparison green does not run the asset, clear a hold, start equipment, or leave equipment in service. Go and clearance still require a named human decision against observed outcomes, named coverage and assumptions, and refusal when evidence is insufficient. Treating green as go is another path to false clearance under the honesty and verification boundary. Sync may surface the color 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.

A green board looks like a release. The tiles are the same color. The health score sits inside the band. The meeting treats the color as if the plant had been cleared to run, a hold had been lifted, a start had been approved, or equipment had been left in service. It has not. The screen updated because a query returned a value that met a rule. The rule can be a high limit, a low limit, a score band, or a status word. Someone chose those limits. The color does not say who, 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 paint green 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 green display cannot be read as permission to go. The Human decision chapter records who accepted, rejected, escalated, or returned. The color does not record that act.

Green is a value under a threshold

The color 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 renderer maps the comparison to green when the value sits inside the rule. A person looks at the renderer.

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

A green tile, a green status, a green health score, and an all-green dashboard are the same kind of display. Each one shows a stored or computed value under the thresholds someone chose.

Dashboard Is Not Control already treats the screen as a read. Refreshing, filtering, or drilling into the tile does not write a setpoint, an isolation, or a work order. This essay is the call the color invites on that same read. The tile is green because a value met a rule. Meeting the rule is not permission to run, clear, start, or leave equipment in service.

The threshold was chosen

Green 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 paints the tile 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 color only reports the comparison.

A tight band and a loose band paint the same color when the value sits inside. The color 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 score left out. Naming the threshold, the coverage, and the assumptions is part of the evidence. Leaving them unnamed and reading the color as go skips that record.

Calibration Is Not Validation keeps a small historical residual from being stored as fitness for the decision. A calibration can move a score into the band and paint the tile green. The residual is still not validation. The green tile is still not go. Accuracy Is Not Precision keeps repeatability from being stored as truth relative to the plant decision. A precise health score can sit in the same place every time and still be the wrong quantity for the decision. Painting that repeatable number green does not make it accuracy, and it does not make it permission.

A green feed 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 look green 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 color 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-green dashboard is green for the points on the screen. Equipment that is not on the screen is not cleared by the color of the points that are. Coverage of a watched set is not permission to order work, isolate equipment, or change the plant. A full green board of that set is not permission to run the equipment the set does not watch, and it is not permission to run the equipment it does watch.

Evidence from the plant beats the color. If the evidence is insufficient, the case refuses. A green tile does not fill the gap.

Go is a named decision

Run, clear, start, and leave in service are decisions about the plant. 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 does not support the call. The color 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. A green dashboard does not imply the act. The system does not accept the recommendation because the tiles are green.

Alert Is Not Decision states the other color. A threshold breach, a red tile, or a pager page can surface that something crossed a rule. Seeing it, acknowledging it, or silencing it is not a decision. A green status is the same class of display on the inside of the rule. The absence of red is not a decision to go. Clearing an alert because the tile returned to green 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. Green is not a stronger form of quiet. It is a color applied when a value met a rule. Quiet and green can both be true while the decision to run has not been made.

What the Decision Case may store

Evidence may cite what a display 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. 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 board painted green is not a customer plant release.

A recommendation may say investigate because of what the display showed, or it may say the color 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 equipment because a tile is green.

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 green tile does not unlock it. Sync does not write the work order. Sync does not start the asset. 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 green tile. A health score that returns to the band after someone else operated the plant is not the check. Sync must not auto-close, auto-authorize, or treat green 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 color. A later question that cites an all-green dashboard as if the plant had been cleared is citing a rendering rule.

Sync may surface a green 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 display showed and which threshold painted it. Human decision may hold who accepted the consequence. Verification may hold the observed outcome. None of those steps is a green tile. The Honesty boundaries keep this edition from treating a color 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 green tile runs an asset, clears a hold, starts equipment, leaves equipment in service, 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, 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 Status Is Not Clearance, on why a status field, a status tile, a status badge, or an all systems status OK string is a label on stored or computed values 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: 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, Dashboard Is Not Control on why a dashboard reads a value and does not write the plant, Alert Is Not Decision on why a rule crossing is not the decision, Telemetry Is Not Truth on why a stream of tags is not truth for the plant decision, Accuracy Is Not Precision on why repeatability is not truth relative to that decision, Calibration Is Not Validation on why a small historical residual is not fitness for the 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 color does not.