agent harness v0.8.0

v0.8.0

The eighth release of @judgment-pack/harness, as an attested package asset and a Go module tagged by the release workflow. It holds the decisions that complete the agent's operating surface: the agent's policy table, cross-provider modelling, sub-agents, the write side of memory, proposal edits, context compaction, the output boundary, records, identity per tool call, provider failover with the usage ledger, steering a run in flight, and the evaluation corpus. Every change was built by Codex CLI from an accepted design, reviewed in a clean-room or narrow round recorded on its pull request, and the whole release diff was reviewed once more before the tag (same vendor, OpenAI; not a cross-vendor claim); its findings, one HIGH on the store-side guard's label exemption and four MEDIUMs, were fixed in one batch (#133) and the fixed head re-read. There is no registry package.

What v0.8.0 holds

• ADR-0011, the agent's policy table (#116, #118): the policy the package applies, as one table in three layers with one precedence, every entry with its default, its owner and the event that records the choice.
• ADR-0012, cross-provider modelling (#117, #119): one model of a provider's capability (families, tiers, the reasoning levels) read the same way on every engine, with the host's explicit choices honoured and the fallbacks recorded.
• ADR-0013, sub-agents (#97, #120): delegated children with a declared profile, a bounded budget reserved from the parent's, no inherited catalogue, and their results framed as data at the continuation.
• ADR-0014, memory, the write side (#98, #121): a memory proposal as a reviewed write, never a silent one; framed recall; the refusal paths and the resume.
• ADR-0015, proposal edits (#110, #122): the person's edits to a proposal as a first-class step, validated by the Runtime, the prior draft preserved on refusal.
• ADR-0016, context compaction (#99, #123): the index by default and a bounded, framed summary on request, with the replaced turns' digests carried so a resume rebuilds the same bytes.
• ADR-0017, the output boundary (#100, #124): a redaction or refusal guard on what leaves the model: answers, proposals, tool arguments, notices (the gate's own included), undeclared tool names; tool results and declared names exempt; a versioned pattern set with vectors; counts per pattern on the checkpoint and the report.
• ADR-0018, records (#101, #126): retention, redaction on store and an export shape for checkpoints, reports and transcripts; the store-side guard counts in the records figures, carries delivery's exemptions, scans only the record's model-derived members and refuses a record it cannot redact.
• ADR-0019, identity per tool call (#102, #127): the person's or a service's identity declared on the source record, pinned per call, shown in the report; the first service act always asked; a credential-bearing label refused at declaration; the pin and the withholding state ride the checkpoint.
• ADR-0020, provider failover and the usage ledger (#104, #130): a switch to a declared fallback at a request boundary, recorded with its reason and restored on resume; a bounded number of switches with a refusal on exhaustion; a closed ledger per provider and model, aggregated over delegated children, host prices outside it.
• ADR-0021, steering a run in flight (#105, #129): the person's new words delivered at the next request boundary, framed at the rank of the person's turn, bounded, carried on the checkpoint and delivered once; a delegated child receives none.
• ADR-0022, the evaluation corpus (#103, #128): recorded, redacted runs replayed against each release engine and both Go adapters from recording-backed transports (the model's answers and the tools' results from the recording), a structured drift report, entries validated before store, three seed entries under corpus/.
• The pre-release rows (#115, #132): the critic's trigger order in the generated reference, integer fallback tiers read the same way in both languages, the compaction report's index mode carried by a vector.
• The devkit at v0.5.0 (#125, #131): the builder's self-checks in AGENTS.md, the handover lists in dev.json, the update-branches workflow; the mutation table builds the harness before its rows (#132).

What the Desk must do to adopt it

The follow-ups filed on the Desk for each decision (the composer, project form and report changes they name); judgment-pack-desk#537 and #546 as filed.

What it does not hold

the Desk follow-ups for these decisions (filed after the tag); the devkit's handover CI job in the adopting repositories (devkit #21); running Codex itself in GitHub Actions

Installing and verifying

Install the tarball from this release and pin it by the digest in checksums.txt; the Go module by go get github.com/Judgment-Pack/judgment-pack-agent/go@v0.8.0 with go.sum committed. Verify the attestation as docs/releasing.md describes before pinning.