Question Is Not Decision

A Decision Case opens on a reliability or maintenance question a named person can decide. The question is recorded before evidence or recommendation. Recording or refining a question is not the decision. Sync may hold the question and gather approved evidence; a named human accepts, rejects, escalates, or returns. An open question, a clarified question, or a rephrased question must not be read as authorization, execution, or plant control.

Reliability work collapses the first words because a clear question sounds like progress. Someone names the asset, the failure, or the deferral. The meeting tightens the sentence. The case now holds a better line. Later that line is cited as if the work were approved, the job were released, or the plant were under direction. It was not. The record stored a question. No named person had 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 the Question step cannot be read as the human decision. The manual is the public contents. The Question chapter and the Human decision chapter are the two steps this essay keeps apart.

The case opens on a question

The opening record is a reliability or maintenance question a named person can decide. It can be a failure that needs a cause. It can be a job someone wants to defer. It can be a condition someone wants watched until the next outage. The Question chapter publishes that opening. It is step 01 on the spine.

The question is recorded before evidence or recommendation. Evidence is not attached yet. No proposed next action has been drafted. Nobody has been asked to approve. The case has a subject a person could decide. It does not have the decision.

A question that never leaves this step remains a question.

Sharper wording does not advance it. Noting a missing fact does not advance it. The signed-in case can store the sentence so the loop has a start. Storage is not acceptance.

Recording or refining a question is not the decision

Sync may hold the question. Holding it means the signed-in case keeps the sentence where the loop starts, so a later reader can see what was asked. Sync may gather approved evidence onto that same case: 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. Gathering that record does not accept a proposal. There may not be a proposal yet.

Refining is the same kind of work. The question is narrowed to one asset. “Look at the pump” becomes “can this seal wait until the next outage.” The words are clearer. Authority has not moved. An open question, a clarified question, and a rephrased question are still questions.

Recording or refining a question is not the decision.

A later reader should be able to tell those three from a decision. If the case shows only the question, nothing has been accepted, rejected, escalated, or returned. If evidence has been added, the case shows a basis. It still does not show who decided.

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. That split is the subject of Recommend Is Not Authorize.

A named human accepts, rejects, escalates, or returns. That act is the decision. The Human decision chapter publishes it. The case keeps the person beside the proposal: who decided, and which recommendation they decided. Until a named person has made that act, the case holds a question and, at most, a proposal. The person who can accept the operational consequence is still the one who decides.

Read the two steps as separate chapters: Question and Human decision. The first is recorded before evidence or recommendation. The second is the named act on a recommendation. A well-phrased question is not a substitute for that act.

An open question is not authorization, execution, or control

An open question, a clarified question, or a rephrased question must not be read as authorization, execution, or plant control.

Authorization is the named human decision on a recommendation. The question sits before that decision. Clarifying the wording does not grant permission to do the work. Rephrasing it does not either.

The same question 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. A question is earlier than that disposition. It cannot be read as execution. ACTION stays locked until authorized execution systems write the work order or isolate the equipment. A question does not unlock it.

It also does not control the plant. Coverage Is Not Control states why sensors, CMMS rows, dashboards, patrol routes, and a recorded coverage gap are not control authority over work, isolation, or change. A question about coverage is still a question. Sync may hold the question and gather approved evidence. Sync may recommend. A named human decides. Authorized execution systems write the work order or the isolation. None of that follows from the question alone.

Verification Is Not Optional states the gate after an authorized action. The case is not closed until the check is recorded. A question that was never decided has nothing authorized to check. Citing the question as if the outcome were known treats an opening record as a closed case.

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. Question is step 01. Human decision is step 04. The question is recorded before evidence or recommendation. The decision is the named act that comes after a recommendation. 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 recording a question authorizes work, executes work, 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 Dashboard Is Not Decision, on why a dashboard of plant or maintenance state is not a Decision Case and not a decision. Companion reading: Coverage Is Not Control on why plant coverage is not control authority over work, isolation, or change, 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 Question chapter is where the case opens. It is not the decision.