3.2 KiB
3.2 KiB
ADR-0013 — Capability Resolution, Selection and Gap Handling Foundation
Status: ACCEPTED
Date: 2026-08-17
Context
DEV-000063 introduced Work-owned CapabilityRequirement without selecting or executing concrete implementations. The system now needs a provider-neutral way to answer which real capabilities can satisfy a requirement, whether they are operationally usable, whether policy permits them, and what typed gap remains when no implementation is eligible.
The Core Semantic Model already assigns Capability registry/bindings ownership to the Capability module. Cognitive Registry is a specialized capability registry for model/provider/model-binding semantics. This ADR must not create a parallel cognitive source of truth.
Decision
- Keep
capabilityas the canonical owner for capability descriptors, implementation registrations, implementation health/availability, resolution results, typed gaps, acquisition strategy candidates and generic capability usage observations. - Represent a capability separately from an implementation:
Capability/CapabilityRef: what the system can obtain or do.CapabilityImplementation: a concrete adapter, provider, runtime, agent or internal function that may satisfy that capability.
- Capability identity is typed but extensible. Known
CapabilityKindconstants are allowed for current semantics, but the registry stores string capability kinds and stable capability IDs without imposing a closed universe. - Resolver V1 returns
AVAILABLE,PARTIALLY_AVAILABLE,UNAVAILABLEorUNKNOWNwith eligible implementations and typed exclusion/gap reasons. - Selection V1 is deterministic and evidence-weighted. It must rank eligible implementations by typed evidence and stable IDs, not by hardcoded provider/adapter names.
- CredentialRef is allowed as implementation metadata, but credential existence never means capability availability or Authority. Secret values remain outside canonical state and are resolved only by trusted runtimes.
- Cognitive systems remain integrated through the existing Cognitive Registry and Router. General capability resolution may express the conceptual relation that cognition is a capability, but cognitive invocation continues through the existing gateway/router.
- Reminder scheduling is the first concrete production capability for this foundation. It creates Continuity-owned
ProspectiveItemstate through the Continuity runtime boundary. It does not create durable Work for simple reminders. - Unsupported email sending creates a Capability-owned
CapabilityGapcorrelated to the original human intent. It must not claim execution and must not become an automatic Codex/self-extension task.
Consequences
capabilitygains generic implementation, resolution, gap and usage-observation contracts/tables.continuitygains a narrow authenticated creator reminder-registration endpoint that owns creation ofProspectiveItemrows./chatcan schedule a simple reminder through capability resolution and can persist a typed gap for unavailable capabilities.- No cognitive binding is promoted to
ACTIVE. - No new canonical owner, broad plugin marketplace, autonomous adapter installation or self-modifying loop is introduced.