base-layer/commandkit
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Record the ConfigKit upgrade and comparison plan

Browse Source
This commit is contained in:
Eric Rakestraw
2026-10-11 18:23:55 +00:00
parent ecd713ef2f
commit f67ee235d7
3 changed files with 468 additions and 17 deletions
Download Patch File Download Diff File Expand all files Collapse all files

16
docs/policy/architecture.md
View File

@@ -2,7 +2,7 @@
**Base Policy Version:** 1.3
**Last Updated**: 2026-10-10
**Last Updated**: 2026-10-11
**Upstream Source:** [architecture.md](https://gitea.maximumdirect.net/eric/policy/src/commit/d84a38ebab26f048cafbe59a2246700c35d29843/docs/policy/architecture.md)
@@ -134,6 +134,14 @@ and input checks before shared state initialization and provider acquisition.
Factories need not run after a failure and remain uninvoked during construction,
installation, help, version, and scope discovery.
For two-selection configuration comparison, prepare and check each side's input
separately with its scope identity and selection, applying the same applicable
converted selector values to both. Finish both checks before initializing shared
state once and invoking the integration-owned pair provider under
[ADR 0012](../adr/0012-typed-configuration-comparison-pairs.md). Required provider
wiring follows declared capabilities; a comparison-only scope does not require
an unrelated ordinary acquisition callback.
Omitted input and state factories supply the respective type's zero value,
including nil for pointers. Caller factories and callbacks retain responsibility
for objects they return or reference; do not promise arbitrary deep copies,
@@ -232,8 +240,10 @@ Concrete integration needs guide provider representations under
Native report writers and safe inspection data preserve owning-library semantics.
Loading all selected views before report output is a `config show` decision under
[ADR 0007](../adr/0007-native-yaml-reports.md); other inspection operations define
their own output timing. Semantic comparison uses supported safe snapshots and
reports sensitivity gaps under [ADR 0008](../adr/0008-semantic-configuration-diff.md).
their own output timing. Semantic comparison delegates to supported owning-library
comparison APIs and retains paired safe disclosure and hidden-change metadata at
the provider boundary. Reports may present the reduced view selected by
[ADR 0008](../adr/0008-semantic-configuration-diff.md).
## Scope And Non-goals