_{AGENTS  ·  EVIDENCE  ·  MEMORY  ·  PROTOCOL  ·  CONTINUITY}

_{spec-driven  ·  wave-driven  ·  lane-isolated}

_{English  ·  Português (Brasil)}

_{Project site  ·  the catalogue, the manual and the design system, rendered}

House Party Protocol

Operate coding agents under evidence, not trust.

House Party Protocol (HPP) is a local-first harness for coding agents. It sits around the work an agent does in Claude Code or Codex CLI and turns four questions into executable contracts: what may run, who may approve, what counts as proof, and where the next step comes from after an interruption. The order of work is not negotiated in the conversation: a spec compiles into a WorkGraph, the graph runs in topological waves, parallel sessions work in isolated lanes, and every wave closes on evidence, never on a sentence.

The harness is a Python package with no runtime dependencies (python -m hpp), a manifest that declares the protocol, a set of installable modules, and one distribution channel per host. Nothing runs in the background. Every verdict it produces can be re-derived from files on disk.

The problem

An agent says "done". The sentence is fluent, the diff looks plausible, and nothing checked it. The tests it reports may have run against a stale checkout, or may not have run at all; text in a transcript is not an exit code. The approval a reviewer gave yesterday still reads "approved" this morning, after the spec changed and three files moved. Nobody re-opened it, because nothing tied the approval to the bytes it approved.

Two sessions share one repository. One rewrites a module while the other reviews it; the review lands on a version that no longer exists. Or the agent that wrote the code is the one that reviews it, with the same blind spots and a pen in hand: it "fixes and proceeds", and the defect in the process never surfaces. A lock left by a session that died at 3 a.m. blocks every other session at 9, because a stale lock and a live one look identical.

Then the failures that lie by being technically correct. A service answers 200 while its data is from Tuesday. A signal stamped in the future is reported as fresh. A counter returns zero because the pattern never matched, and zero is read as "no problems". A loop takes "one more iteration" past its budget. A summary restored after a crash is treated as a to-do list, so a finished step runs again and overwrites its own result. None of these raise an error. That is what makes them expensive.

How the harness responds

Each failure above has a mechanism in the code, and each mechanism has a command that shows it.

Cross-model by construction

The harness never assumes one brain. Two independent mechanisms, neither of which names a model:

Two honesties about that last row. The route it returns DOES name a provider — {'provider': ..., 'tier': ...} — but only one that you listed in the request: the harness never chooses a vendor you did not declare, never ranks them, and never reads a price. And the shell a checker needs to inspect is a promise, not a capability: Write and Edit are absent by configuration, while Bash is constrained by instruction, so where that matters the working tree is captured before and after the review and compared — a checker that touched it invalidates its own findings (rules/loop-maker-checker.md).

Hosts today are Claude Code and Codex CLI: same protocol, same exit codes, same maps. A lane driven by one and reviewed from the other is the ordinary case, not an integration project.

Those three rows are a state machine, not a convention. lane-kit keeps one append-only board per repository and is its only writer: CHECKPOINT-READY only from the lane that claimed the item and only with evidence pasted in, a verdict only from another lane and another model family, DEFERRED the only verdict an unreachable checker can produce, and MERGED only on top of a VERIFIED that is already on the board.

_{The board those rows produce, as multi-session/lane-kit-1.4.1/scripts/lane_board.py prints it: four example items driven through the machine, every event naming the lane that wrote it, the evidence pasted at checkpoint, and — for a verdict — the lane and the model that gave it. Two attempts were refused on the way there, both exit 1: a verdict from the builder's own lane (maker≠checker violated: reviewer (exec-b) is the SAME lane as the builder) and merging a 🔴 item without --human-approved. The last block is the one nobody thinks to ask for — verdicts already decided whose lane has not been told. Text rendered from the command's real stdout by scripts/render_terminal_svg.py, like the two captures above.}

Quickstart

Requirements: Python 3.10 or newer (pyproject.toml), git on PATH for attestation, no third-party packages. CI exercises Python 3.10 to 3.13 on Linux, macOS and Windows (.github/workflows/ci.yml); older interpreters are not promised because nothing measures them.

pip install git+https://github.com/rusharlabs/house-party-protocol@v2.7.0
hpp doctor
hpp init --target ../your-repo

From 2.6.5 on, every release is also published to PyPI by the release workflow, with no stored token: pip install house-party-protocol==<version> installs the same wheel.

Installing with an agent? Paste this URL at it and say to follow it: https://raw.githubusercontent.com/rusharlabs/house-party-protocol/main/INSTALL_FOR_AGENTS.md

INSTALL_FOR_AGENTS.md is written for the agent, not for you: it detects the host, checks the preconditions instead of assuming them, and requires the agent to read hpp init's plan to you before a single file is written.

