The Feeder That Could Not Be Restored Yet

The story

18:06 — one protective operation changes three local truths

At 18:06, Feeder 27 trips during a windstorm. Laila Morgan, Ridgeline Electric's distribution system operator, sees the protection source report the breaker open in a protection-lockout state. That source state is not worker protection, field clearance, or permission to switch. The exact records are protection event PROT-771 and outage case OUT-402, which initially associates 3,420 synthetic service points with the interruption across North, Central, and River.

Laila's goal is to determine whether North and River can enter a partial-restoration proposal while damaged Central remains held out. Mateo Ruiz owns the field-clearance evidence she will need. The outage clock has started for all 3,420 represented service points, but neither urgency nor a green map can supply the missing safety evidence.

The initial records are consequential and narrow. They do not establish what caused the trip, whether equipment is damaged, whether any conductor is safe, where a work boundary exists, or when service can return. Grid records the source-reported event and starts evaluating dependencies without filling in those missing truths.

18:09 — a plausible topology appears

The authored topology suggests a possible future configuration: after separately authorized external switching, North would return from the Feeder 27 source, River would transfer through a tie to source F31, and damaged Central would remain held out. This is a proposal to screen, not the current topology or a switching sequence.

The Scenario deliberately uses only a simple authored screen:

Segment	Synthetic service points	Proposed treatment	Simple authored screen	Result
North	1,480	Return from F27	1.20 × 1.25 = 1.500 MW ≤ 1.65 MW	Pass
Central	1,160	Hold out	0.92 MW; no pickup is screened	Remains out
River	780	Transfer through F31	0.58 × 1.25 = 0.725 MW ≤ 0.82 MW	Pass

The screened proposal covers 2,260 of 3,420 service points, displayed as 66.1 percent under the fixture's declared rounding rule. The capacity screen passes. That result is not a power flow, protection study, switching instruction, safety conclusion, authorization, execution report, or restoration count.

18:14 — the plan depends on a pre-event fact

The selected record for isolation point SW-27-4 says open, but its observation time is 18:05:51—twenty seconds before the feeder trip. The outage system has derived an isolated label from that and another device indication.

Grid keeps the supporting facts visible while blocking the favorable conclusion. A symbol on a map is not field clearance. A topology label cannot prove that Ridgeline's external employee-protection conditions have been completed.

18:16–18:23 — a field-link gap returns with a contradiction

Mateo Ruiz, the employee responsible for clearance CLR-731, loses the field connection for seven minutes. His crew continues under Ridgeline's external procedure. The control-center model sees only the age of its last accepted field evidence; it neither directs the crew nor invents an update.

During the gap, the device adapter redelivers the original SW-27-4 event. The source event ID and 18:05:51 observation time are unchanged. The duplicate is ignored and does not refresh the observation; recent receipt cannot repair stale evidence.

When the connection returns, Mateo reports that the local position indication is insufficient to establish the work-zone boundary and that damaged conductor is visible inside the held-out Central segment. The outage-system label supports a favorable isolation conclusion; the field report refutes it. The evidence is contradictory, so the represented policy blocks the proposal.

The model does not average away the disagreement or decide that one source always outranks another. The disagreement is the decision-relevant state.

18:25 — three alternatives expose the stopping point

The fixture evaluates exactly three defined alternatives:

Alternative	Result	Why
Return all three segments from Feeder 27	Rejected	The Central damage and isolation gate remain unresolved.
Transfer North and River together through F31	Rejected	(1.20 + 0.58) × 1.25 = 2.225 MW, above the authored 0.82 MW tie headroom.
Hold Central out, return North from F27, and transfer River through F31	Conditional	The simple load screens pass, but current clearance evidence is still missing.

Completing that small search does not prove the topology complete, find a global optimum, or make the third plan electrically feasible or safe. It only explains why one authored proposal survives farther than the other two.

18:37 — external clearance evidence changes what may be proposed

