Retire completed plans and outline named inheritance

This commit is contained in:
2026-09-29 20:11:42 +00:00
parent b604aa167b
commit 0a4b774bfe
9 changed files with 301 additions and 1318 deletions

View File

@@ -24,9 +24,12 @@ contract, if any, would be appropriate.
## Distinction From Layered Loading
The separate [filesystem and layered-loading request](feature-request-promptkit.md)
concerns acquiring configuration from different sources and combining it under
explicit composition or precedence rules.
The completed filesystem and layered-loading request is preserved in Git history
at `b604aa1:docs/roadmap/feature-request-promptkit.md`. The implemented
[layered-loading contract](../config.md#layered-loading) covers acquiring
configuration from different sources and combining it under explicit composition
or precedence rules. The proposed ConfigKit design for this remaining request
is in the [named-inheritance roadmap](named-inheritance.md).
Named inheritance concerns relationships between configuration entries: a child
identifies a base, which may itself identify another base. The relationship