Intake status answers whether the requested material arrived. Evidence state answers whether that material supports a later claim. Day 1 records the first and deliberately leaves the second at Not Assessed.

Technical identifiers and raw source labels remain in their recorded language when the interface switches to French. The UI may translate; the evidence does not.

A later reviewer must be able to distinguish the original payload from a normalized derivative and verify whether the frozen Day 1 object changed.

AUTUM preserves source time, server time when available, extraction time and receipt time. Cross-system chronology cannot be trusted if clock origin and skew are unknown.

Machine-readable sources receive an intake profile before they are allowed to feed a control rule. Quality profiling describes the payload; it does not yet decide whether the evidence supports the case.

Each source is authoritative only for a bounded statement. AUTUM joins authority domains; it does not promote one database into universal ground truth.

Day 1 freezes field meaning before transformation. A value, unit, type, null rule and source owner are treated as part of the evidence contract.

PHX-001 records the access identity, boundary, permission, logging and expiry. No Day 1 credential permits a plant command or source-record deletion.

Day 1 may record a provisional hierarchy from the case charter and source metadata. It may not yet certify cross-system aliases. That certification is Day 2.

Normalization and later rule evaluation create new objects. They do not erase the source entity that generated them.

The gaps remain attached to source owners and downstream claims. None blocks Day 2 identity reconciliation.

Day 1 records the inconsistency and stops. Day 2 must establish the alias relationships, context and confidence before a cross-system join is permitted.

PHX-D01 uses public standards as design constraints. This demo does not claim AUTUM, the synthetic client or PHX-001 is certified against them.

Yes. Custody, time, quality, access and authority domains are now visible. The next controlled problem is identity.

P204 appearing inside a string is useful evidence, not proof. Day 2 classifies every relationship before AUTUM allows one source to be joined to another.

These synthetic records are the minimum evidence used to classify identity and dependency. Day 2 does not infer a relationship from naming convention alone.

The graph uses typed relationships. That protects AUTUM from collapsing an asset, its sensor and the production line it supports into one synthetic object.

The decision table determines what AUTUM may later join automatically and what must remain a relationship instead of an identity alias.

A certified alias must survive more than name similarity. These tests are recorded so a later reviewer can challenge the relationship.

Join permission is a governed output of Day 2. Later controls may not bypass this table because two fields happen to look similar.

The final artefact records approved relationships and explicit rejections. “Rejected as alias” is a useful result, not a failure of the case.

The activity sequence records candidate generation, evidence tests, relationship classification and final join permission.

Every record used in the baseline must represent a state known at or before 09:40 local time. Later updates may be appended as subsequent events, but they cannot silently rewrite the frozen baseline.

Day 2 established which joins are permitted. Day 3 now uses those joins without allowing any source to overrule another source outside its authority domain.

The chart is descriptive, not predictive. It shows the accepted SCADA / historian observations in the frozen case window.

Day 3 does not say the production system is wrong. It says the production system answers a narrower question than the cross-system operating record.

Claims are promoted only to the level supported by the retrieved record. The Case Room explicitly records statements it cannot yet make.

The reconstruction is versioned and reproducible from the certified joins, source timestamps and evidence states.

A visible mismatch is not authority to act. Day 3 ends before rule evaluation, exception creation or operational intervention.

AUTUM will retain the depth of the earlier Evidence Room model, but it will not manufacture three documents per day for symmetry. Every material source, controlled artefact and decision record receives its own inspectable record when it carries evidentiary or governance weight.

Every input is bound to a source, authority domain, D02 relationship and D03 evidence state. ORC-17 is not allowed to infer missing fields from narrative text or from a different authority domain.

ORC-17 separates “may I evaluate?”, “does the contradiction exist?” and “how far may the software escalate?”. This prevents a governance gap or a single sensor spike from independently creating a critical exception.

The ladder separates observation from escalation and human authority. Level 5 protects the software boundary; it is not an autonomous plant shutdown instruction.

