Document PromptKit configuration ownership and capture
This commit is contained in:
@@ -1,6 +1,7 @@
|
||||
# ADR-0010: Use workload-oriented LLM profile defaults
|
||||
|
||||
**Status:** Accepted
|
||||
**Status:** Accepted; profile source replacement behavior superseded by
|
||||
[ADR-0019](0019-adopt-native-promptkit-configuration.md)
|
||||
**Date:** 2026-08-03
|
||||
|
||||
## Context
|
||||
@@ -23,11 +24,13 @@ intentional exceptions, and the run-wide CLI profile override has highest
|
||||
precedence.
|
||||
|
||||
The D&D family owns an embedded fallback profile named `dnd-extraction`.
|
||||
Operators may provide a complete profile with the same ID through a PromptKit
|
||||
filesystem source. PromptKit selects the higher-precedence matching definition;
|
||||
Notarius does not merge profile documents. Production, development, and local
|
||||
deployments can therefore use different execution policy behind one unchanged
|
||||
pipeline ID.
|
||||
Operators may configure the same ID through a PromptKit filesystem source. The
|
||||
original decision specified that an operator definition replaced the fallback
|
||||
as a complete profile; that source-composition clause has been superseded by
|
||||
[ADR-0019](0019-adopt-native-promptkit-configuration.md), which adopts native
|
||||
recursive overlays. The workload-oriented identity and D&D ownership decision
|
||||
remain in force. Production, development, and local deployments can therefore
|
||||
use different execution policy behind one unchanged pipeline ID.
|
||||
|
||||
## Alternatives considered
|
||||
|
||||
@@ -42,8 +45,8 @@ pipeline ID.
|
||||
## Consequences
|
||||
|
||||
Pipeline configuration expresses workload intent rather than a specific
|
||||
provider or model. Operators can replace the complete execution policy without
|
||||
editing bindings, while binding-level and run-wide exceptions remain available.
|
||||
Profile changes affect resolved pipeline and checkpoint identity, so they may
|
||||
provider or model. Operators can configure execution policy without editing
|
||||
bindings, while binding-level and run-wide exceptions remain available. Profile
|
||||
changes affect resolved pipeline and checkpoint identity, so they may
|
||||
intentionally cause work to be recomputed. The D&D fallback becomes a
|
||||
maintained application execution-policy asset.
|
||||
|
||||
Reference in New Issue
Block a user