Remove completed planning documents
This commit is contained in:
@@ -2,16 +2,8 @@
|
||||
|
||||
Current Notarius behavior is documented in the canonical README, CLI,
|
||||
configuration, operations, internal, and integration docs. This backlog records
|
||||
future work outside the [native migration roadmap](promptkit.md), which owns
|
||||
PromptKit/ConfigKit/CommandKit adoption, continuation, admission, cache, output,
|
||||
and debug decisions. Items below are ordered roughly by value and specificity,
|
||||
not as committed release dates or prerequisites for that migration.
|
||||
|
||||
Native shared loading/commands, complete assessment/continuation, concurrent
|
||||
ready lane completion, accepted-result reuse, and private capture are implemented;
|
||||
see the [implementation evidence](implementation.md) for final acceptance status.
|
||||
They are not deferred platform work. Human model-quality evaluation, broader
|
||||
reference/context policies, and storage/distribution extensions below remain separate.
|
||||
proposed extensions to that implementation. Items below are ordered roughly by
|
||||
value and specificity, not as committed release dates.
|
||||
|
||||
## Near-Term D&D Pipeline
|
||||
|
||||
@@ -57,12 +49,12 @@ The sections below keep broader extensions deferred.
|
||||
|
||||
- Consider a dedicated semantic-policy selection option for a typed
|
||||
reconciliation module when a concrete operator workflow needs more than the
|
||||
migration's [native prompt replacement](promptkit.md#configuration-sources-and-prompt-assets).
|
||||
[native prompt replacement](../config.md#promptkit-profiles).
|
||||
- Use native prompt IDs and sources while retaining typed interpretation and
|
||||
deterministic safety rules. Define any additional configuration and domain
|
||||
compatibility checks from that workflow; do not recreate asset registration,
|
||||
prompt fingerprints, or checkpoint dependency tracking.
|
||||
- Reuse the selected [accepted-artifact cache policy](promptkit.md#accepted-artifact-cache-u8-resolved)
|
||||
- Reuse the [accepted-artifact cache policy](../operations.md#accepted-result-cache-and-recovery)
|
||||
when evaluating policy changes and the need for explicit refresh.
|
||||
|
||||
### Broader Reconciliation Inputs And Module Selection
|
||||
@@ -83,7 +75,7 @@ The sections below keep broader extensions deferred.
|
||||
- Add production LLM-backed validators only when a concrete review policy
|
||||
benefits from model judgment and deterministic checks are insufficient.
|
||||
- Consider additional validator diagnostic views only if a concrete need remains
|
||||
after the selected [native observations and debug capture](promptkit.md#inspection-and-execution-bookkeeping).
|
||||
with the existing [native observations and debug capture](../internal/llm.md#native-evidence-and-sensitive-data).
|
||||
- Existing typed resolution already checks validator target, artifact kind,
|
||||
and exact Go-type compatibility. Add further semantic suitability metadata
|
||||
only if a deployment needs a contract beyond those implemented checks.
|
||||
@@ -128,7 +120,7 @@ Define compatibility and migration policy before generated-reference chains
|
||||
must span multiple schema versions or long-lived historical artifacts. The
|
||||
policy should address stable identifier semantics, when an older artifact may
|
||||
be decoded or adapted, and when consumers need regenerated artifacts. For cached
|
||||
artifacts, use the [selected reuse policy](promptkit.md#accepted-artifact-cache-u8-resolved)
|
||||
artifacts, use the [current reuse policy](../operations.md#accepted-result-cache-and-recovery)
|
||||
and explicit refresh where needed. Do not add a general migration framework
|
||||
until an actual contract change requires one.
|
||||
|
||||
|
||||
Reference in New Issue
Block a user