42 Quantum
In development

Software Production Suite

Project name: The Hitchhiker's Guide (HHG)

01The research goal

The research goal: can one platform let a person with an idea and no engineering department ship software at the standard a large one would? Big organizations get quality from headcount, review layers, and internal libraries. This project tests whether an AI build environment, a vetted module library, and enforced quality gates can do the same job for one person.

It is the largest project in the lab and the one the others feed. The orchestration engine runs the AI that builds inside it. The knowledge graph tells a builder what already exists so nothing gets rebuilt.

02How it works

The platform is organized as rooms, each one a working surface: a build environment with an integrated editor and AI assistant, a module library where vetted work is reused instead of rewritten, a research library connected to arXiv, Semantic Scholar, OpenAlex, and PubMed, a task system with typed work contracts, a collaboration space, and a five gate quality pipeline covering build, test, security, compliance, and human review.

Payment is the other half of the experiment. A bounty economy lets a founder with no cash offer shares instead, with contracts that convert to real equity on reviewer sign off. The lab runs its own development through this system, so the first user is us.

Built so far: the working prototype with a 161 table schema, around 100 API routes, the task and share contract system running end to end, GitHub ingestion, and the research library connectors.

In action

What it looks like running

Captured from a working install. Hover a numbered callout, or tab to it, to read what that part of the screen does.

Crucible · Build stage

Crucible's Build stage on the radar_sim project: the agent's conversation on the left, the checkout's file tree, a Python file open in the editor, and the run timeline along the bottom.
A project open in Crucible. The agent has read the code, the editor shows the file it is working in, and every run sits on the timeline underneath.

Crucible · System lens

The System lens in Crucible showing a SysML model of HHG itself: the model tree, a level-one structure diagram, a generated legend and the validation panel.
The same project seen as a system model. HHG modelled in its own System lens: parts, interfaces and requirements on the left, the structure diagram in the middle, validation on the right.

The surfaces

4 instruments, one discipline

Workspace

Where you build.

The AI-native build environment, editor, tooling, and assistant in one place.

Crucible

Where it is verified.

Two-stage quality and security gate, mapped against recognised standards.

Greenhouse

Where it grows.

Project incubation and the module library everything is assembled from.

Bounties

Where it gets paid.

Cash or share-backed contracts, vesting on reviewer sign-off.

Sub-project

Sub-project of The Hitchhiker's Guide (HHG)v0.3.3

Desktop Bridge

Project name: HHG-Bridge

Desktop Engine Supervisor & Approvals

HHG runs in the browser; the work it directs happens on a computer. The Bridge is that computer's side of the conversation: a small Windows tray app that supervises the orchestration engine, answers local confirmations before anything runs, finds and starts local model servers, and brings runs, tasks, approvals and notifications to the desktop.

Lines of code
37,738Lines of code
Commits
41Commits
Files
145Files
Building since
Oct 2026Building since
  • Rust
  • Tauri 2
  • React
  • TypeScript

Working today

  • Runs and supervises the orchestration engine, with no terminal open
  • Finds any local model server on the machine and starts it from the app
  • Local approvals and a per-event notification matrix, delivered on the desktop
  • Game mode: scans the PC for games and keeps the GPU free while one is running

HHG-Bridge · Overview

The HHG-Bridge desktop app's Overview page: engine state, the link to HHG, the coordinator model, model hosts found on the machine, and live RAM and VRAM meters.
The Bridge on a Windows desktop, paired to a local HHG. It is watching an engine, holding the link open, and reading every model server on the machine every two seconds.

What the lab built

  • Nine working rooms: Workspace, Crucible, Greenhouse, Library, Tasks, Babble, QA, Telemetry, Bounties
  • The Crucible, a two-stage quality gate mapping code against ISO, OWASP, HIPAA, PCI DSS, FedRAMP, NIST and GDPR
  • Share-backed bounty contracts that vest real equity on reviewer sign-off
  • Passive translation: messages translate when read rather than when sent
Lines of code
249,145Lines of code
Commits
248Commits
Files
1,382Files
Building since
Apr 2026Building since
  • Next.js
  • TypeScript
  • Turso
  • Drizzle
  • NextAuth
  • Vercel

At a glance

How the system flows

  1. 01

    Design

    A goal argued down into buildable parts

  2. 02

    Build

    The AI build environment

  3. 03

    Vet

    Five quality gates, then human review

  4. 04

    Publish

    Vetted work enters the module library

  5. 05

    Reuse

    The next builder starts from it instead of from zero