Record native operator interface ownership and align documentation
This commit is contained in:
53
docs/adr/0006-adopt-commandkit-native-operator-interfaces.md
Normal file
53
docs/adr/0006-adopt-commandkit-native-operator-interfaces.md
Normal file
@@ -0,0 +1,53 @@
|
||||
# ADR 0006: Adopt CommandKit's Native Operator Interfaces
|
||||
|
||||
## Status
|
||||
|
||||
Accepted. Complements [ADR 0004](0004-definition-boundary.md) and
|
||||
[ADR 0005](0005-configkit-boundary.md). Both remain accepted and are not
|
||||
superseded.
|
||||
|
||||
## Date
|
||||
|
||||
2026-11-19.
|
||||
|
||||
## Context
|
||||
|
||||
Scriptorium is adopting CommandKit's native operator interfaces within the
|
||||
PromptKit and ConfigKit boundaries established by ADRs 0004 and 0005.
|
||||
|
||||
## Decision
|
||||
|
||||
Scriptorium adopts CommandKit's native operator interfaces.
|
||||
|
||||
ConfigKit owns configuration policy and everything in the configuration
|
||||
lifecycle before the final, fully resolved configuration handoff. Application
|
||||
schema and domain callbacks operate through ConfigKit's supported extension
|
||||
points within that lifecycle.
|
||||
|
||||
PromptKit owns prompt definitions, preparation, execution, validation, and
|
||||
inspection semantics. Its configuration is resolved through ConfigKit, with
|
||||
PromptKit supplying its domain schema and rules through ConfigKit's supported
|
||||
extension points.
|
||||
|
||||
Scriptorium owns the domain. After the handoff, it interprets the resolved
|
||||
configuration values and uses them to perform useful work that satisfies the
|
||||
user's request. It does not revise what constitutes effective configuration.
|
||||
It supplies requests through PromptKit's supported APIs and uses the returned
|
||||
results without redefining their meaning.
|
||||
|
||||
CommandKit's `ckconfig` and `ckprompt` integrations expose upstream ConfigKit
|
||||
and PromptKit features. Scriptorium neutrally makes those features available
|
||||
through the native interfaces, preserving upstream semantics.
|
||||
|
||||
## Alternatives Considered
|
||||
|
||||
Retaining custom configuration and prompt inspection would duplicate upstream
|
||||
behavior and create another owner for its semantics. Use the native integrations
|
||||
instead.
|
||||
|
||||
## Consequences
|
||||
|
||||
Standard inspection exposes the upstream result without constructing a different
|
||||
effective document, reconciling separate explanation trees, or reinterpreting
|
||||
upstream paths. The [adoption roadmap](../roadmap/commandkit-adoption.md) tracks
|
||||
implementation.
|
||||
Reference in New Issue
Block a user