2026-07-17 21:30:39 +00:00
|
|
|
# agent-harness
|
|
|
|
|
|
Harness foundation: INTENT, ADR-001, architecture, prototype adoption
- INTENT.md: three-layer model (blueprint/instance/harness), single
shared runtime, never-become boundaries
- ADR-001 (accepted): DEC-2026-002 resolution — one harness repo for
all projects; instances are declarative state in consuming repos
- docs/architecture.md: components, contracts (manifest, tool
profiles, completion events, credential lanes), deployment shape
- agent_harness/: executor-worker prototype adopted and renamed
(6/6 tests green); HARNESS-WP-0001 initial workplan (7 tasks)
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-17 23:35:27 +02:00
|
|
|
The single shared runtime for unattended agent instances in the Coulomb /
|
|
|
|
|
Operational Knowledge ecosystem. Projects declare agents (manifest +
|
|
|
|
|
`.kaizen/` state); this harness runs them — blueprint via kaizen-agentic,
|
|
|
|
|
tasks via activity-core, compute via llm-connect, credentials via
|
|
|
|
|
OpenBao/ops-warden, reporting to the Custodian State Hub.
|
|
|
|
|
|
|
|
|
|
- Why and boundaries: [INTENT.md](INTENT.md)
|
|
|
|
|
- Decision + architecture: [docs/adr/ADR-001](docs/adr/ADR-001-agent-harness-architecture.md),
|
|
|
|
|
[docs/architecture.md](docs/architecture.md)
|
|
|
|
|
- Current work: [workplans/](workplans/)
|
|
|
|
|
|
2026-07-17 23:49:03 +02:00
|
|
|
## Usage
|
Harness foundation: INTENT, ADR-001, architecture, prototype adoption
- INTENT.md: three-layer model (blueprint/instance/harness), single
shared runtime, never-become boundaries
- ADR-001 (accepted): DEC-2026-002 resolution — one harness repo for
all projects; instances are declarative state in consuming repos
- docs/architecture.md: components, contracts (manifest, tool
profiles, completion events, credential lanes), deployment shape
- agent_harness/: executor-worker prototype adopted and renamed
(6/6 tests green); HARNESS-WP-0001 initial workplan (7 tasks)
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-17 23:35:27 +02:00
|
|
|
|
|
|
|
|
```
|
2026-07-17 23:49:03 +02:00
|
|
|
# Validate a consuming repo's instance manifest (.kaizen/schedule.yml)
|
|
|
|
|
agent-harness validate --target ~/binky-control
|
|
|
|
|
agent-harness validate --target ~/binky-control --strict # require harness fields
|
|
|
|
|
|
|
|
|
|
# List named tool profiles
|
|
|
|
|
agent-harness profiles
|
|
|
|
|
|
|
|
|
|
# Run exactly one task (local JSON task-file path)
|
|
|
|
|
agent-harness run --task-file examples/task-hello-sandbox.json [--no-hub] [--no-metrics]
|
|
|
|
|
|
|
|
|
|
# Deterministic mailbox scan (no LLM session)
|
Harness foundation: INTENT, ADR-001, architecture, prototype adoption
- INTENT.md: three-layer model (blueprint/instance/harness), single
shared runtime, never-become boundaries
- ADR-001 (accepted): DEC-2026-002 resolution — one harness repo for
all projects; instances are declarative state in consuming repos
- docs/architecture.md: components, contracts (manifest, tool
profiles, completion events, credential lanes), deployment shape
- agent_harness/: executor-worker prototype adopted and renamed
(6/6 tests green); HARNESS-WP-0001 initial workplan (7 tasks)
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-17 23:35:27 +02:00
|
|
|
agent-harness mail-scan --target-repo ~/binky-control
|
|
|
|
|
```
|
|
|
|
|
|
2026-07-17 23:49:03 +02:00
|
|
|
Each `run` resolves the agent's tool profile + budget from the target
|
|
|
|
|
repo's instance manifest (default `green-commit-only`), loads a persona
|
|
|
|
|
bundle (`kaizen-agentic schedule prepare`), runs a bounded agentic
|
|
|
|
|
session (cwd-pinned, hard allow-list, never pushes), verifies a local
|
|
|
|
|
commit, writes `.kaizen/metrics`, and posts a State Hub progress event.
|
|
|
|
|
|
|
|
|
|
Instance manifest contract: [docs/instance-manifest.md](docs/instance-manifest.md).
|
|
|
|
|
Example: [examples/schedule.harness.yml](examples/schedule.harness.yml).
|
Harness foundation: INTENT, ADR-001, architecture, prototype adoption
- INTENT.md: three-layer model (blueprint/instance/harness), single
shared runtime, never-become boundaries
- ADR-001 (accepted): DEC-2026-002 resolution — one harness repo for
all projects; instances are declarative state in consuming repos
- docs/architecture.md: components, contracts (manifest, tool
profiles, completion events, credential lanes), deployment shape
- agent_harness/: executor-worker prototype adopted and renamed
(6/6 tests green); HARNESS-WP-0001 initial workplan (7 tasks)
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-17 23:35:27 +02:00
|
|
|
|
|
|
|
|
Tests: `PYTHONPATH=".:$HOME/llm-connect" python3 -m pytest tests/ -q`
|