Skip to main content
Patriot Web Solutions

Public & inspectableRe-verified 2026-09-16

Hive Mind OS

Don’t trust your coding agent — verify it. Hive Mind OS produces a tamper-evident receipt bundle proving what an AI agent actually did: the commands it ran, their exit codes, the diff it produced, and whether an independently sealed check passed.

What it is

A verification framework for AI coding agents. Instead of trusting an agent’s summary of its own work, Hive Mind OS re-executes sealed checks in a separate workspace and writes a receipt bundle: a patch, a manifest, a validated receipt store, and a machine-readable mission report.

Why it exists

CI runs after you have already decided to trust a change, and agent frameworks orchestrate work but prove nothing. The missing piece is evidence produced independently of the agent being judged — that is the piece this project builds.

How it connects to the classroom

This is the discipline our classes teach: claims carry checks. The framework is the working example learners can open, run offline, and argue with — the demo command builds a small repository with a known regression, repairs it, and writes the receipt bundle where you can read it.

What to look at first

  • README — the status table states exactly what works and what is not ready, before any pitch.
  • docs/ACCEPTANCE_SPECIFICATION_GUIDE.md — field-by-field guidance for writing a sealed acceptance specification.
  • examples/verify-an-agent-change — a complete offline walkthrough from agent-authored patch to inspected receipt bundle.
  • docs/architecture/ — the courtroom synthesis and hardened vision contract: decisions, dissent, and evidence burdens.
hive-mind verify 
  --repository /path/to/local/repository 
  --spec /path/to/acceptance-spec.json 
  --output /path/to/absent/receipt-bundle
  1. The acceptance spec is sealed before the candidate change exists, so the test cannot be bent to fit the answer.
  2. The spec must declare every path the commit touches; an undeclared change fails validation.
  3. A failed validation publishes no receipt bundle — no evidence, no claim.
The verify command from the Hive Mind OS README, captured 2026-09-15 at revision 20a7ea2 and re-read unchanged on 2026-09-16.

Status: public and inspectable — see the ledger (checked 2026-09-16).