Threshold Is Not Diagnosis

Sync recommends. A named human decides. Execution stays with authorized systems. On the Decision Case, a threshold breach is a number that crossed a line. It is not a diagnosis. It is not the case. A threshold breach can inform a recommendation. It does not name the failure mode, authorize action, verify outcome, or replace a named human decision.

The number crossed the line. The alarm band lit. The set-point was left behind. The limit on the screen is red. Someone says the asset is diagnosed, and the room treats the sentence as the Decision Case. Nobody named the failure mode. Nobody recorded the evidence that would let a later reader tell why the number moved. Nobody wrote accept, reject, escalate, or return. Nobody stored the verification. The Decision Case still has to show the question, the evidence, the recommendation, the named human decision, and the check. A line that was crossed is not that record.

This essay follows Proxy Is Not Outcome and stands beside Alert Is Not Decision, Correlation Is Not Causation, and Verification Is Not Optional. Proxy keeps a KPI, a leading indicator, a model score, a green tile, a closed work-order count, an MTBF estimate, a sensor health %, or any other stand-in from being stored as the verified operational outcome. Alert keeps seeing, acknowledging, or silencing an alert from being stored as a decision. A threshold breach can be what the alert reports. The breach is still not the diagnosis, and it is still not the case. Correlation keeps co-moving tags, coincident alerts, and dashboard trends from being stored as a recorded causal check, and it keeps them from authorizing action. Two tags crossing bands in the same window are still co-movement. They do not name the failure mode. Verification keeps the case open until the check is written down. A return inside the band is not that check.

Facts come before assumptions. The same gap has neighboring forms. Assumption Is Not Evidence keeps a belief, a habit, a prior shift's story, or an unverified model output from being stored as a recorded fact. "It crossed the limit, so we know what failed" is that story when the story is a line. Confidence Is Not Evidence keeps a strong gut feel, a high model score, or a manager's certainty from being stored as a recorded check. Being sure the breach means one failure mode does not record that mode. Trend Is Not Truth keeps a rising or falling line, a co-moving tag cluster, a week-over-week delta, and a trend narrative from being stored as a recorded causal check or a verified outcome. A line that later crosses a band is still a line. Unknown Is Not Clear records missing evidence as unknown, not as clear or ready. Blank Is Not Zero keeps an empty field from being stored as a measured zero. Silence Is Not Clearance keeps no reply, no alert, and an empty inbox from being read as approval. A quiet band is not clearance. A breach does not fill the blank with a failure mode, and it does not turn the missing reply into the named decision.

Orville Davis states the Decision Case order in Field Manual v0: Question, Evidence, Recommendation, Human decision, Action, Verification, and Learning. The manuals index lives at /manuals. Evidence is step 02. The Evidence chapter keeps a visible split between observed fact, assumption, and what is still missing. A threshold breach can be an observed fact that a number crossed a stored line. It is not a fourth column that names the failure mode, authorizes the work, or closes the case. A proposal whose only basis is that a line was crossed has no diagnosis a later reader can inspect. A proposal with no named human decision is not a Decision Case. Honesty boundaries sit beside the spine: recommend is not authorize, evidence is required, and Stage-1 does not treat a numeric threshold, a limit, an alarm band, or a set-point as a diagnosis or as live plant control.

A threshold breach is not a diagnosis

A diagnosis names a failure mode a later reader can inspect: what failed, on what evidence, and what is still missing. A numeric threshold is a line on a number. A limit is a bound. An alarm band is a range the display treats as out. A set-point is a target the control or the procedure was given. Crossing any of them says the number left the line. It does not say why. Those are different records. The band does not write the failure mode.

The meeting can note the breach. Noting it records that someone saw the number cross the line. It does not record the diagnosis, and it does not open the Decision Case. The failure mode stays in the evidence a later reader can inspect, or it stays missing. The breach stays a fact about the number, or it stays off the case as a display. Treating the breach as the diagnosis invents a name the record does not hold. The room thinks the mode is known. The mode was never written. That skip is the failure this essay names.

