Choose drone tactics from camera-derived state

01 · Role in the system

What Jev does here

Jev reads symbolic scene features derived from onboard depth and segmentation buffers. It chooses a maneuver, scores risk, and estimates whether a target is truly lost. A 50 Hz reflex layer can veto those judgments, while a 500 Hz geometric controller owns flight dynamics; Jev never receives pixels or direct motor control.

02 · Control boundary

Where Jev sits

Classical perception to Choice, Score, and Noul judgments; faster deterministic loops retain safety authority.

Code owns the loop, permissions, thresholds, validation, and side effects. Jev owns only the bounded judgments described above.

03 · Known limits

What this evidence does not prove

• The strongest course result is one simulation run and does not establish a repeatable improvement.
• Perception and safety are separate code paths; the model neither sees camera pixels nor controls motors directly.

04 · Attribution

Public sources

This is a Community record: the project was published by a third-party community author.

• RomanSlack ↗Community · github · public · checked 2026-09-18