_{The two commands as they print from a clone of this repository. Both images are text rendered from the real output by scripts/render_terminal_svg.py; regenerate them after any change to the wizard.}

The package has no runtime dependencies and ships its own manifest and benchmark suite, so hpp — including hpp benchmark and hpp --self-test — answers from any directory once installed (pipx install git+… works the same way). From a checkout, the CLI is the module:

git clone https://github.com/rusharlabs/house-party-protocol.git
cd house-party-protocol
python -m hpp doctor

hpp init runs six fixed stages and prints a plan. Each boot line completes only when its stage has finished; readiness counts checks that ran, and each item carries the command that reproduces it. What it can verify depends on where hpp runs. This repository is the emitted distribution — harness, manifest, the ten module directories with their CHECKSUMS.txt, marketplace.json and the module installer — and from a clone of it, against an empty target (python -m hpp init --target <empty-dir> --non-interactive --no-animation), the output is:

> detecting host...           ✓ greenfield · 0 existing item(s) preserved
> checking prerequisites...   ✓ python 3.14.3 · protocol 2.1
> mounting profile...         ✓ would-write · host=claude-code · bundle=reliable-coding · policy=audit · 3 default(s)
> loading modules...          ✓ 6 modules · reliable-coding · claude-code · 6/6 checksums verified
> wiring suggestions...       ✓ 7 commands to paste · 0 files written · 17 hooks declaring capabilities
> verifying evidence...       ✓ policy · graph · events · benchmark
> protocol online.

  READINESS  every line is a check that ran; the command below it reproduces it
  ████████████████░░░░  9/11 verified · 2 not verified · 0 failed

The two items not verified are the two that only a later action can prove: the profile (plan only; --apply writes it) and the host wiring (a paste you do yourself). The pip install is a different channel: the wheel carries the harness, the manifest and the benchmark suite, but no module directories and no marketplace.json. The same command from that install, on the same empty target, reads:

> detecting host...           ✓ greenfield · 0 existing item(s) preserved
> checking prerequisites...   ✓ python 3.14.3 · protocol 2.1
> mounting profile...         ✓ would-write · host=claude-code · bundle=reliable-coding · policy=audit · 3 default(s)
> loading modules...          ✓ 6 modules · reliable-coding · claude-code
> wiring suggestions...       ✓ 7 commands to paste · 0 files written · 17 hooks declaring capabilities
> verifying evidence...       ✓ policy · graph · events · benchmark
> protocol online.

  READINESS  every line is a check that ran; the command below it reproduces it
  █████████████░░░░░░░  7/11 verified · 4 not verified · 0 failed

The two extra items there — distribution integrity and module checksums — are reported as not verified because there is nothing to measure them against, never as passed. In either channel nothing is written until you re-run with --apply, and then exactly one file is written: .hpp/profile.json. hpp init --json gives the same report as JSON for CI and agents; --non-interactive, --yes and --profile answer the questions without a prompt. The fourth question is optional and new in 2.6.0: --decision-advisor off|typesafe|openrouter|compatible records a typed-decision advisor you will integrate yourself (default off) and prints how — see examples/typed-decisions.

After --apply, paste the wire block the command printed. For Claude Code that is the native plugin channel:

/plugin marketplace add rusharlabs/house-party-protocol
/plugin install operator-kit@house-party-protocol