Sync may surface threshold breaches. Holding a breach beside a recommendation can inform that recommendation. Informing a recommendation does not name the failure mode. The recommendation is a proposal. The person who can accept the operational consequence records accept, reject, escalate, or return. If the only support is that a line was crossed, the proposal is not a diagnosis and it is not a closed case. The system does not auto-accept because the number left the band.

A limit, an alarm band, and a set-point are not the case

A Decision Case opens on a question a named person can decide. The question is recorded before evidence or recommendation. Recording that a limit, an alarm band, or a set-point was crossed does not record that question, and it does not record the decision. The case is the order: question, evidence, recommendation, human decision, action, verification, and learning. A red line is not that order.

A dashboard can show the breach. Dashboard Is Not Decision keeps that display off the decision. Color does not put it back as a case. Red is not a diagnosis. A return to green is not a verified outcome. Amber is not a partial decision. A green tile, an improved trend, or a cleared alert tile must not be read as authorization, verification of outcome, work-order execution, or plant control.

An alert that fired because the number crossed the band is still an alert. Seeing, acknowledging, or silencing it is not a Decision Case and not a decision. Clearing the queue because the number "came back inside" must not be read as authorization, verification of outcome, work-order execution, or plant control. Sync may emit alerts, coverage gaps, and recommendations. Sync may surface threshold breaches. A named human still opens a Decision Case on a question, cites approved evidence, and accepts, rejects, escalates, or returns.

This essay states no OEM limit and supplies no plant set-point. A line the meeting invented is not a diagnosis, and this page does not publish the number. The case holds the measurement that was stored, the line that was stored, and what is still unknown. It does not hold a limit this essay made up so the band would look decisive.

A breach does not name the failure mode

The same numeric threshold can be crossed for more than one reason. The instrument can be wrong. The window can be wrong. The set-point can have been moved. A related condition can have moved the number without being the mode the room wants to name. Co-moving tags that cross together are still co-movement. They are not a recorded causal check, and they do not authorize action. Naming the mode is a recorded claim. The breach is not that claim.

If the case cannot show the asset configuration, the failure and maintenance history, and the human judgment that connects the breach to a mode, the line is a number without a trail. Evidence Lineage Is Not Optional already requires that trail. A threshold does not shorten it. The breach can sit on the case as an observed fact, labeled as a fact about the number. The label does not promote the line into a failure mode. Honesty Boundary Is Not Optional says Sync states what is simulated, seeded, or out of scope. Naming that limit does not promote a practice breach into a plant diagnosis. The Honesty boundaries chapter keeps Stage-1 from claiming a live diagnosis the edition does not hold.

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 is a practice record. A practice breach is still a practice number. It is not a live plant diagnosis, and it is not a substitute for the failure mode the operator still has to name from evidence.

A breach does not authorize action

Authorization is the named act. A drafted next action is a proposal. Recommend Is Not Authorize keeps that proposal off the decision. A proposal that cites a threshold breach is still a proposal. The band can be red. The limit can be behind the number. Neither the color nor the line accepts the operational consequence. A threshold breach can inform a recommendation. It does not authorize action.

The system does not auto-accept because the number left the set-point. Sync recommends. A named human decides. If the only support is the breach, the proposal is not ready to be stored as authorized. A hoped-for reading of the line is not the decision.

Recording an ACTION disposition is work intent. It is not plant execution. Action Is Not Execution keeps that intent off the plant. Sync does not write the work order. The systems that already hold execution authority write the work order or the isolation. Execution stays with authorized systems. A threshold breach, however it is surfaced, does not move execution onto Sync, and it does not replace the named decision that would have to come first.

Crossing the line does not verify the outcome

Verification records whether the authorized action did what it was supposed to do. The case stays open until that check is on the case. A number that returns inside the alarm band is a later reading. It is not, by itself, the check. The band can be re-entered because the window changed, because the set-point moved, because the instrument changed, or because a different condition moved the number. The return does not record what the authorized change did.

