Terraform + Intended: Infrastructure as Authority

Status: on the roadmap — not yet available. The Intended Terraform provider is an early-stage stub today, not a shipped product: there is no published provider on the Terraform Registry and no intended_* resources you can apply. This post describes the model we're building toward. We removed the earlier HCL examples because they referenced resources that don't exist yet — we won't ship copy-pasteable code that can't run. Track this work in the capability build roadmap and the Capability Truth Matrix (row: *Terraform provider → Planned*).

If your infrastructure is defined as code, your authority policies should be too. The goal of the Intended Terraform provider is to let you manage policies, domain packs, escalation workflows, and agent configurations using the same HCL syntax and GitOps workflows you use for everything else — so there's no clicking through a console to create policies, no manual changes that aren't tracked in version control, and no drift between what you think your policies are and what they actually are.

What you can do today instead

Until the provider ships, manage policy-as-code through the tested paths:

• The CLI — author, validate, and deploy policy packs (intent-submit, policy-pack-install, audit-query). See the Capability Truth Matrix for the exact command surface.
• The REST API — the same operations a provider would wrap are available directly; see the API reference.
• Policy packs in your repo — keep your policy-pack JSON in version control and deploy it via CI using the CLI, which gets you GitOps-style review and rollback today.

What the provider will add

When it ships, the provider will wrap those same APIs as first-class Terraform resources (policies, domain-pack installs, escalation workflows, agent configs) with plan/apply/import and drift detection — so authority becomes part of the same terraform plan your platform team already reviews. We'll publish runnable HCL here the moment the provider is real.