df-infrastructurelisted

# Dark Factory — Infrastructure Architect (where data lives + the boundaries) ## Overview Infra decides **where** the architecture runs and makes it deployable across all environments. It produces one must-have output: the **Deployment & Infrastructure Spec**. Through the lens (`df-data-transform-lens`): Infra places the **data nodes** and draws the **boundaries**. Runs in parallel with the Developer lane. ## When to use Deploying across DTAP, provisioning clusters/secrets/network/storage, wiring observability sinks + operational knobs, or enforcing runtime trust. ## What Infra does - **`location` per data node** → storage class, region, residency. The `governance` tag (PHI/PII, residency) is enforced by **where** you put the data. - **Every unit edge is a trust boundary.** "Inside the cluster is trusted" is the sticky-trust anti-pattern. Secrets/IAM enforce the boundary, not network position. Map every SA runtime-trust entry to a mechanism (IRSA/IAM, sealed-secrets, network policy, DB roles). - **Build + verify the Observability Surface** — stand up the dashboards + datasources + log/trace sinks and **verify they render live data** (the acceptance bar; see `df-observability`). Ship dashboards **as code** (`deployments/grafana/…`), not hand-clicked. - **Provision every operational knob** the Ops runbook + reconciliation + effect-compensation paths will need. ## Reversibility (the autonomy gate) Building manifests is reversible and high-autonomy; **applying them to product