intutic_sop Cloud

A workspace SOP (rule set), managed through /api/v1/sops. A new SOP starts in DRAFT. Promotion through review, shadow and VALIDATED stays in the SOP review workflow, because each step is gated on evidence (the Gödel score, shadow results). Editing a SOP that is not a draft forks a new DRAFT version with a new id and retires the old one, exactly as an edit in the dashboard does; the plan shows lifecycle_state returning to DRAFT when that will happen. Needs an OWNER or ADMIN key.

Example Usage

resource "intutic_sop" "deploys" {
  title            = "Production deploys"
  markdown_content = file("${path.module}/sops/production-deploys.md")
  risk_tier        = "HIGH"
  complexity_tier  = "TIER_1"
}

Schema

Required

• complexity_tier (String) One of TIER_0, TIER_1, TIER_2.
• markdown_content (String) The SOP body in Markdown (at most 100,000 characters).
• risk_tier (String) One of LOW, MEDIUM, HIGH, CRITICAL.
• title (String)

Optional

• version (String) Version label (at most 16 characters). The API sets 1.0.0 on create and bumps the patch number when an edit forks a new version, unless you set it.

Read-Only

• content_hash (String) SHA-256 of markdown_content, as intutic sops status compares it.
• id (String) The SOP id (sp_…). Changes when an edit forks a new version.
• lifecycle_state (String) Where the SOP is in its review lifecycle (DRAFT … VALIDATED, INVALIDATED).
• version_counter (Number) Optimistic-lock token; an update sends it so a concurrent edit is refused, not overwritten.

Import

# Import by SOP id.
terraform import intutic_sop.deploys sp_0123456789abcdef