buildroom

Filesystem-backed contract chain for Auto-think / Auto-build, piloted 2026-11-14. Pattern source: @gkisokay buildroom guide. Roles mapped onto the Hermes stack:

Buildroom role Here
Research / Dreamer nightly cron buildroom-dreamer (writes candidate contracts)
Main (approval gate) Hermione, interactively — buildroom.py approve/reject
Coder Hermes subagent (delegate_task), bounded by product-plan
QA separate Hermes subagent, never trusts the coder receipt
Operator summary buildroom.py summary -> operator/operator-summary.json

Rules (pilot guardrails)

  1. A signal is not a task. Only idea-contract.json enters the pipeline.
  2. The writer of a contract never approves it. Dreamer proposes; Main decides.
  3. Coder builds only inside product-plan allowed_paths / planned_files.
  4. QA re-runs the plan's verification_commands independently.
  5. Nothing is "verified" until verification-delta.json says confirmed.
  6. Every receipt validates against schemas/*.schema.json (python3 buildroom.py validate --all).

Job lifecycle

candidate -> approved/rejected -> planning (product-plan.json) -> built (coder-verification.json + qa-verification.json) -> verified (delta confirmed)

Layout

jobs//{idea-contract,main-review,product-plan,coder-verification,qa-verification,verification-delta}.json operator/operator-summary.json inbox/ staging dir where the dreamer drops contract JSON before init schemas/ pilot subset: 6 schemas (full guide has 12; trust/retention deferred)

S
Description
No description provided
Readme
47 KiB
Languages
Python 100%