Adapter And Host Ownership

Host repos own runtime-specific behavior.

Map keys: promise.readiness, promise.evaluation, rule.host-owned-execution, rule.vocabulary-consistency. Evidence path: deterministic plus consumer dogfood. Evidence status: current. Next action: keep adapter contract tests, the external consumer smoke, and the product-import-isolation lint deterministic; consumer-side parity proof grows when new host adapters land. Terms covered here: adapters, prompts, model choice, credentials, runtime launch, command templates, backend selection, fixtures, acceptance policy, repo-specific flags, portable schema.

Maintainer Promise

Cautilus owns generic workflow contracts, packet shapes, readiness semantics, behavior-surface vocabulary, and normalization helpers, while host repos own prompts, runners, credentials, model or backend selection, fixtures, and policy.

Subclaims

Cautilus-owned schemas and packet shapes describe the workflow without encoding host-specific runtime details.
Adapters expose host-owned commands and runtime decisions explicitly so they remain inspectable rather than hidden inside product logic.
The same product workflow runs unchanged across two adapters because repo-specific behavior lives in adapters and fixtures.
Cautilus does not import host-specific prompts, runners, credentials, or policy into product code paths.

Evidence

internal/runtime/adapter_test.go TestValidateAdapterData* family covers explicit and command-instance discovery, live-run invocation, typed runner readiness, and claim-discovery configuration against the adapter contract.
scripts/agent-runtime/adapter-resolution.test.mjs covers adapter resolution across host-owned name and path variants.
scripts/on-demand/smoke-external-consumer.test.mjs bootstraps a temporary external consumer repo through npm run consumer:onboard:smoke and asserts the same product workflow runs unchanged.
npm run lint:product-import-isolation (scripts/check-product-import-isolation.mjs) parses every non-test Go file under cmd/ and internal/ and rejects any third-party import outside an explicit allowlist; this proves product code paths do not pull in host-specific prompts, runners, credentials, or policy. Self-test: scripts/check-product-import-isolation.test.mjs.