What problem does it solve? Platform teams and agents often make infrastructure decisions without a written, enforceable source of constraints, leading to inconsistent naming, ungoverned regions, unclear compliance obligations, and undefined agent permissions. This Skill produces a versioned constitution document that every downstream platform skill and agent treats as its governing contract. ## Core Features & Use Cases - Constraint capture: Records decided, enforceable rules across scope and sovereignty, compliance regimes (SOC 2, ISO 27001, NIS2, DORA), naming and tagging standards, approved stacks, IaC rules, agent authority boundaries, and observability defaults. - Rule-ID governance: Assigns each rule an ID (CON-xx) so specs, PRs, and verifier findings can cite specific constraints, with amendments following the same PR and approval path as code. - Use Case: When starting an Azure platform engagement, interview stakeholders about existing CAF alignment and landing zones, then draft a constitution with region allowlists, mandatory tags, Bicep-first IaC policy, and read-only agent credentials that downstream skills cite in every recommendation. ## Quick Start Draft a platform constitution for my Azure organization covering allowed regions, SOC 2 compliance evidence, naming and tagging standards, and what agents may do autonomously.