Between 18:23 and 18:37, Mateo and Ridgeline's system operator complete the utility's external field and safety process. Grid neither encodes nor instructs those steps. At 18:37, that process produces attributable report CLR-731-R4, bound to the held-out Central zone, responsible employee, procedure revision, source time, and external system record.

That report changes the isolation evidence from unresolved to supported. It does not release the clearance, energize equipment, or authorize the partial plan. It permits the model to assemble a packet for the person who holds the next authority.

18:40–18:47 — human authority and external execution remain separate

Laila reviews packet RESTORE-PACKET-220, which binds the protective event, current topology, Mateo's clearance report, the surviving alternative and its arithmetic, the held-out Central boundary, unresolved assumptions, external validation sources, and stop conditions.

Laila authorizes external switching order SO-220 under Ridgeline's represented policy. Her assertion records the decision on one exact packet. It does not move a switch.

The external DMS acknowledges the request at 18:40:08. It has received the request; it has not proved execution. Later SCADA and field reports describe external work, while protection, meter, and outage sources support later device and service states. Only after the source-defined outage aggregate arrives does the model publish the source's initial label: 2,260 restored / 1,160 remaining. Even then, that aggregate does not prove that every premise, device, or person has service or is safe.

19:04 — the restoration count is corrected

Meter exception revision METER-552 reports sixteen synthetic River service points still without service because of a separate secondary condition. The current figures become:

restored = 2,260 - 16 = 2,244
remaining = 3,420 - 2,244 = 1,176
displayed restored share = 65.6%

The correction does not undo Laila's earlier authorization or prove it was wrong. It changes the current outage state, adds follow-on work, and makes the first operations summary and public-update draft stale. Their successors must use 2,244 while retaining the lineage back to the initial source report.

The opening question therefore has a bounded answer. The capacity screen remained conditional until a current external clearance report made the partial plan reviewable. Laila's authorization enabled only an external request; later source reports separately described work and corrected the service count. None of those states establishes electrical safety, complete restoration, or a public outcome.

Why this setting is recognizable

The U.S. Department of Energy's public restoration overview describes utilities maintaining plans to restore electricity safely after outages. DOE's Power System Data Analytics describes measurement, processing, display, system visibility, and operator-support tools. OSHA's electric power generation, transmission, and distribution standard distinguishes relevant system-operator and employee-in-charge responsibilities and addresses controlled deenergizing, clearance, and reenergization within its applicability.

Those official sources ground only the high-level restoration, operator-support, and clearance context. They do not establish Ridgeline's topology, calculations, facts, authority delegation, switching sequence, Grid composition, or result. Actual applicability, system state, procedure, engineering, and safety judgments belong to the responsible utility and qualified professionals.

Where the model stops

Grid can represent selected evidence, freshness, contradiction, declared alternatives, a synthetic capacity screen, an exact packet, and correction lineage. It cannot determine electrical truth, perform power flow or protection analysis, establish deenergization or clearance, issue or execute switching, direct a crew, release a clearance, energize a feeder, certify restoration, or publish a public outcome.

This public page contains no real utility, location, voltage, coordinate, control endpoint, protection setting, credential, customer record, or crew location. It is not an operational diagram and must not be adapted into switching guidance.

What remains to prove

Source revision 2026-08-27.1 has reviewed domain context, product boundaries, and a public-suitability finding, so this authored, non-operational scenario can be published at R2. The fixture itself remains authored.

The next proof is an exact deterministic implementation of the three segments, calculations, stale indication, seven-minute link gap, duplicate, contradiction, clearance state, three alternatives, authority stop, external evidence states, and sixteen-service-point correction. It needs a separately identified independent oracle reviewer, retained execution and verification evidence, negative cases, and a high-consequence assurance review. Any intended-environment work would additionally require utility-owned engineering, safety, cybersecurity, identity, delegation, source, control, records, accessibility, reconciliation, and operator qualification. No later readiness label can turn this editorial fixture into a switching procedure or electrical safety claim.