A proxy that moved after the breach is still a proxy. A closed work-order count is still a count. A green tile is still a display. None of them verify outcome. Verification still records the actual check. Treating the return inside the band as the outcome invents false closure. The case looks finished. The check was never written.

Learning is what a later question is allowed to inherit. Learning Requires a Verified Outcome says the later question inherits that verified outcome, not a hope. Learning requires a verified outcome, not a hoped-for return inside the band. What was believed may include a labeled note that a numeric threshold was crossed. Learning does not inherit the breach as if the check had named the failure mode and confirmed the result. A later crew that repeats the work because the last number "already crossed," without the verification on the prior case, is inheriting a line. That is the wrong lesson. The Learning chapter publishes the closed record. It does not publish a threshold breach as a diagnosis.

A breach does not replace a named human decision

A named person accepts, rejects, escalates, or returns the recommendation. That act is the decision. Human Decision Is Not Optional says until that act is recorded, the case is still a proposal. A threshold breach does not replace a named human decision. The line does not sign accept. The alarm band does not sign reject. The set-point does not escalate. The limit does not return the proposal. The signed-in Decision Case keeps who decided visible beside the recommendation. The recorded act is mandatory.

A gate on the Decision Case is a recorded step that is either satisfied or not: evidence a later reader can inspect, a named human decision, a verification written down. A numeric threshold does not satisfy the gate. A limit does not open it. An alarm band does not stand in for the missing record. A set-point does not close it. A threshold breach can inform. It does not name the failure mode, authorize action, verify outcome, or replace a named human decision.

Unknown, blank, and silence stay what they are

Unknown stays unknown. Filling the unknown line with a threshold breach does not change the state to clear, and it does not name the failure mode. Bad or not-ready evidence stays blocked. A breach that looks related to the blocked item does not relabel blocked as ready. The operator must not treat unknown as go because the number left the band. Go would mean the evidence is sufficient for the next recorded step. A threshold breach is not sufficiency.

Blank stays blank. Zero is a verified measurement of none. A breach written into an empty field collects a flag. It does not collect the missing value. Recovery figures that were left blank stay blank. They are not inferred from a limit that was crossed. A blank verification field is not a verified outcome of none, and a return inside the band does not close it.

Silence stays silence. No reply is not approval. An empty inbox is not clearance. A quiet dashboard is not controlled. A number sitting inside the band on a quiet screen is still a number. It does not write accept, reject, escalate, or return. It does not record a check that nobody performed. A narrative about the quiet band does not turn the missing response into the named decision.

Sync recommends. Humans decide.

Sync may surface threshold breaches. Sync may hold the breach beside a recommendation. That is a proposal. The person who can accept the operational consequence records the decision. Until that act is on the case, the case is still a proposal. The system does not auto-accept because the number crossed a line. Sync recommends. A named human decides.

Execution stays with authorized systems. Coverage of the tag is not control of the plant. A Decision Case that records a threshold breach does not put Sync in control of the work, the isolation, or the change. The Verification chapter is the check. The breach is not the check. The Human decision chapter is the named act. The line is not the act.

Crossing a numeric threshold, limit, alarm band, or set-point is not a diagnosis and not a Decision Case. A threshold breach can inform a recommendation. It does not name the failure mode, authorize action, verify outcome, or replace a named human decision. Sync may surface threshold breaches. A named human still decides. Execution stays with authorized systems.

The neighboring boundaries still hold

This boundary is not the neighboring ones. Each of those essays still holds. None of them promotes a threshold breach to a diagnosis or to a Decision Case.

Proxy Is Not Outcome is the stand-in the room stores in place of the check. Alert Is Not Decision is the signal that something crossed a rule. Correlation Is Not Causation is the chart of co-movement. Verification Is Not Optional is the check that still has to be written. Threshold Is Not Diagnosis is the line itself: the numeric threshold, the limit, the alarm band, the set-point. A KPI does not become a diagnosis because it crossed a mark. An alert does not become the case because the band lit. Tags that travel together do not name the failure mode because they crossed together. A later reading inside the band does not close the case. The label stays. The diagnosis stays unwritten until the evidence names the mode. The decision stays unwritten until a named person records it.

