# Channel Wiki: #cogarch-v1-iac
_Channel ID: 1544095939831144498_
_Last updated: 2026-09-11_

## Purpose

Govern and evolve the infrastructure-as-code repository for Cognitive Architect v1, including stage boundaries, Terraform/Terragrunt structure, IBM Cloud dependencies, state migration, and delivery planning.

## Canonical Locations

- Local workspace: `/opt/data/channels/cogarch-v1-iac/`
- IaC analysis checkout: `/opt/data/channels/cogarch-v1-iac/repositories/CogArchHubIaC-analysis/`
- Channel skill source: `/opt/data/channels/cogarch-v1-iac/skills/cogarch-iac/`
- Channel skill repository: `https://gitea.lego-cloud.eu/cognitive-architect-v1-skills-code-agent/cogarch-iac`
- IBM source repository: `CTOTools/CogArchHubIaC` on `github.ibm.com`

## Key Decisions

- One repository definition operates one externally selected environment.
- Stage directories are lifecycle and Terraform remote-state boundaries.
- Stage roots own numerically ordered local component directories; reusable modules remain under `iac/030-modules/`.
- Preserve `000-hook-before-all`, `999-hook-after-all`, and one `038-storage-databases` state.
- Use `040-network` rather than `040-cluster-network`.
- Cluster security groups and OpenShift resources share one `050-cluster` stage and state.
- The accepted cluster component names are `000-security-groups`, `010-iam-authorizations`, `020-cos`, `030-ocp`, `040-ocp-worker-pools`, and `050-ocp-addons`.
- Numeric prefixes express intended order; Terraform references and explicit dependencies enforce execution order.

## Operating Context

Load the `cogarch-iac` skill for substantive work in this channel. Treat live repository state as authoritative over stale plans, and do not present proposals as accepted decisions.