Skip to main content

DCP Harness

dcp-harness is a lightweight evidence-producing shell for Auto Research. It wraps Claude Code CLI, controls the agent's external actions, records the run, performs the registered DCP ablations, and writes a Bundle that anyone can check offline with dcp-audit.

The wrapper gives the agent only file tools. Claude's shell, Web, MCP, and subagent tools are disabled. The only external action is a strict JSON file. The harness can execute a task experiment or fetch an allowlisted HTTPS URL, then records the request, raw response, model-visible text, workspace change, model identity, and receipt hashes before starting a fresh model session. Only the main run may use live Web access. Challengers and Gate 3 branches get an exact replay of URLs observed by the main run.

A small task adapter supplies task semantics, private evaluation, baseline, and truthful or neutral experiment feedback. Private scores are opened only after every candidate in a phase has committed. The adapter registers all thresholds and sample counts before the main run. It also supplies SHA-256 digests for the private verifier, held-out units, baseline policy, and feedback policies; these materials are rechecked before every phase. The harness fills mechanical evidence from the frozen ledger, invokes the unchanged dcp-audit kernel, and immediately checks that the resulting Bundle replays exactly.

Quickstart

python -m pip install dcp-harness
dcp-harness init my-audit
# Complete task_adapter.py and configure the model and Docker image first.
dcp-harness doctor --config my-audit/dcp-harness.json
dcp-harness run --config my-audit/dcp-harness.json --run my-audit/run-001
dcp verify my-audit/run-001/bundle

init --force adds missing starter files without overwriting existing files. The commands can also be run separately. Resuming Gate 3 reuses its existing receipts and completed branches. An interrupted model call with no committed turn record remains unresolved rather than being silently retried.

dcp-harness capture   --config my-audit/dcp-harness.json --run my-audit/run-001
dcp-harness challenge --config my-audit/dcp-harness.json --run my-audit/run-001
dcp-harness gate3     --config my-audit/dcp-harness.json --run my-audit/run-001
dcp-harness finalize  --config my-audit/dcp-harness.json --run my-audit/run-001
dcp-harness status    --config my-audit/dcp-harness.json --run my-audit/run-001

Trust boundary

The harness owns agent execution, action mediation, Web capture and replay, randomization, checkpoints, receipts, and append-only ledgers. The Python task adapter is trusted only for the parts that necessarily depend on the task. It prepares public files, runs the private verifier, and defines truthful and neutral observations. assemble_evidence() derives scores, hashes, counts, and branch records mechanically. Its AuditAttestations input contains the small set of task-specific judgments that cannot be inferred from bytes. Every attestation defaults to false.

Built-in positive controls check file delivery and response formatting by copying a canary. They do not independently establish the proposal's broader Memory, Web, and known-component calibration coverage. Assess that coverage separately when approving a new task's audit.

The model API connection is infrastructure transport, not a research Web channel. In container mode the agent has no tool capable of starting an arbitrary network request. A task adapter that talks to another service must treat that service as a registered experiment and return its observation through the audited action channel.

Current scope

The alpha supports one local auditor, Claude Code CLI, Docker isolation, allowlisted HTTPS capture, exact observed-URL replay, Gate 2 challenges, Gate 3 paired feedback and sham branches, pre-action infrastructure replacement, resumable phases, and deterministic local Bundles. Host mode is available for development but cannot attest private isolation. Local Bundles always retain formal_certificate_issued=false; formal countersigning belongs to a future external registry rather than this package.

See the repository usage guide for the complete CLI and Python examples.

Licensed under Apache-2.0.

Release files for dcp-harness 0.1.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for dcp-harness 0.1.0
File Size Uploaded
dcp_harness-0.1.0.tar.gz 70.7 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for dcp-harness 0.1.0
File Interpreter ABI Platform
dcp_harness-0.1.0-py3-none-any.whl Python 3 none any Details

Total release size: 135.2 kB

Release files / dcp_harness-0.1.0.tar.gz

Download URL dcp_harness-0.1.0.tar.gz
Size 70.7 kB
Tags Source
SHA-256 checksum
How to use checksums
62ee8b511363da69272abd7f0ecaecb5fe319629049ba359dd72d14389b5a67e
BLAKE2b-256 checksum
How to use checksums
19c95ecead139187bac83526cf7e6025922b84790e12808c78d5982930802685
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Sep 5, 2026.

Transparency log

Release files / dcp_harness-0.1.0-py3-none-any.whl

Download URL dcp_harness-0.1.0-py3-none-any.whl
Size 64.5 kB
Tags Python 3
SHA-256 checksum
How to use checksums
f1df49e197926164842944b2954135ca3bd12c642cf72b809544679e48f52525
BLAKE2b-256 checksum
How to use checksums
71d3ba7df0df0fa9b38f09fff20c0dde9cfc40e337f0be872a7d4b1d2acc102f
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Sep 5, 2026.

Transparency log

Release history Release notifications | RSS feed

0.1.1

2 release files

This release

0.1.0 This release

2 release files

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page