JARVISLabs

Grounded “no record” answers (persona policy 2.1.0)

JARVIS may only say it has “no record” of something after a search it actually ran in the same turn. This removes an old example that taught it to claim checks it never made.

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

Technical

What it is

Policy 2.1.0 replaces a 2.0.0 example answer that described an inspection that had not happened.

Truth ladder

Where it stands

Rung 3 of 8: TESTED

Automated tests exercise it in isolation, often against fixtures.

Project record: TESTED in canonical (521 passed), INACTIVE: the active policy is still 2.0.0

  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

  • Landed but inactive: turning it on belongs to the language-model owner, together with contract v2.

Record

Status history

  1. TESTED First published state.

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

Connected work

Connected work