Human hold, return, or land overrides dominate autonomy
BOUNDED AUTONOMOUS INSPECTION
NATIVE WEBGL / WEBXR
Interactive spatial model
Select a nodeUse the node list or interact with the scene.
DERIVED RESULT
Condition record and proof
PROOF CHECKS PASS
The deterministic result proves the declared synthetic software behavior for this input. It does not certify a real system or establish legal liability.
Missing critical gates cannot produce an inspection state
{"authority current": true, "battery margin at or above 20 percent": true, "environmental uncertainty at or below abstention boundary": true, "human supervision available": true, "navigation integrity established": true, "separation assurance available": true, "software and configuration attested": true, "synthetic safety volume valid": true}
Only normalized synthetic coordinates are emitted
SYNTHETIC_NORMALIZED_SCENE_UNITS
No hardware or flight-control protocol exists
Hardware interface NONE; protocol list empty
No target, payload, weapon, or force function exists
All prohibited output classes are false
Control-state history is append-oriented and hash-addressed
f4ccd8f30961ca4a0c2af2feeb25d6c80975271b5fde4f3cdd7d4f1bdb02575d
Every derived state terminates at the synthetic null sink
Derived state recorded; no external command channel exists
EQUIVALENT REPRESENTATIONS
Visual, table, and text views
Spatial arrangement
The scene contains three fictional inspection drones, three abstract inspection volumes, a bounded authority artifact, a human supervisor, a normalized safety volume, a base, an append-oriented control-state ledger, and a synthetic null sink. Controls request only high-level standby, inspection, hold, return, or land states. No real aircraft or geographic control is possible.
The 3D scene is an additional representation. The table and text below contain the authoritative accessible state.
| Node | Type | State | Detail | Position |
|---|---|---|---|---|
| Bounded authority artifact | authority | supported | Authority current | -3.6, 2.1, -2.2 |
| Human supervisor | human | supported | Operator command: start inspection | 3.6, 2.1, -2.2 |
| Normalized safety volume | geofence | supported | Normalized safety volume established | 0, 0.2, 0 |
| Synthetic drone base | drone-base | qualified | Fleet state: INSPECT | 0, -2.15, -2.6 |
| Inspection Drone A | drone | supported | Inspecting a predeclared infrastructure inspection path at 40% synthetic progress | -2.36, -0.43, -0.38 |
| Inspection Drone B | drone | supported | Inspecting a predeclared infrastructure inspection path at 40% synthetic progress | 0.0, -0.09, -0.24 |
| Inspection Drone C | drone | supported | Inspecting a predeclared infrastructure inspection path at 40% synthetic progress | 2.36, -0.43, -0.38 |
| Inspection Volume A | inspection-zone | supported | Predeclared fictional inspection volume | -2.6, 1.1, 2.2 |
| Inspection Volume B | inspection-zone | supported | Predeclared fictional inspection volume | 0, 1.8, 2.7 |
| Inspection Volume C | inspection-zone | supported | Predeclared fictional inspection volume | 2.6, 1.1, 2.2 |
| Control-state ledger | provenance | supported | 3 append-oriented transition records | -1.4, -1.9, 1.7 |
| Synthetic null sink | null-sink | safe | No command leaves the synthetic null sink | 1.4, -1.9, 1.7 |
| From | Relationship | To |
|---|---|---|
| authority | delegates | drone-a |
| authority | delegates | drone-b |
| authority | delegates | drone-c |
| human | supervises | drone-a |
| human | supervises | drone-b |
| human | supervises | drone-c |
| base | stages | drone-a |
| base | stages | drone-b |
| base | stages | drone-c |
| drone-a | predeclared_path | zone-a |
| drone-b | predeclared_path | zone-b |
| drone-c | predeclared_path | zone-c |
| drone-a | records_state | provenance |
| drone-b | records_state | provenance |
| drone-c | records_state | provenance |
| provenance | derived_output_only | sink |
Text description
The scene contains three fictional inspection drones, three abstract inspection volumes, a bounded authority artifact, a human supervisor, a normalized safety volume, a base, an append-oriented control-state ledger, and a synthetic null sink. Controls request only high-level standby, inspection, hold, return, or land states. No real aircraft or geographic control is possible.
Declared proof invariants
- human hold, return, or land commands dominate bounded autonomy
- missing authority, invalid navigation, geofence failure, low battery, excessive uncertainty, or missing separation assurance cannot produce an inspection state
- only normalized synthetic scene coordinates are emitted
- the engine exposes no hardware interface, flight protocol, payload control, target selection, or weapon function
- control-state history is append-oriented and hash-addressed
SYNTHETIC TECHNOLOGY DEMONSTRATION — This scene uses a fictional three-drone inspection fleet, normalized coordinates, predeclared scene paths, high-level safety states, and a synthetic null sink. It has no connection to real aircraft, no MAVLink or vendor flight protocol, no GPS coordinates, no target selection, no payload control, no weapon function, and no operational command authority.
SOURCE REPORTS
Research used to implement this scene
DOC Autonomous C2 Simulation Architecture →DOC Autonomous Delegation Architecture Research →DOC Autonomous System Assurance Platform →DOC Autonomous System Defensive Architecture →DOC Autonomous Systems Uncertainty Architecture →DOC Decision Provenance System Architecture →DOC Human Judgment Interface Design →DOC Synthetic Kill Web Simulator Architecture →
Open the complete drone-control implementation record →
Open the complete report-to-software traceability matrix →