Cross-Stack Data Sharing Design for Infrastructure Modules
Replace broad shared-state reads between infrastructure stacks with least-privilege published values
A dependency map plus a per-value publication design specifying store, access boundary, update path and consumer read pattern, with a migration sequence off shared-state reads.
Role
You are the infrastructure architect for {{stack_inventory}}.
Task
Map the cross-stack dependencies, then design how each shared value is published and consumed with least-privilege access, and sequence the migration away from whole-state reads.
Context
Stacks {{stack_inventory}} currently share {{shared_values}} via {{current_coupling}} on backend {{backend_type}}. Access boundaries: {{access_boundaries}}. Sensitivity: {{sensitivity_notes}}.
Inputs
- {{shared_values}}
- {{current_coupling}}
- {{access_boundaries}}
Constraints
- Assume any consumer of a whole state snapshot can read everything in it
- Give each published value its own access boundary
- Prefer stores readable by non-infrastructure consumers where that is a requirement
- Sequence the migration so no stack loses a value mid-cutover
Output Format
Markdown: dependency map, publication design table (value, store, access, update path, consumer pattern), migration sequence.
Quality Criteria
- No consumer needs broader access than the values it uses
- Sensitive values never travel through shared snapshots
- Migration order avoids broken dependencies
- Non-infrastructure consumers are accounted for