Community · E2 · artifact verified
Drive Android from semantic UI state
A proof-of-concept Android loop stabilizes the screen, builds a short list of valid actions, and lets Jev pick one while code executes it.
01 · Role in the system
What Jev does here
Jev receives a compact semantic description of the current screen together with a small set of pre-validated actions such as tap, go back, wait, or escalate, and answers with one action plus confidence and a probability margin. Coordinates, MCP calls, and invented steps are impossible by construction because the controller maps each answer to a prepared call. Confidence and top-two margin gates decide execution, repeated states trigger escalation, and ranked action pages keep crowded screens from overwhelming the model.
02 · Control boundary
Where Jev sits
Observe-stabilize-normalize loop to one bounded action Choice; code owns UI stabilization, execution, safety gates, escalation, and JSONL traces.
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
- Exercised only against read-only Android Settings navigation on one real device; other apps are unsolved.
- Payments, account changes, and destructive actions are explicitly out of scope, and no benchmark is published.
04 · Attribution
Public sources
This is a Community record: the project was published by a third-party community author.
- Friedjof ↗Community · github · public · checked 2026-09-18