JARVISLabs

Screen regions tied to real UI/DOM elements

Screen regions tied to real UI/DOM elements.

TESTED Recorded 19 September 2026

Technical

What it is

Bounded UIA/DOM regions and fresh semantic actions (jarvis/perception/screen.py, targeting.py).

Truth ladder

Where it stands

Rung 3 of 8: TESTED

Automated tests exercise it in isolation, often against fixtures.

Project record: IMPLEMENTED (body state, CURRENT_BODY_EVIDENCE_MATRIX.md 2026-09-19 @23f2f945); ledger row status IN_PROGRESS

  1. CONCEPT Designed or specified. No working code yet.
  2. IMPLEMENTED Code exists. Nothing has demonstrated that it behaves correctly.
  3. TESTED Automated tests exercise it in isolation, often against fixtures.
  4. INTEGRATED Wired into the rest of JARVIS and tested across component boundaries.
  5. PRODUCTION-REACHABLE The owner can reach it through the real runtime path, not only through a test harness.
  6. LIVE-PROVEN A bounded probe ran the real code path on a booted JARVIS on the real machine and recorded evidence. The project treats live evidence as expiring after 24 hours, so every live reading here shows the date it was taken.
  7. FORMALLY VERIFIED Its critical property is checked by a proof or exhaustive verification.
  8. RELEASE-QUALIFIED Passed every qualification gate for a named release.

Limits

Limitations

  • Generic invoke without an independent application-goal postcondition stays UNVERIFIED. Focused tests and integrated code, not a release qualification; the formal post-LM row remains open unless noted.

Record

Status history

  1. TESTED Recorded state: IMPLEMENTED (body state, CURRENT_BODY_EVIDENCE_MATRIX.md 2026-09-19 @23f2f945); ledger row status IN_PROGRESS

Only states recorded in the public export are listed. Earlier states may exist in the project’s private ledgers.

Connected work

Connected work

Neighbours

Related capabilities