Harden participant and map ownership and validate bounded physical flight
This commit is contained in:
@@ -126,3 +126,9 @@ Only a successful negative test enables signed actor-action demand for flight st
|
||||
|
||||
|
||||
Native113557 proves the signed-action hypothesis: both input and rotor signal hold -0.05, the same aircraft reaches a five-second 7–9m hover and lands with two seconds of ground stability. It then fails the immediate post-shutdown check. Inspection found stage7 returned neutral collective0 while the real rotors continued coasting; the next variant holds proven minimum pitch -1 during shutdown and records every landing predicate. No stability, geometry, timeout or damage limit changes. The failed run remains retained.
|
||||
|
||||
## Native autohover and signed-control pass
|
||||
|
||||
[114504](evidence/native-2026-09-19-114504-powered-flight/report.json) passes81 assertions with zero captured errors. Both positive and negative actor-local input/rotor-signal gates pass before autohover is enabled on the exact occupied controller. One normal engine start consumes native fuel; the same aircraft holds7–9m for five seconds, descends and maintains ground contact for two seconds, then passes the engine-off check at approximately-0.063m relative height,0.012m/s speed and0.063rad/s angular speed. Drift stays inside8m and height inside18m. The original autohover flag is restored. Rotors are still coasting at195.5RPM when engine-off is verified; this is not a rotor-stop or sustained parked-aircraft test.
|
||||
|
||||
This qualifies one bounded vertical mechanism, not route travel, operational HQ aircraft, human piloting or multiplayer. The manual113557 run's shutdown failure and114111 repeated-hover timeout remain archived.
|
||||
|
||||
Reference in New Issue
Block a user