JARVISLabs

Machine epistemology court

An internal "court" argues evidence for and against a claim.

IMPLEMENTED Recorded 29 July 2026

Technical

What it is

TRIBUNAL machine-epistemology court with adversarial roles over the claim graph (jarvis/research/tribunal.py).

Truth ladder

Where it stands

Rung 2 of 8: IMPLEMENTED

Code exists. Nothing has demonstrated that it behaves correctly.

Project record: IMPLEMENTED

  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 code and its tests exist, but the project's AUDIT 03 reachability sweep found no production entry point constructing it at the time the state was set (2026-07-29); later post-LM work may have changed this (UNCERTAIN, registry not re-derived).

Record

Status history

  1. IMPLEMENTED Recorded state: IMPLEMENTED

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

Neighbours

Related capabilities