Adopt shared configuration model in architecture and implementation plan

This commit is contained in:
2026-11-21 13:51:26 +00:00
parent 515649fee0
commit 248d0dbcf5
6 changed files with 210 additions and 75 deletions

View File

@@ -38,6 +38,11 @@ The temporary copy is exploratory evidence, not a patch ready to merge. Its
generated conversion boilerplate and experimental names are not proposed as a
new generator or a finalized public API.
Subsequent design decision: [ADR 0002](../adr/0002-shared-configuration-data-model.md)
selects one shared settings model exposed through root aliases. The assessment
below records the experiment as run; its separate settings declarations and
conversions are superseded by the [implementation plan](implementation.md).
## Results
| Area | Evidence |
@@ -70,8 +75,9 @@ before library callbacks; a consumer could wrap the returned callbacks to run
another component afterward. No component registry was needed.
Keep actual normalization and validation in one internal rule implementation.
Public settings conversions are ordinary facade boundary work, not another
composition pass. Capture owned execution values after successful loading.
The prototype's public settings conversions were ordinary facade boundary work,
not another composition pass; the selected shared model removes them. Capture
owned execution values after successful loading.
The existing public source-construction types need not become the decoding model
merely because some fields resemble it.