Document chunk plan remediation
This commit is contained in:
@@ -1,9 +1,8 @@
|
||||
# ADR-0005 Feature Roadmap
|
||||
|
||||
This roadmap defines the intended end state for
|
||||
[ADR-0005](../adr/0005-cache-canonical-chunk-plans-by-source.md). The feature
|
||||
is not implemented. The ordered coding work belongs in the
|
||||
[implementation plan](implementation.md).
|
||||
This roadmap records the implemented target state for
|
||||
[ADR-0005](../adr/0005-cache-canonical-chunk-plans-by-source.md). The
|
||||
[implementation record](implementation.md) preserves the completed work.
|
||||
|
||||
## Intent
|
||||
|
||||
@@ -156,11 +155,11 @@ This feature does not provide:
|
||||
|
||||
## Completion Outcomes
|
||||
|
||||
The feature is complete when independent runs over the same canonical source
|
||||
**Achieved.** Independent runs over the same canonical source
|
||||
reuse byte-stable materialized chunks across pipeline, lane, reference,
|
||||
chunk-module, and LLM configuration changes; bypass and refresh obey their
|
||||
documented state semantics; provenance identifies the effective producer;
|
||||
legacy chunk checkpoints cannot compete with plan reuse; and all focused,
|
||||
integration, compatibility, CLI, and repository-wide validation passes. The
|
||||
integration, compatibility, CLI, and repository-wide validation pass. The
|
||||
configuration and operations references must also document both the per-user
|
||||
default and the recommended system-wide Linux setting.
|
||||
|
||||
Reference in New Issue
Block a user