The dependencies page presents the run seam (and the spec and history seams) as live, with external loops behind one contract, but the adapters chapter says those seams are design targets

The dependencies page presents the run seam (and the spec and history seams) as live, with external loops behind one contract, but the adapters chapter says those seams are design targets

A premise contradiction (severity minor) found by the cross-document consistency pass.

• End A: .abcd/development/brief/02-constraints/02-dependencies.md:43 — "Claude Workflows, the companion harness's agent loop, or a thin native Go loop behind one contract."
• End B: .abcd/development/brief/05-internals/02-adapters.md:34 — "are design targets, each introduced by the first intent that consumes it"

The dependencies page says every capability abcd once delegated to a bundled tool has a native default with the external tool available as an opt-in adapter over the same seam. As live examples it gives the run seam, with Claude Workflows, the companion harness's loop or the native loop behind one contract, the spec seam with ccpm, and the history seam with specstory. The adapters chapter says only scanner exists as a seam. It calls oracle, history, spec and run design targets, each to be introduced by the first intent that consumes it, and says no registry for choosing a backend exists. External loops cannot be available behind a seam that is not built.

Evidence: .abcd/work/reviews/2026-10-26-consistency/00-summary.md, finding 97.