35 lines
1.7 KiB
Markdown
35 lines
1.7 KiB
Markdown
# Deferred Scope
|
|
|
|
This document owns intentionally excluded features, not a committed delivery plan.
|
|
The [architecture policy](../policy/architecture.md) governs changes to these
|
|
boundaries. Implemented behavior belongs in the [configuration contract](../config.md)
|
|
and consumer adoption in the [consumer guide](../consumers/README.md).
|
|
|
|
## Explicit non-goals and deferred scope
|
|
|
|
General environment-variable configuration overlays are not supported. Typed secret
|
|
references and explicit directory bootstrap are the environment convention. Literal
|
|
credential configuration and implicit secret-directory discovery are unsupported.
|
|
|
|
The following remain deliberately excluded:
|
|
|
|
- automatic `conf.d` discovery;
|
|
- remote imports, arbitrary providers, and additional configuration formats;
|
|
- custom merge strategies, sequence merging, and reset operators;
|
|
- named overlay inheritance;
|
|
- parser-specific or custom structural-decoding extension APIs;
|
|
- generic dynamic-subtree conversion and module-registry APIs;
|
|
- automatic schema migrations;
|
|
- hot reload, runtime resource replacement, and remote resource validation;
|
|
- a bundled CLI framework or application commands; and
|
|
- configuration diffs and fingerprints.
|
|
|
|
Applications may build their own validate, effective-value, source, bootstrap, and
|
|
explanation commands around the library. Broadening these boundaries requires
|
|
concrete consumer evidence, compatibility review, and an explicit design change.
|
|
|
|
Built-in sibling inheritance using `extends` is proposed in the
|
|
[named-inheritance roadmap](named-inheritance.md), based on the
|
|
[downstream request](feature-request-promptkit-inheritance.md). It is not yet
|
|
implemented and is distinct from inheritance between selected overlay files.
|