A world-class control rule is defined as much by its non-trigger conditions as by its trigger conditions.

This demonstration test bench changes only the in-browser scenario state. It does not modify the frozen source records or the historical Day 3 baseline.

These synthetic unit tests protect the control from later logic drift. A rule version that changes an expected result requires a new controlled version.

When ORC-17 triggers, the evaluation record must retain the exact evidence basis used at evaluation time. Later source changes cannot rewrite the original decision basis.

Against OBS-D03-001, the core contradiction is established and the unresolved override record raises the response to Level 4. The software is therefore permitted to create the governed exception record and route the operating decision — not to select the operating state itself.

Reason codes are explicit and version-bound. They describe the control conditions observed at opening time; they do not attribute intent and they cannot be rewritten after a later source update.

EXC-204-17 points to a frozen evidence snapshot rather than to “whatever the source system says now”. This protects the historical basis of the exception when later records change.

The exception carries the same authority-domain discipline as the underlying case. No source is promoted beyond the statement it is entitled to support.

The exception remains open until a named authority has dispositioned the operating question and the closure basis is captured. A return to green telemetry alone does not close the record.

AUTUM assembles and routes the record. Technical confirmation, recommendation and final operating authority remain separated.

These timings are synthetic PHX-001 case controls, not universal industry standards. They define the review expectations for this demonstration exception.

Closure is a governance event. The record closes only when the disposition, authority, evidence basis and linked control state are explicit.

The visual record is backed by a structured exception object. IDs, versions and reason codes are stable machine references; the interface language may change without changing the record.

Exception creation, routing and subsequent changes are recorded as append-only case events.

Day 6 does not score evidence with a decorative percentage. A record is challenged against six review dimensions and then assigned a defensible state.

The register is transversal to the daily workspaces. Blue links open the individual Evidence Record without exposing raw technical detail in the main reading flow.

Gaps are not generic to-do items. Each gap carries an owner, an affected claim, a decision consequence and a disposition requirement.

Day 6 decides which statements are sufficiently supported for a decision-maker and which must remain held, qualified or excluded.

The decision-maker does not receive the entire Case Room as an undifferentiated dump. Day 6 packages the minimum evidence necessary to understand the operating contradiction and its limits.

Day 6 creates a review trail for evidence promotion, qualification and exclusion.

The case is deliberately split into three authority lanes so technical judgement, operating control and capital commitment cannot collapse into one role.

The matrix converts job titles into governed decision rights for PHX-001. “Consulted” or “expert” is not treated as implicit approval authority.

The operating decision has a defined chain of contribution. No technical recommendation is silently promoted into final authority.

A job title alone is insufficient where the controlling matrix requires a delegation or approval limit. Day 7 records the authority basis used by the Case Room.

PHX-001 preserves separation between evidence creation, technical confirmation, operating disposition and financial commitment.

The authority map is tested against common failure paths before it is allowed to drive the decision workflow.

The operating decision and the replacement-capital decision are linked by context but remain separate governance objects with separate authorities and closure effects.

A robust authority model is defined by the routes it refuses as much as the routes it allows.

Day 7 records the authority sources, role boundaries, delegation checks and rejected routes used to build the governance map.

The authority receives only the claims, evidence, options and limitations necessary to determine a governed outcome. Technical depth remains available through blue record links and the Evidence Room.

DEC-1842 is the operating decision required by EXC-204-17. The Operations Director owns the final disposition; technical and maintenance roles contribute separately.

Supported facts and unresolved questions remain visible beside one another so uncertainty cannot disappear during executive compression.

AUTUM does not calculate a hidden recommendation score. Decision criteria remain visible and separately sourced.

PR-4481 remains a Purchase Request, not a Purchase Order. Its capital decision is linked to the case but does not determine the operating state of P-204.

The Case Room exposes the dependency between the decisions without allowing one approval to masquerade as the other.

Decision intelligence stops at the human authority boundary. The system may make the decision easier to defend; it may not make the decision disappear.

