Skip to content

About

Transport-neutral agent harness semantic contract, schemas, fixtures, and conformance

Resources

Stars

0 stars

Watchers

0 watching

Forks

Latest commit

 

History

4 Commits

Folders and files

NameName
Last commit message
Last commit date
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Agent Harness Contract

An independent, transport-neutral semantic contract for session-owning agent harnesses and their controllers. The public contract is the specification in spec/semantic-v0.md, the JSON Schema, and the machine-readable examples. The schema checks record shapes; the specification defines behavior that JSON Schema cannot express. Neither Duo's Go types nor a first-party agent defines conformance.

Status: v0 contract-authoring snapshot. The process-external conformance runner can test an external implementation through a suite-private subprocess driver; no real runtime has been exercised yet. The 2026-09-26 step-6 decision declines to select a first public binding pending a named owner boundary and fresh scoped evidence; it establishes no runtime support or conformance. Compatibility release/tag and first-party agent remain later roadmap steps. Fixture and runner self-tests are not evidence that a particular runtime passes. A consumer should pin the repository commit and artifact digests until a tagged conformance release exists.

This repository is distinct from Duo's northbound duo.external/v1 contract and from the separately named first-party agent implementation repository. Duo is one possible controller. No central model-traffic relay, terminal, transport, or Go dependency is required.

Validate the example records with Python 3 and the jsonschema package (version 4.10 or newer):

python3 tests/check_fixtures.py
python3 -m unittest discover -s tests/conformance -p 'test_*.py'

To exercise an external harness, provide its driver and a disposable subject:

python3 tests/conformance/run.py -- /absolute/path/to/your-driver

The runner reports per-scenario PASS, FAIL, or UNVERIFIED; it never issues a blanket compatibility verdict. Missing claims or independent fault hooks do not count as passes. This suite-private driver is not the step-6 binding.

The roadmap places this semantic contract in step 4, process-external conformance in step 5, unlike-topology mapping and binding selection in step 6, and the first-party agent in step 7. Private research informs the contract but is neither a publication dependency nor a current runtime support claim. Implementations must re-verify any live external pin they rely on.

Licensed under MIT.

About

Transport-neutral agent harness semantic contract, schemas, fixtures, and conformance

Resources

Stars

0 stars

Watchers

0 watching

Forks

Releases

Packages

Contributors

Languages