Honesty Boundary Is Not Optional

Sync states what is simulated, seeded, or out of scope. Calling a pilot "production," hiding simulation, or marketing self-guided as live when it is not, crosses the honesty boundary. Naming the boundary is not weakness — it is the industrial requirement. A Decision Case that pretends plant authority Sync does not hold is not a Decision Case.

Reliability work collapses the claim because a confident sentence looks like a closed record. A pilot is introduced as production. A practice record is narrated as a live plant result. A path that is not live is marketed as if a person could already walk it. The meeting treats those sentences as if the product held authority it does not hold, as if a simulated reading were an observed plant fact, or as if a self-guided path were a live product. They are not. The record either states its limit or it asks a later reader to believe a limit that was never named.

Sync keeps that split on the signed-in Decision Case and in the public contents of the loop. 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, and the standing limit beside it, in Field Manual v0. The manuals index lives at /manuals. This essay is why the Honesty boundaries chapter is not a footnote. The manual is the public contents. The chapter is the rule that governs every step.

The chapter states three boundaries

Field Manual v0 publishes three boundaries that 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 the 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. Those sentences are the public statement. They apply to the question, the evidence, the recommendation, the human decision, the action, the verification, and the learning. A later chapter does not get to outrun them.

Naming the boundary is not weakness — it is the industrial requirement.

The sibling chapters state what each step is allowed to be. The question is recorded before evidence or authority. Evidence is the inspectable record on the case: observed fact, assumption, and what is still missing. The recommendation states a proposed next action, the evidence it uses, and the uncertainty it leaves in view. A named person accepts, rejects, escalates, or returns. Action records the work that decision authorized, and plant execute stays outside this edition. Verification records whether the authorized action did what it was supposed to do. Learning keeps the closed case so a later question can see what was believed, authorized, and checked. None of those steps is a license to narrate a wider authority than the edition describes.

Hiding simulation crosses the boundary

Sync states what is simulated, seeded, or out of scope. Simulated or seeded telemetry and assets are practice records. They are not live plant results. A practice record can sit on a signed-in case so a person can learn the order. It can show a question, a basis, a proposal, a named decision, a work intent, a check, and what a later case is allowed to inherit. Completing that order does not convert the record into a site outcome.

Hiding simulation crosses the honesty boundary. Dropping the label, narrating the practice record as a live plant result, or letting a demo stand in for a verified outcome asks the reader to treat a practice basis as observed fact. The evidence chapter already requires the split: observed fact, assumption, and what is still missing. A simulated reading that is presented as observed fact fails that split. A seeded asset that is presented as a customer fleet fails it as well. The case can still be completed. It cannot be told as something the edition has said it is not.

Sync states what is simulated, seeded, or out of scope.

Out of scope is the same kind of statement. Plant execute, a live connector tag pull, SMTP invite delivery, and automatic revocation of access on expiry are outside this edition. Stating that they are outside is how a reader knows the signed-in journey does not include them. Silence on that point is not a smaller claim. It is a claim that leaves the limit unnamed.

A pilot called production crosses the boundary

A Strategic Pilot is a governed proof around one operating decision. Calling that pilot "production" crosses the honesty boundary. Production would mean the claim matches what this edition describes as live. This edition describes the signed-in Decision Case. It does not describe plant execute or a live tag pull as live. A governed proof of one decision is not a plant in operation under Sync, and it is not a customer case study.

The same sentence covers the Reliability Assessment. That assessment asks whether the records can support a conclusion. It is a bounded review. It is not a production deployment, and it is not permission for Sync to act on the plant. A reader who is told the pilot or the assessment is production has been told a different product than the one the manual describes.

This essay names no plant, states no savings figure, and claims no prevented failure. The honesty chapter already says this edition contains no customer case study. Inventing one to make the boundary feel concrete would cross the boundary the essay is stating.

Marketing self-guided as live crosses the boundary

Self-guided onboarding is not claimed as a live product path. Marketing it as live when it is not crosses the honesty boundary. The sentence is a product boundary of the same kind as the Stage-1 limit. Stating it is how a reader knows which path exists. There is a signed-in Decision Case a person can complete. Commercial entry is a bounded Reliability Assessment or a Strategic Pilot. Neither sentence is a claim that a person can onboard themselves into a live plant deployment and treat that path as production.

Marketing self-guided as live when it is not crosses the honesty boundary.

The workspace where the case is completed is not that marketing claim. A signed-in user can walk the loop the manual describes. Walking it does not make self-guided onboarding a live product path, and it does not make SMTP invite delivery or automatic revocation of access on expiry part of this edition. Those remain outside the claim. Naming them as outside is the honest description of the path that exists.

Pretended plant authority is not a Decision Case

A Decision Case that pretends plant authority Sync does not hold is not a Decision Case. Sync may show coverage, emit alerts, and recommend. A named human accepts, rejects, escalates, or returns. Authorized execution systems write the work order or the isolation. The case that says Sync ordered the work, isolated the equipment, or controlled the plant has left the boundary. That pretense is a different object. The Decision Case this manual describes does not hold authority the product does not have.

The peer essays already hold the adjacent lines. Alert Is Not Decision states that seeing, acknowledging, or silencing an alert is not a Decision Case and not a decision. Dashboard Is Not Decision states that a status display is not the decision. Recommend Is Not Authorize states that a drafted proposal is not permission. Action Is Not Execution states that a recorded ACTION disposition is work intent, not plant execution. Verification Is Not Optional states that the case stays open until the check is recorded. Each line fails if the case is allowed to pretend an authority the edition has withheld.

Action, in the field manual, records the work the human decision authorized and keeps that statement on the case. Plant execute is outside Stage-1. The product does not dispatch unsupervised work to equipment. Work that follows the decision moves through the customer systems of record and the people who already hold operating authority. A Decision Case that skips that sentence and speaks as if Sync held the plant is not the case the spine describes. It is a story about authority that was never on the record.

A Decision Case that pretends plant authority Sync does not hold is not a Decision Case.

Verification does not repair that pretense. The check asks whether the authorized action did what it was supposed to do, and which evidence would show that. Stage-1 verification is the check written on the case. A live pull of historian or control-system tags is not the proof this edition describes. A simulated signal is not that proof either. Learning inherits the closed case, including the limit that was named. It does not inherit a hoped-for plant result, and it does not inherit a claim that Sync executed the work.

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. The Honesty boundaries chapter sits beside the spine, not after it. Recommend is not authorize. Evidence is required before a recommendation is treated as a decision. Stage-1 readiness is the signed-in Decision Case. Later editions can deepen a chapter. They do not get to call a pilot production, hide a practice record, or market a path as live when this edition has said it is not. The spine stays in this order. The boundary stays in force.

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 Sync executes plant work, writes a work order, isolates equipment, or controls a plant. 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. Self-guided onboarding is not claimed as a live product path.

The series continues with Human Decision Is Not Optional, on why the recorded human decision is mandatory: a named person accepts, rejects, escalates, or returns the recommendation, and until that act is recorded the case is still a proposal. Companion reading: Alert Is Not Decision on why seeing, acknowledging, or silencing an alert is not a Decision Case and not a decision, Dashboard Is Not Decision on why a dashboard of plant or maintenance state is not a Decision Case and not a decision, Recommend Is Not Authorize on why a drafted proposal is not permission, Action Is Not Execution on why a recorded ACTION disposition is not plant execution, 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, not a production claim. The Honesty boundaries chapter is the standing rule.