Sync Field Manual

A Decision Case opens on a question a reliability or maintenance person can decide: what happened, what should happen next, or what can wait. The question is the case. On the signed-in product, that question is recorded as the first step of the loop, before evidence is attached and before anyone is asked to approve.

This chapter states that order. It does not name a site, a unit, or a result. A question that never acquires an evidence record remains a question.

Evidence is the part of the case a later reader can inspect: approved knowledge, asset context, work history, condition information, and a visible split between observed fact, assumption, and what is still missing. The recommendation waits on that record. A proposal with no basis is not ready for a human decision.

Stage-1 evidence is the record held on the case. A live connector that pulls historian or control-system tags sits outside this edition.

The recommendation states a proposed next action, the evidence it uses, and the uncertainty it leaves in view. The signed-in Decision Case can hold that proposal so a person can read it. Drafting the proposal leaves authority where it already sits.

Recommend is not authorize. Acceptance, rejection, escalation, and return belong to the human decision, under a named person.

A named person accepts, rejects, escalates, or returns the recommendation. That act is the human decision. The signed-in loop keeps it explicit: the case shows who decided, and the recommendation remains visible beside the decision.

Until that act is recorded, the case is still a proposal. Authority stays with the person who can accept the operational consequence.

Action is the record of the work the human decision authorized. It states what was approved to happen next and keeps that statement on the case, beside the question and the evidence. The signed-in loop includes this step so the decision and the intended work stay in one record.

Plant execute is outside Stage-1. 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.

Verification records whether the authorized action did what it was supposed to do, and which evidence would show that. The Decision Case keeps the check on the same record as the question, the recommendation, and the human decision.

Stage-1 verification is that recorded check. A live pull of control-system tags is not the proof this edition describes.

Learning keeps the closed case — question, evidence, recommendation, human decision, action, and verification — so a later question can see what was believed, what was authorized, and what was checked. The signed-in loop ends on that record.

This chapter publishes the rule. It names no plant, states no savings figure, and claims no prevented failure.

Three boundaries govern every chapter in this edition. Recommend is not authorize: a drafted proposal does not permit the work. Evidence is required: a recommendation that cannot show its basis is not treated as a decision. Stage-1 readiness means a signed-in user can complete the Decision Case — question, evidence, recommendation, human decision, action, verification, and learning — and this manual describes that journey.

Stage-1 is the limit of the claim. 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 contains no customer case study.