Unknown, blank, and silence are still the missing record. A threshold breach does not interpret them into clearance. A case that is unknown, blank, or quiet is not made ready by a number that left a line. A crossed line is not a measurement of the missing field, and it is not the named decision.

The check that closes the case is still verification. The lesson a later case may inherit is still the verified outcome, not a hoped-for return inside the band. The trail behind a recommendation is still evidence lineage. An alert is still not a decision. A dashboard is still not a decision. A trend is still not the truth. Those records are either on the case or they are not. If they are not, a threshold breach does not supply them.

Where the public statement lives

Field Manual v0 is the public contents of the Decision Case. Start at the manuals index or open Sync Field Manual directly. Evidence is step 02. Observed fact, assumption, and what is still missing stay distinct. A threshold breach does not collapse that split into a diagnosis. A proposal with no basis is not ready for the human decision that follows. Verification is step 06. A number that returns inside the band is not the check. Learning is step 07. A later case inherits the verified outcome, not the breach the last shift treated as the diagnosis. Honesty boundaries keep the edition from treating a numeric threshold, a limit, an alarm band, or a set-point as a live diagnosis or as plant control. Later editions can deepen a chapter. The spine stays in this order.

What this article is not claiming

This is an essay about the record, not a customer case study. It names no plant, states no savings figure, and claims no prevented failure. It states no OEM limit and supplies no plant set-point. It does not claim that Sync executes plant work, writes a work order, isolates equipment, or controls a plant. It does not claim that a threshold breach is a diagnosis, that crossing a numeric threshold, limit, alarm band, or set-point is a Decision Case, that a breach names the failure mode, that a breach authorizes action, that a breach verifies outcome, or that a breach replaces a named human decision. It does not claim that self-guided onboarding is a live product path.

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, and a threshold breach on a practice screen is not a diagnosis. Self-guided onboarding is not claimed as a live product path.

The series continues with Symptom Is Not Cause, on why a vibration spike, a hot bearing, a pressure drop, an operator report, a CMMS complaint code, a red tile, or any other observed symptom is not the cause and not a Decision Case. Companion reading: Proxy Is Not Outcome on why a KPI, a leading indicator, a model score, a green tile, a closed work-order count, an MTBF estimate, a sensor health %, or any other stand-in measure is not the verified operational outcome, Alert Is Not Decision on why seeing, acknowledging, or silencing an alert is not a decision, Correlation Is Not Causation on why co-moving tags, coincident alerts, and dashboard trends are not a recorded causal check and do not authorize action, Verification Is Not Optional on why the case stays open until the check is recorded, Trend Is Not Truth on why a rising or falling line, a co-moving tag cluster, a week-over-week delta, or a trend narrative is not a recorded causal check and not a verified outcome, Confidence Is Not Evidence on why a strong gut feel, a high model score, or a manager's certainty is not a recorded check, Assumption Is Not Evidence on why a belief, a habit, a prior shift's story, or an unverified model output is not a recorded fact, Unknown Is Not Clear on why missing evidence is recorded as unknown, not as clear or ready, Blank Is Not Zero on why an empty field is not a measured zero, Silence Is Not Clearance on why silence, no reply, no alert, and an empty inbox are not authorization, Dashboard Is Not Decision on why a display is not authorization, Evidence Lineage Is Not Optional on why a recommendation you cannot reconstruct is not an industrial decision, Learning Requires a Verified Outcome on why a later case inherits the verified outcome, not a hoped-for return inside the band, Recommend Is Not Authorize on why a drafted next action is still a proposal, and Human Decision Is Not Optional on why the named act is mandatory. A Reliability Assessment asks whether the records can support a conclusion. A Strategic Pilot is a governed proof around one operating decision. The Verification chapter is the public statement of the check this essay refuses to replace with a threshold breach.