Configuration boundary and ownership review #583

Closed
opened 2026-10-27 13:36:54 +00:00 by sam · 0 comments
Owner

Run the first focused architecture campaign for the configuration refactor. Trace the current TOML/YAML loaders, defaults, validation, overlays, secret references, identity/repository settings, worker snapshots, container/NATS passthrough, and every production consumer. Produce a field-level current-to-target ownership ledger and decide the smallest behavior-preserving migration slice. Do not edit runtime code until ownership, input DTO boundaries, provenance requirements, schema generation boundary, compatibility semantics, and deletion criteria are recorded.

Acceptance Criteria

A reproducible current-state trace covers entrypoints, loaders, consumers, process boundaries, tests, deployment passthrough, and decoded-but-unwired fields; every in-scope setting has one current owner, target owner, scope, validation/provenance behavior, and migration disposition; base/overlay and secret compatibility semantics are explicit; the first implementation slice has an observable outcome, bounded change cone, parity tests, rollback, and deletion criterion; no unresolved semantic decision is left for the implementer to invent.


Imported from beads archie-core-1786637491213-54-c614e36e · GitHub #75 · type task · priority P2 · created 2026-08-08 · closed 2026-08-08

Run the first focused architecture campaign for the configuration refactor. Trace the current TOML/YAML loaders, defaults, validation, overlays, secret references, identity/repository settings, worker snapshots, container/NATS passthrough, and every production consumer. Produce a field-level current-to-target ownership ledger and decide the smallest behavior-preserving migration slice. Do not edit runtime code until ownership, input DTO boundaries, provenance requirements, schema generation boundary, compatibility semantics, and deletion criteria are recorded. ### Acceptance Criteria A reproducible current-state trace covers entrypoints, loaders, consumers, process boundaries, tests, deployment passthrough, and decoded-but-unwired fields; every in-scope setting has one current owner, target owner, scope, validation/provenance behavior, and migration disposition; base/overlay and secret compatibility semantics are explicit; the first implementation slice has an observable outcome, bounded change cone, parity tests, rollback, and deletion criterion; no unresolved semantic decision is left for the implementer to invent. --- _Imported from beads `archie-core-1786637491213-54-c614e36e` · GitHub #75 · type task · priority P2 · created 2026-08-08 · closed 2026-08-08_
sam added the mediumtask labels 2026-10-27 13:36:54 +00:00
sam self-assigned this 2026-10-27 13:36:54 +00:00
sam closed this issue 2026-10-27 13:36:54 +00:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: sam/archie#583