A final decision record must show who confirmed the evidence, who recommended, who decided and what evidence basis was used.

Day 8 records creation of the operating and capital decision packs while retaining their separate authorities and evidentiary limits.

The case has moved beyond detection. The remaining question is whether the current operating state can be defended, altered under a certified envelope or stopped under controlled procedure while the technical and capital paths progress separately.

Three forms of pressure converge. None of them alone replaces the operating authority, but together they justify immediate governed disposition.

AUTUM does not rank the options with a hidden score. It shows which options are currently governable, which require additional evidence and which authority must carry the decision.

The decision pack is designed to reduce verification work without collapsing technical, financial and governance questions into one statement.

Day 9 deliberately excludes expected-loss mathematics because PHX-001 has no validated probability-of-failure model. Economic consequence and engineering probability remain separate questions.

Select a sensitivity factor and a duration. The console recalculates the linearized full-stoppage scenario only.

The schedule distinguishes owner-confirmed scenario inputs from accounting facts. Confirmation strengthens the scenario; it does not turn it into realized loss.

The values below apply a disclosed component profile across five comparison windows. They do not forecast outage duration.

The options from DEC-1842 remain governance choices. Day 9 exposes what is economically known, what is missing and what cannot be compared yet.

PR-4481 remains a separate capital decision. Comparing its value with scenario exposure provides scale, not an automatic ROI argument.

Day 9 records assumption confirmation, sensitivity construction and the boundaries retained in the decision pack.

These are comparison scenarios, not forecasts. They show the economic scale associated with different full-stoppage windows using the disclosed component profile. No probability is assigned to any window.

PR-4481 is a USD 184,000 Purchase Request. The comparison below helps the authority understand magnitude. It does not establish payback, avoided loss or a procurement recommendation.

Economic consequence can sharpen urgency. It cannot fill gaps in engineering probability, operating authority or procurement governance.

These synthetic dispositions exist to complete the product demonstration. They are explicitly attributed to the client-side roles established in the Day 7 Authority Map.

The product outcome is a change in governed operating state and decision accountability — not merely a dashboard that looks different.

Closure is based on authority, evidence and resulting control state. The exception does not disappear because telemetry changed or a timer expired.

The final brief compresses the case without erasing evidence limits, decision ownership or the distinction between operating and capital actions.

Each work stage remains independently versioned so later corrections cannot rewrite the basis of earlier decisions.

PHX-001 can close once the decision objective is satisfied even while non-blocking historical evidence gaps remain visible for future work.

The closure trail distinguishes human decisions, client execution and AUTUM recording actions.

This view preserves the final case state without rewriting the opening baseline. Every row retains the authority domain of its source.

The operating record does not flatten SCADA, MES, CMMS, ERP and governance records into a single undifferentiated truth source.

Case closure ends the decision objective. It does not terminate the maintenance, procurement or inspection workflows that continue afterwards.

The asset record joins identity, telemetry, work control, governance, decision and procurement without confusing those objects with each other.

The timeline preserves the chronology required to reconstruct how a physical condition became a governed decision.

The Evidence Room exists to make the decision basis challengeable. It does not reward volume of documents; it records evidentiary sufficiency and limitation.

Every material claim used by authority is linked to a source domain, evidence state, limitation and downstream decision use.

Records become decision evidence only after identity, chronology, authority-domain and limitation checks are satisfied.

The permanent decision view preserves the evidence, authority, selected outcome and downstream effect of each decision independently.

Technical confirmation, operating disposition and procurement approval are deliberately separated because they carry different authority and risk.

The case closed against authority and evidence, not because a timer expired or a dashboard status changed.

Two historical gaps remain visible because neither was required to support the final operating disposition.

The output is a reusable decision trace, not a disappearing alert.

Closure is a governed state transition. Every mandatory condition is attributable to a record, source or named authority.

The case objective is complete, but the underlying asset, maintenance and procurement workflows continue to generate new operational records.

The durable output is the control architecture and evidence model that can be re-used on another asset, site or exception class.