Finding
ADR-190 (proposed in #554) introduces shipped base weights that users personalise locally. Adopting a new base means rebasing the local delta, and rejecting it means maintaining your own base. That exposed a classification the project has not written down. agent-ways sits between Claude Code and the person using it: it shapes what the model sees without replacing Claude Code. "Sub-harness" is the working name. ADR-190 defers the term, and the roles it implies, to a separate ADR.
Proposal
An ADR that defines:
- Sub-harness. What agent-ways is relative to Claude Code, and what it owns: the corpus, hooks,
wayd, and weights.
- Adopters. People who track the upstream corpus and base weights, and what they get automatically: rebasing in shadow, the acceptance check, and rollback.
- Forkers. People who maintain their own branch, corpus, base weights, and possibly training recipe, and what the tooling guarantees them. For example,
ways tune rerank --base <path|release> works without assuming the upstream base, and nothing names the maintainer's base.
- Where this touches installation and releases: ADR-184's targets and activation, and the release manifest's lineage and licence chain.
Finding
ADR-190 (proposed in #554) introduces shipped base weights that users personalise locally. Adopting a new base means rebasing the local delta, and rejecting it means maintaining your own base. That exposed a classification the project has not written down. agent-ways sits between Claude Code and the person using it: it shapes what the model sees without replacing Claude Code. "Sub-harness" is the working name. ADR-190 defers the term, and the roles it implies, to a separate ADR.
Proposal
An ADR that defines:
wayd, and weights.ways tune rerank --base <path|release>works without assuming the upstream base, and nothing names the maintainer's base.