Action Is Not Execution

Action is not execution. Recording work intent on the Decision Case does not write a work order, isolate equipment, or dispatch work. Sync may recommend. A named human may decide. ACTION remains a locked disposition until authorized execution systems write the work order or isolate the equipment.

Reliability work collapses the last words because they sound alike. Someone accepted the recommendation. The case says action. The meeting moves on. Later the record is cited as if the job had been done. The plant was not touched. A work order was not written. Equipment was not isolated. The case stored an intention, and the organization treated it as execution.

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 Action step cannot be read as plant execution. The manual is the public contents.

The disposition is not the job

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 Action chapter publishes that step. On the case it is a disposition: work intent, held with the decision that produced it.

A disposition answers a narrow question. What work did the named person approve? It does not answer whether a work order exists, whether equipment was isolated, or whether anyone with operating authority has started the job.

Those are execution records. They are written somewhere else.

The work order is written in the system the site already uses to authorize maintenance — the customer’s CMMS or EAM, or the equivalent system of record. Isolation is the site’s existing practice for taking equipment out of service, under the people who already hold operating authority. The Decision Case does not become either record by storing the intent. Sync does not write them in this edition.

Sync may recommend. A human may decide. Neither executes.

Recommend is not authorize. A recommendation is an argument: a proposed next action, the evidence it uses, and the uncertainty it leaves in view. Drafting it leaves authority where it already sits. That split is the subject of Recommend Is Not Authorize.

A named person accepts, rejects, escalates, or returns the proposal. That act is the human decision. It records who decided. It still does not change the plant. Authority to accept a recommendation is not authority for software to dispatch work, open a permit, or isolate equipment.

Action sits after that decision so the approved intent stays on the same record as the question and the evidence. It does not promote the decision into execution. Read the two steps as separate chapters: Human decision and Action.

Direct plant execute stays off. 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.

ACTION stays locked

ACTION remains locked until authorized execution systems write the work order or isolate the equipment.

Locked means the Decision Case may store the disposition and may not treat that storage as the job. Until the customer’s authorized execution systems have written the work order, or the site’s isolation practice has taken the equipment out of service, the case has an intent. It does not have execution.

The write belongs to those systems and to the people who already operate them. Sync does not perform it. This edition does not describe a live copy of that write returning into the case. When an authorized execution system does write the work order or record the isolation, that write is still their record. The Decision Case can keep the disposition beside the question. It does not absorb the CMMS, the permit, or the plant.

The lock is the boundary in this edition, not a claim that a later integration has shipped. Stage-1 readiness means a signed-in user can complete the Decision Case. Plant execute is outside that claim. A live connector that pulls historian or control-system tags sits outside it as well. Simulated or seeded telemetry and assets are practice records. They are not a work order, and they are not an isolation.

Verification and learning cannot start from a locked intent

Authorization records who decided. The ACTION disposition records what was approved to happen next. Neither records whether the work was executed, or whether it did what it was supposed to do.

Verification Is Not Optional states the next gate. After a named human authorizes an action, the loop is not closed until verification is recorded. A disposition that never became a work order has nothing executed to check. A work order that was written and never checked is still an open case. The verification entry keeps three things distinct: what was supposed to change, which evidence would show it, and what was observed — including a result that did not match. A locked intent supplies only the intention.

Learning Requires a Verified Outcome states what a later case is allowed to inherit. Learning keeps the closed case. It does not keep a hoped-for outcome, a recommendation that was never authorized, or an action that was never verified. An ACTION disposition is a further record that does not count. A later question that cites the action as if the job were finished is citing intent. Unless verification holds an observed outcome, there is nothing verified to pass forward.

Evidence still has to be reconstructable. Evidence Lineage Is Not Optional asks whether a later reviewer can rebuild the proposal. The same reviewer should be able to tell the disposition from the work order and the isolation. A lesson that merges them is a story about work that may not have been done.

Read the gate in the Verification chapter, then Learning. Both sit after Action. Neither treats the disposition as the result.

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. Action is step 05. It sits after the human decision and before verification. 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.

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 or isolating equipment. 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 Coverage Is Not Control, on why plant coverage is not control authority over work, isolation, or change. Companion reading: Recommend Is Not Authorize on why a drafted proposal is not permission, Verification Is Not Optional on why the case stays open until the check is recorded, and Learning Requires a Verified Outcome on why a later case inherits the closed record, not the work intent. A Reliability Assessment asks whether the records can support a conclusion. A Strategic Pilot is a governed proof around one operating decision. The Action chapter is the public statement of the step this essay describes.