Acceptance, validation, dependencies
OPEN-SOURCE FLAGSHIP / HARNESS
Make long-horizon agent work bounded, inspectable, and resumable.
Meta Harness turns a large implementation specification into dependency-ordered phases and slices, bounded worker packets, validation gates, proof ledgers, checkpoints, and an explicit next action.
Repository ↗PINNED SOURCE / 45034762b88d
01 / EXECUTION CHAMBER
The protocol is the product.
This walkthrough is derived from actual schemas and checked-in examples. It is not a live agent or fabricated success demonstration.
INTERACTIVE PROTOCOL WALKTHROUGH
Execution Chamber
Static simulation from real repository examples. No coding agent is running in this browser.
docs/implementation_spec.md
REQ-001 and REQ-002 enter the phase compiler.02 / CONTRACT SURFACES
Every handoff carries state and proof.
The same contracts support CLI, MCP, adapter, skill, and instruction-emitter surfaces.
Scope, owner, evidence requirements
Changed files, outputs, risks
Claims linked to evidence paths
Durable state and carry-forward risk
Continue, review, stop, or block
BOUNDARY CONDITIONS
Pre-1.0. Source-installed. Read-only first.
- Adapter support varies.
- Fake-adapter simulation is not command-verified release proof.
- The harness does not guarantee correctness or autonomy.
- External side effects require explicit approval.
Independent of the 2026 paper with a similar “Meta-Harness” title unless repository history establishes otherwise.