Build history

A system assembled as contracts, not vibes.

The public history focuses on architectural lanes and verification posture. It avoids live-private metrics while showing how the project became a governed cognitive substrate.

01

Two-device runtime

Pi senses and desktop brain split stabilized around local WebSocket transport and thin-sensor design.

02

Epistemic immune system

Capability gate, attribution, provenance, identity boundary, contradictions, calibration, graph, quarantine, audit, soul integrity, compaction, and intention truth shipped as layered contracts.

03

Capability acquisition

Parent acquisition jobs coordinate research, planning, implementation, plugin quarantine, verification, skill registration, and truth recording.

04

Self-improvement governance

Stage 0/1/2 self-improvement, sandbox validation, pending approvals, atomic apply, supervisor rollback, and CoderServer integration landed.

05

Synthetic lanes

Synthetic perception, claim, and commitment exercises create growth data without contaminating lived memory, identity, or conversation history.

06

Oracle Benchmark

Eval sidecar matured into PVL contracts, scorecards, hard-fail gates, evidence provenance, and Oracle seal levels.

07

HRR research

Holographic cognition and spatial mental-world lanes exist as shadow/advisory research with zero-authority governance.

Release framing

Architecturally complete, runtime maturing.

That phrase is the honesty anchor. JARVIS has the core components wired; each instance still earns trust, identity, memory quality, and autonomy through lived runtime evidence.