JARVISLabs

Model-visible contract v2

A frozen specification for what the language model sees: the body computes simple facts (is this record still valid? is this the current version?) and shows its working, but never hands the model a verdict.

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

Technical

What it is

Derived facts are single comparisons with their operands and authority NONE; fields such as safe_to_replay or proceed are forbidden; whole fields are dropped with one explicit truncation line instead of cutting text mid-token; v1 output stays byte-identical.

Truth ladder

Where it stands

Rung 1 of 8: CONCEPT

Designed or specified. No working code yet.

Project record: FROZEN_SPEC_FOR_IMPLEMENTATION_NOT_ADOPTED

  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

  • A frozen specification: parts are prepared on branches but untested, and nothing is adopted.
  • It comes with its own versioned gate; the old gate is not relaxed.

Record

Status history

  1. CONCEPT 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