Multi-harness control plane
State: closed/retired · Kind: system · Audience: user
Summary
Section titled “Summary”- Retired in
T-1NWG.sdlcused to author an agentic harness ONCE as a canonical, host-neutral model and emit it to multiple control planes — Claude Code, Codex, Cursor, Gemini — via a set of per-host exporters (sdlc harness export <target>). - Once the agent-pants vault build (
T-CIAA,T-66RD,T-FQN9) became sdlc’s sole build path for producing the Claude plugin itself, the exporters were a redundant, unused second build path — no host besides Claude was ever actually shipped — and were deleted along withharness export. - The canonical, host-neutral
HarnessModelshape and its Claude-derivation reader (deriveHarnessModel/importClaude, exposed assdlc harness model) survive as a read-only introspection op over the built plugin; see D-HRNS-harness-model-and-exporters for the original decision record (kept for history, not amended).
Statement
Section titled “Statement”An agentic harness is the surface a coding agent runs inside: its invocable capabilities, the
context it carries, the tools it may use, the servers it can reach, and the lifecycle hooks that
fire around it. This capability used to hold a canonical model of the surface plus a set of
exporters projecting it onto Claude Code, Codex, Cursor, and Gemini. No host besides Claude was ever
shipped through it, and Claude’s own plugin is now produced by the agent-pants vault build directly
(not through this model), so the multi-host projection this capability named is retired. sdlc harness model’s read-only introspection of the model remains, documented at
C-HRNS-multi-harness-control-plane’s locations.
What it provides
Section titled “What it provides”- A canonical
HarnessModel(metadata, capabilities, hooks, MCP servers, permissions, documents), validated with markdown-contract. - An importer that bootstraps the model from an existing Claude surface (still live).
- Exporters that emitted the native surface for Claude Code, Codex, Cursor, and Gemini, plus a
portable
harness.jsoninterchange form (retired inT-1NWG). sdlc harness export <target>(retired) andsdlc harness model(still live, read-only) on the deterministic op substrate.
Locations
Section titled “Locations”packages/ts/agent-plugin/solutions/ontological/lib/services/harness/ops/