Record native operator interface ownership and align documentation

This commit is contained in:
2026-11-20 00:49:27 +00:00
parent 6ed4ac624a
commit bcb1a76e34
4 changed files with 97 additions and 34 deletions

View File

@@ -1,9 +1,9 @@
# CommandKit migration notepad
Status: design direction agreed; ready for feature-roadmap preparation. This
working record captures the decisions for Scriptorium's CommandKit migration.
The remaining integration details below belong in the roadmap alongside
implementation sequencing and validation.
Status: discussion record incorporated into the
[adoption roadmap](commandkit-adoption.md) and
[ADR 0006](../adr/0006-adopt-commandkit-native-operator-interfaces.md).
The roadmap owns implementation work; the ADR records the ownership decision.
## Product context
@@ -49,11 +49,11 @@ use `ckconfig` and `ckprompt` for their standardized operator interfaces.
Scriptorium should retire the corresponding custom inspection machinery as
those interfaces take over.
PromptKit continues to own preparation and execution semantics. ConfigKit
continues to own configuration resolution. Scriptorium supplies application
configuration and source selection, generation and server commands, process
lifecycle, and application-specific artifact handling. CommandKit adoption
does not introduce workflow or conversation state.
ConfigKit owns configuration policy through the fully resolved handoff,
including PromptKit configuration resolution. PromptKit owns prompting and
inspection semantics. Scriptorium interprets resolved values and uses upstream
APIs and results to satisfy user requests. CommandKit adoption does not introduce
workflow or conversation state. ADR 0006 records these boundaries.
Prefer shared upstream capabilities over new Scriptorium-specific equivalents.
If a required shared capability is missing, discuss an upstream request before
@@ -320,13 +320,11 @@ flag and loader mappings, and sequence replacement and removal of CLI code.
Define appropriate verification for the selected behavior and update canonical
documentation, examples, and release migration guidance as implementation lands.
## Preparing the roadmap
## Roadmap handoff
Fold the agreed decisions and remaining integration details into a feature
roadmap. Preserve the selected upstream conventions and explicit non-goals.
Record any concrete new issue found during preparation without reopening settled
product choices merely to preserve the old CLI. This notepad remains the
discussion record until its decisions have been incorporated into that roadmap.
The [adoption roadmap](commandkit-adoption.md) incorporates these decisions and
integration details. Keep implementation status there; retain this notepad as
the discussion record.
[upstream-guide]: https://forge.maximumdirect.net/base-layer/commandkit/src/commit/d330d7637f2e7507eca931a899397222c82bc892/docs/consumers/guide.md
[upstream-cli]: https://forge.maximumdirect.net/base-layer/commandkit/src/commit/d330d7637f2e7507eca931a899397222c82bc892/docs/cli.md