Unknown Is Not Clear

In the Decision Case and in Recovery, missing evidence is recorded as unknown, not as clear or ready. Bad or not-ready evidence is blocked. A green dashboard, an empty field, or silence is not clearance. The operator must not treat unknown as go. A blank economic assumption is not zero.

Reliability work fills the gap because an empty place on the record looks quiet. The dashboard is green. A field was left blank. No one spoke to the missing item. The meeting treats that quiet as clearance: the evidence is fine, the case can proceed, the operator can go. It cannot. What was missing is still missing. The record has to say unknown. If the evidence is present and bad, or present and not ready, the record has to say blocked. Neither word means clear.

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. Assumption Is Not Evidence keeps that assumption from being stored as a recorded fact. A proposal with no basis is not ready for a human decision. What is still missing is unknown. Recovery uses the same constraint on the record: missing or stale evidence stays unknown, and bad or not-ready evidence is blocked.

Missing evidence is recorded as unknown

Unknown means the evidence is not on the record. It does not mean the condition was checked and found clear. It does not mean the job, the part, the zone, the feed, or the duration is ready. The operator reads unknown as a refusal to pretend the gap is a result.

On the Decision Case, the evidence a later reader can inspect is approved knowledge, asset context, work history, condition information, and that split. Stage-1 evidence is the record held on the case. A live connector that pulls historian or control-system tags sits outside this edition. An absent tag is not a recorded clear. It is still missing.

Recovery states the same rule in the constraint register. Job readiness refreshes labour, material, component-life, physical-zone, and external-resource constraints. Missing or stale evidence stays unknown. Manual fallback and connector ingestion are both source-bound: the value comes from a named source, or it is not a value. Until a tenant has actually supplied a provider endpoint, credential, and reviewed adapter, readiness reports unknown. That report is correct. It is not a claim that a customer feed is live, and it is not clearance to proceed as if the feed had arrived.

Unknown concurrency fails closed. New event work is unknown. Scheduling treats that work as sequential until an authorized human records a named parallel group and a substantive basis. The system does not invent a parallel plan to fill the unknown. Absent meter or interval evidence for component life stays unknown and is not inferred. If comparable history is too thin and no explicit planned or estimated hours are on the record, duration stays missing and approval is blocked. Missing is not a duration of zero, and it is not permission to approve.

Unknown is the absence of the record. It is not a finding that the evidence is clear.

Bad or not-ready evidence is blocked

Blocked is a different state. The evidence is present, and it is not fit to proceed. Bad evidence and not-ready evidence are both blocked. The operator does not relabel them unknown to make the case look open, and does not relabel them clear because someone hopes the next shift will fix the condition.

Recovery parts risk uses that split on material lots. Plan generation refreshes hard constraints for condition, certification, and staging. Missing staging evidence is unknown. Bad or not-ready evidence is blocked. Approved alternates and donor candidates stay advisory. They require a human action. They do not clear a blocked lot, and they do not turn unknown staging into a staged part.

Permit, isolation, and asset-state truth stay with the systems that already hold them. A Recovery constraint does not clear that truth by itself. Material that is still requested or short is not ready. Quality checks require explicit pass evidence before work completion. Those gates are blocked or unmet until the record says otherwise. Sync does not execute the plant work that would change them.

A green dashboard, an empty field, or silence is not clearance

A green dashboard shows a status color. It does not supply the missing evidence, and it does not convert unknown into clear. Dashboard Is Not Decision already keeps the display off the decision. This essay is the evidence state beside that display. A green tile can sit on the screen while labour, material, staging, component life, or a tenant feed is still unknown. The color is not clearance.

An empty field is the same kind of quiet. For Recovery economic assumptions, blank is not zero. Labour, overtime, contractor, logistics, risk, and life-cycle figures are human-entered. A blank is left blank. It is not stored as zero, and it is not treated as a measured saving. Those figures do not verify value. Verification of value remains a separate authority. An empty evidence field on the Decision Case is the same posture: the field does not become observed fact because nobody typed a number.

Silence is not clearance either. No alert, no comment, and no change on the tile do not record the evidence as present. Silence Is Not Clearance is that sentence at full length: silence, no reply, no alert, and an empty inbox are not authorization and not clearance. A missing operator response is not approved. A quiet dashboard is not controlled. Alert Is Not Decision keeps a rule crossing off the decision. The absence of that signal is not the opposite finding. A quiet queue does not mean the missing record was checked and found clear.

The operator must not treat unknown as go

Go would mean the evidence is sufficient for the next recorded step. Unknown is the statement that it is not. The operator leaves the case where the gap is, names what is missing, and does not proceed as if the gap were a pass. Recovery scheduling does the same with unknown concurrency: the work stays sequential until a named human records the parallel basis. Approval stays blocked while duration is missing. A rendered page is not that basis. Readiness that still says unknown is not a release.

This boundary is not the neighboring ones. Each of those essays still holds. None of them records missing evidence as clear.

Verification Is Not Optional says a claim needs a recorded check after a named human has authorized an action. Unknown is earlier and different. It is the missing record, not the check that closes the case. A case cannot verify an outcome from evidence that was never on the record.

Recommend Is Not Authorize says a proposal is not authorization. Unknown evidence is not a proposal that has been cleared. A drafted next action that rests on unknown is still not ready for a human decision. Drafting it does not fill the gap.

Honesty Boundary Is Not Optional says Sync states what is simulated, seeded, or out of scope. Naming that limit does not record missing plant evidence as clear. Simulated or seeded telemetry remains a practice record. It is not a live result, and it is not a substitute for the unknown the operator still has to leave visible.

Human Decision Is Not Optional says a named person must accept, reject, escalate, or return the recommendation, and that until that act is recorded the case is still a proposal. A named act does not convert unknown evidence into clear evidence. The person can refuse to decide while the basis is missing. The system does not decide for them, and it does not mark the missing basis clear so the act looks finished.

Question Is Not Decision, Dashboard Is Not Decision, and Alert Is Not Decision keep the question, the display, and the alert off the decision. Those inputs are not the decision. They are also not clearance of missing evidence. Opening the question, painting the tile green, or silencing the notice leaves unknown as unknown.

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. What is still missing stays visible. A proposal with no basis is not ready for the human decision that follows. Recovery keeps the operational constraint beside that chapter: missing evidence is unknown, bad or not-ready evidence is blocked, and blank is not zero. Later editions can deepen a chapter. The spine stays in this order.

What this article is not claiming

This is an essay about the evidence 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 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 unknown means clear, that blocked means ready, or that a blank economic assumption is zero. 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. A tenant feed that has not been configured stays unknown. Self-guided onboarding is not claimed as a live product path.

The series continues with Blank Is Not Zero, on why an empty field, a missing reading, or an unset value is not a measured zero. Silence Is Not Clearance states why no reply and an empty inbox are not authorization. Companion reading: Human Decision Is Not Optional on why a named person must record the disposition, Verification Is Not Optional on why a claim needs a recorded check, Recommend Is Not Authorize on why a proposal is not authorization, Honesty Boundary Is Not Optional on why simulated or seeded work is not marketed as live, Alert Is Not Decision, Dashboard Is Not Decision, and Question Is Not Decision on why those inputs are not the decision. A Reliability Assessment asks whether the records can support a conclusion. A Strategic Pilot is a governed proof around one operating decision. The Evidence chapter is the public statement of what is still missing.