Interrupt vs ambient-HUD vs hold-for-briefing arbitration

Decides whether to interrupt, show quietly on the HUD, or hold for the briefing.

TESTED , rung 3 of 8 Recorded 8 September 2026

Technical

What it is

Interrupt vs ambient-HUD vs hold-for-briefing arbitration.

Truth ladder

Rung 3 of 8: TESTED

Automated tests exercise it in isolation, often against fixtures.

Project record: NOT_PROBED_THIS_PASS

CONCEPT Designed or specified. No working code yet.
IMPLEMENTED Code exists. Nothing has demonstrated that it behaves correctly.
TESTED Automated tests exercise it in isolation, often against fixtures.
INTEGRATED Wired into the rest of JARVIS and tested across component boundaries.
PRODUCTION-REACHABLE The owner can reach it through the real runtime path, not only through a test harness.
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.
FORMALLY VERIFIED Its critical property is checked by a proof or exhaustive verification.
RELEASE-QUALIFIED Passed every qualification gate for a named release.

Limits

Last passing probe is older than the 24-hour window (state set 2026-09-08); the registry labels it NOT_PROBED_THIS_PASS rather than carrying a stale LIVE.

Record

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

Neighbours