From 07aaee8ef68f2145572ce568dec4ae3ade33e711 Mon Sep 17 00:00:00 2001 From: Eric Rakestraw Date: Sat, 21 Nov 2026 13:29:06 +0000 Subject: [PATCH] Add shared configuration model to future roadmap --- docs/roadmap/future.md | 18 ++++++++++++++++++ 1 file changed, 18 insertions(+) diff --git a/docs/roadmap/future.md b/docs/roadmap/future.md index 938c954..e351111 100644 --- a/docs/roadmap/future.md +++ b/docs/roadmap/future.md @@ -38,6 +38,24 @@ consumers. ## Ideas +### Shared Configuration Data Model + +Use one canonical configuration data model for the public settings API and the +internal configuration adapter. This could reduce duplicate type declarations, +field-by-field conversions, construction-time allocations, and the maintenance +needed when configuration fields change. + +- Consider a narrow architecture-policy exception allowing the root facade to + alias deliberately public, data-only settings types. A small public settings + package is an alternative if explicit public ownership is preferable. +- Treat shared settings types as intentional public contracts while retaining + loading, validation, and execution logic internally. +- Preserve owned runtime capture and independence from later caller mutation; + sharing type definitions does not eliminate necessary value copies. + +Selection requires an explicit architecture-policy decision. Inclusion here does +not change that policy or expand the current configuration-handoff scope. + ### Schema Bundling Allow consumers to author reusable schemas across multiple files and package