For Codex CLI the module installer copies each module into .agents/hpp/<module> and runs its declared smokes. On Claude Code, a module without a plugin hook is copied by hand (each module's README shows the cp -r line) and the installer detects, wires and verifies it. Either way it plans first and applies only on a second, explicit invocation:

python installers/kit-forge-1.4.2/kit_doctor.py install \
  --kit frameworks/operator-kit-1.6.2 --host codex --target ../your-repo
python installers/kit-forge-1.4.2/kit_doctor.py install \
  --kit frameworks/operator-kit-1.6.2 --host codex --target ../your-repo --apply

The installer is part of this repository, at installers/kit-forge-1.4.2/kit_doctor.py, next to the module directories it installs from. A pip install carries neither, and hpp init says so in its wire block when it cannot find the installer beside the manifest. hpp install --bundle reliable-coding --host codex --target ../your-repo is a different command: it prints a receipt with "mode": "plan-only" and copies nothing.

Harness, protocol, modules, distribution

The product is layered, and the layers are not interchangeable.

harness        python -m hpp          the operating surface: doctor, init, event log,
                                      attestation, maps, WorkGraph, policy, routing, eval,
                                      decision records, evidence bundles, retrieval eval,
                                      citation check, House Session
   │
protocol       hpp.manifest.json      the invariants: roles, loop transitions and gates,
                                      exit codes, host coverage, monitors, bundles
   │
modules        ten versioned dirs     installable capabilities; each stands alone
   │
distribution   marketplace · copy     Claude Code plugin channel · Codex CLI verified copy

hpp doctor validates the manifest and, when marketplace.json sits beside it, cross-checks every module path, version and plugin manifest. In this repository it prints HPP doctor: ok · modules=10 · hosts=claude-code, codex · hooks=18 (permission gates=9 · llm egress=0); the cross-check is visible only in hpp doctor --json, where distribution reads {"checked": true, "modules": 10, "status": "ok"}. From a pip install the one-line output is the same and the field reads {"checked": false, "status": "source-contract"}, because no marketplace.json sits beside the packaged manifest.

The protocol's loop is five transitions, each behind a named gate:

planned --work_started--> active --evidence_recorded--> evidenced --check_passed--> checked
        [scope]                   [fresh-evidence]                 [read-only-checker]

checked --human_approved--> approved --verified--> verified
        [human]                      [closure]

hpp status projects the event log onto this machine and names the next step; hpp resume returns the same answer as JSON. Neither asks a model to remember anything.

What each module solves

The reliable-coding bundle is the first six. Each module installs on its own; integrates_with in the manifest is optional composition, requires is a hard dependency, and today no module requires another. Host coverage is declared per module as native, explicit-command or unsupported; claude-dev-kit is unsupported on Codex CLI, and hpp init halts rather than plan it there.

Proving an installation

A claim about the harness is accepted only with its command. These are the ones the project runs on itself.

python -m hpp doctor                      # manifest contract; distribution when present
python -m hpp benchmark -k 3              # ten executable controls, three runs each
python -m hpp --self-test                 # capability graph non-empty + benchmark gate
python -m pytest tests -q                 # stdlib-only suite, no network
python -m hpp policy check --mode enforce --command "rm -rf src"   # exit 2, BLOCK
python -m hpp graph --view operational --format json | sha256sum   # same hash on every run

The benchmark's ten controls each execute a real mechanism with a positive and a negative case: manifest contract, policy enforcement, WorkGraph waves, lane collision, monitor freshness, context provenance, routing floor, event/evidence gate, graph determinism and evidence attestation. pass^k = 1.00 is required for the gate to pass. The suite file and its hash are in the JSON report (hpp benchmark -k 3 --json). See PROOF.md for the claim matrix and BENCHMARK.md for the scenarios.

In this repository, python installers/kit-forge-1.4.2/kit_doctor.py verify <module-dir> compares every file of a module against its CHECKSUMS.txt, and python installers/kit-forge-1.4.2/kit_doctor.py marketplace . checks the whole tree.

Honest limits

• HPP is a CLI. There is no daemon, scheduler, queue, server, database or remote telemetry. If a check did not run, nothing ran it.
• HPP never calls a model. Routing returns a tier and a provider id from declarations you pass in; it does not pick a vendor, a model name or a price.
• Maps are projections of manifests, event logs and JSON you provide. The Monitor Map does not probe anything; you supply last_signal. The Lane Map does not know your sessions; you supply heartbeats. --now is explicit so that no projection depends on the ambient clock.
• The context budget is measured in characters, not tokens.
• The policy classifier is a small, explicit rule set (recursive delete in any flag order, force push, push to main/master, curl | sh, DROP/TRUNCATE, and MANUAL for any push or outbound transfer). It never executes the command and it does not claim to catch every destructive form.
• Attestation requires git. It hashes the remote identity and stores the hash, not the URL. It binds a verdict to bytes; it does not judge whether the verdict was right.
• On Claude Code, lifecycle hooks are native once you paste the wiring. On Codex CLI there are no lifecycle hooks; the same capabilities are explicit commands. hpp doctor and the manifest report this as native, explicit-command or unsupported, and no adapter pretends otherwise.
• hpp init writes one file with --apply and never edits settings.json, hooks or AGENTS.md. Enabling hooks remains a human action.
• The benchmark proves the harness on the checkout and platform where it ran. It says nothing about the quality of any model.

Reading order

MANIFESTO.md — what the project defends and refuses · CONCEPTS.md — the vocabulary, with what each term is not · METHOD.md — the working method, one command per practice · ARCHITECTURE.md — how the pieces fit and what deliberately does not exist · GRAPH-MODEL.md · LOOPS.md · BENCHMARK.md · PROOF.md · BRAND.md — the identity · DESIGN.md — the tokens, the components and what a pull request with an interface has to satisfy · TIPS.md · manual · catalogue · CHANGELOG.md · AGENTS.md for agents working in this repository.

Development

Module directories in the distribution are emitted artifacts. Changes start in the sources, get a test that fails before the fix and passes after it, and go through the forge. Before declaring anything done:

python -m pytest tests -q
python -m hpp doctor
python -m hpp benchmark -k 3

License

MIT. Copyright (c) 2026 Max Parisi, Rushar Labs. Any module that carries adapted material keeps the NOTICE file its license requires.