JARVISLabs

Print readiness (READY / NOT READY / WHY)

Before anything could reach a printer, JARVIS checks mesh, size, bed fit, orientation, supports, slice, profiles and revision, and answers READY, NOT READY or WHY.

LIVE-PROVEN Recorded 23 September 2026. Advanced Systems branch, not merged into production.

Technical

What it is

jarvis/fabrication/readiness.py: mesh validity, dimensions, bed fit, orientation, supports, slice, profiles, revision, displayed identity.

Truth ladder

Where it stands

Rung 6 of 8: 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.

Project record: COMPLETE/FULL, PRODUCTION_REACHABLE, canonical live proof (20 atoms complete)

  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

  • Readiness is software readiness only: JARVIS has never started a physical print, and the final send still refuses by design.
  • Unknown checks never count as passed, and owner approval is still required for any handoff.
  • Proven on an isolated diagnostic core with synthetic test fixtures, not on the owner’s everyday runtime.

Record

Status history

  1. TESTED Recorded state: lane-tested only; canonical review REPAIR_REQUIRED_BEFORE_CANONICAL_ACCEPTANCE; matrix UNDISPOSITIONED
  2. LIVE-PROVEN Canonical three-boot proof with a real slicer: READY in 0.125 s, receipts identical after restart, NOT VALID after a CAD revision change, NOT READY when the real slicer rejected a part. No printer was contacted.

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

Connected work

Connected work

Neighbours

Related capabilities