An illustrative Tessure world
Critical infrastructure
A ground boundary test, two hostile aerial tracks and denied control requests meet a local protective response at a blue-hour substation. Explore the authored incident, the evidence behind the decision and the physical response. This is an authored illustration, not working detection software.
World 06 / Critical infrastructure
Local protection during a coordinated incident
A ground boundary test, two hostile aerial tracks and denied control requests meet a local protective response at a blue-hour substation.
The illustration plays from beginning to end, including the operator’s review and response. Pause or jump to any moment to explore; these controls do not operate a real site.
The idea this world exploresProtect people locally while keeping ground, air and denied-control observations distinct. An unavailable remote link neither removes local command authority nor proves who caused the incident.
Read the story as text
Coordinated perimeter and control incident
A powered site, a normal round
Authored red-team simulation at a fictional substation. The technician completes a round; the operator and guard remain at the shelter. The white inspection drone is docked beside the yard. Equipment and local-node power stay on throughout.
Fictional roles: Two hostile aerial actors and a ground pair are scripted roles, not identities inferred from appearance.
Three incident streams emerge
The ground pair approach the service boundary. A dark quadrotor enters from the west; an ochre six-rotor aircraft follows a different eastern path. These are hostile roles in this authored incident, not a sensor judgment about identity.
Ground approach + air tracks: Separate visible actors approach the fictional site.
A separate western air track
The dark quadrotor banks into its western observation leg. The western sky head is pitched toward this approach; its observation is separate from the ground gate test.
Western sky camera: Distinct western aerial route, observed within a partial illustrative sector.
The ground pair test the gate
One actor stops at the latch, turns and reaches to pull the locked gate; the second watches nearby. The gate flexes under the modeled contact but does not open.
Gate contact + camera: Deliberate physical boundary testing, independent of the air observations.
A separate control anomaly
The local controller records unauthorized remote requests as denied. Local command authority and equipment power remain on. No remote request is shown operating a transformer.
Local controller: Remote requests denied; local command authority retained.
Contributions corroborate the physical tracks
The ground camera and proposed thermal aperture contribute boundary observations; no thermal image of a person is shown. Two pitched sky heads contribute distinct western and eastern aerial views. Concurrence alone does not identify a common organizer.
Camera / proposed thermal: Ground contact observations within partial illustrated sectors.
Aimed air sensing: Two independent aerial trajectories; no calibrated range or classification claim.
An independent eastern approach
The ochre hexarotor approaches on the eastern track. A separate pitched sky head contributes this view; neither image proves who coordinates the actors.
Eastern sky camera: Six-rotor silhouette and independent eastern route.
The remote link becomes unavailable
The physical node shows UNAVAILABLE and LOCAL ONLY while its local-power rail stays lit. The outage is another observation; the scene does not attribute it to any actor.
Remote link + local node: Remote service unavailable; local inputs remain on.
Local evidence supports a protective hold
Proposed on-site correlation links concurrent ground contact, aerial tracks and denied requests. Preauthorized local alerts and an inner-access hold activate. Observations are queued at the node despite the lost remote link. Equipment remains powered.
Proposed on-site correlation: Ground, air and controller observations combined for local review.
Preauthorized policy: Local beacon/hold cue; remote commands remain isolated.
Attribution: Coordination is authored ground truth, not proof of an organizer from sensor observations.
The operator authorizes local protection
The operator reviews the concurrent ground, air and denied-control observations, directs the technician to shelter and the guard to a protected standoff, and keeps remote commands isolated. The later inspection is authorized only after both hostile tracks clear the corridor. This illustrative sequence advances automatically.
Illustrative decision: The operator authorizes staff protection and a later local inspection.
Current state: The operator completes the local review; the defender remains docked.
Inspection condition: Human approval and a clear air corridor are both required.
Staff carry out the local decision
The technician withdraws along the apron toward shelter. The guard uses a separate inside-fence route to a protected warning position. The operator keeps local command authority; no electrical shutdown occurs.
Authorized ground response: Separate technician, guard and operator tasks begin after approval.
The work area clears
The technician reaches the shelter. The operator touches the local hold control; the inner barrier then closes across the now-clear access. The guard remains ahead of it, inside the outer fence.
Staff + physical control: Shelter arrival precedes barrier closure.
Inner access secured
The inner barrier is down. The guard gives a visible warning from inside the closed outer gate, with a tablet and radio supporting the local check.
Local protective posture: Staff sheltered, inner access held, guard at protected standoff.
The ground pair withdraw
Following the protective posture and warning, the ground actors turn away and leave along the outer approach. Their withdrawal is scripted; the scene makes no claim that software forces it.
Ground camera: Two separate actors visibly turn and depart.
Two separate air departures
The dark quadrotor departs westward and the ochre hexarotor takes a different eastern route. No RF takeover, forced landing or cyber-to-air actuation is shown.
Independent air tracks: Both hostile aircraft make visible departure turns.
The western aircraft departs
The dark quadrotor turns and moves westward away from the yard. This is a scripted departure, not a forced flight-control response.
Western air track: Westward departure with visible motion against the foothills.
The eastern aircraft takes another route
The ochre hexarotor leaves along a separate eastern route. The white inspection aircraft remains docked until this second corridor has cleared.
Eastern air track: Separate departure; defender still parked.
The local flight corridor clears
Both hostile tracks have left the inspection corridor. Ground actors have departed the service gate. The approved defender can now begin its boundary inspection; remote service is still unavailable.
Local track state: Corridor clearance precedes dock opening.
The requested inspection begins
The white defender remains supported while the two dock covers slide clear. Rotor spool begins only after the covers have opened.
Approved dock sequence: Opening before spool and takeoff.
Lift into the clear side corridor
With rotors powered and covers clear, the defender lifts vertically beside the yard, away from people and energized equipment. It has no counter-drone role.
Proposed inspection aircraft: Takeoff follows approval and corridor clearance.
Along the safe side route
The aircraft translates along the outside of the eastern fence. Its gimbal is aimed toward boundary geometry rather than faces.
Aircraft + gimbal: Independent inspection route outside the work area.
Inspect the gap in ground coverage
The defender holds a lateral view of the outer boundary geometry. This supplies a view missing from the fixed ground sector; the guard performs the complementary ground check.
Proposed local inspection: Additional sight line at the boundary; no complete-coverage claim.
Return with the local observation
The requested inspection is complete. The aircraft follows its clear side corridor back toward the open dock while the inner access remains held.
Inspection flight: Return begins; protective ground posture remains.
Back over the open dock
The defender descends vertically above its pad. Rotor power stays on during descent and the covers remain open.
Dock approach: No closure before supported touchdown.
Supported touchdown
Both skids settle onto the pad. Rotor rundown begins with the aircraft supported; the covers wait.
Pad contact: Landing before power-down.
Rotors stop before closure
Rundown completes on the pad. The split covers then close above the stationary aircraft.
Dock sequence: Stationary rotors before cover motion.
Inspection aircraft secured
The defender is parked under the closed dock. The guard maintains the local check and the inner work area stays protected.
Local response record: Complete dock-to-dock cycle.
Connected again; ready to sync
The physical node shows CONNECTED and READY TO SYNC. Queued observations remain locally available. Link restoration does not settle attribution or authorize remote control.
Node + connection state: Remote connection restored; local power never changed.
A protected site, an unresolved investigation
In this authored sequence, the ground pair and both hostile aircraft have departed, the technician is sheltered, inner access is held and local inspection is complete. Denied requests and the ready-to-sync record remain distinct. Equipment stayed on; attribution and external investigation remain unresolved.
Local response record: Ground/air departures, inspection complete and inner hold recorded.
Control + connection record: Requests denied; remote link available; record ready to sync.
Illustration boundary: No measured prevention, downtime, endurance or all-clear claim.