The project

About the project

JARVIS is one person’s long-running project to build a capable personal AI system that runs on their own computer and has to show evidence for what it does.

What JARVIS is

JARVIS is a locally hosted assistant for a single owner. It holds conversations by voice and text, keeps layered memory with provenance, operates Windows applications and the browser, runs engineering calculations and CAD operations, prepares 3D prints, runs long missions and shows its state on a single HUD. Every effect it has on the computer passes through one governance kernel: an emergency stop, a fail-closed policy engine, owner approvals for risky actions, and an independent check of what actually happened.

The idea of a highly capable personal assistant is an old one, and the name nods to it. The system, its design and this site are original work and are not affiliated with any film studio or franchise.

Why it is built this way

Most assistants report success when a command was sent. JARVIS is built around the opposite rule: a dispatched command is not a verified effect, a passing test is not a live capability, and a calculation is not a measurement. That discipline shows up everywhere, from the receipts on every action to the way this site labels every number with its date and evidence type.

How it has been built

The earliest dated artefact is from 17 April 2024: a small voice prototype. The current production branch has 3,272 commits since July 2026, with a test suite larger than the runtime itself. Much of the code has been written with AI coding assistants working under written build orders, ledgers and gates that the owner defines; the owner decides what gets built and what counts as proven. The evolution timeline shows the path, including the gaps.

What this website is, and is not

  • It is the public engineering record: capabilities, benchmarks, history, demos, a journal and a place for suggestions.
  • It is not JARVIS. It has no connection to the owner’s computer, and nothing here can send commands to JARVIS, read its memory or see its screen.
  • Its data is a reviewed export, refreshed by hand. It is never live telemetry.

Contact

The best way to reach the project is the feature request lab. Requests are read by the owner. For privacy questions, see the privacy notice.

Progress is posted as it happens on X: follow @CampbellKaleb23 for new demos, bench results and what is being built next.