JARVISLabs

Governed browser navigation with negative controls

Open, back, forward and reload verified by an independent observer, with three negative controls proving that disallowed addresses sent no requests at all.

INTEGRATED Recorded 23 September 2026. Advanced Systems branch, not merged into production.

Technical

What it is

Five requests on an allowed qualification origin; 0 requests for a non-allowlisted loopback server, localhost on the allowed port, and IPv6 loopback; after a restart without the allowance the same open was refused. Production still refuses every loopback target.

Truth ladder

Where it stands

Rung 4 of 8: INTEGRATED

Wired into the rest of JARVIS and tested across component boundaries.

Project record: Adopted into canonical; live proof on the lane

  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

  • The core’s own receipt said completed-unverified; the VERIFIED verdict came from the independent observer.
  • DNS rebinding protection is still open.

Record

Status history

  1. INTEGRATED First published state.

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