Air traffic control for AI coding

Advanced Nool governance setup

Adopt Nool governance as a maturity ladder: begin with gating and policies, add trust after a proven track record, and enable role-based steering only when ownership is clear.

Use release workspace edges for ordering and contract edges for shared interfaces.
Verify a governance pack before installing it; policies activate automatically.
Keep invariants and playbooks explicit in each downstream project configuration.

nool config init-governance
nool admin pack verify <dir>

Ready- project configuration

This tested `nool.toml` starts fail-fast gating at blast radius 30, enables a trust curve, and adds two role-based steering gates: CISO review before pushing sensitive paths and architect review before solidifying high coupling.

[gating]
fail_fast = true
blast_block_threshold = 30

[trust]
enabled = true
base_trust = 0.5
auto_proceed_threshold = 0.8
auto_proceed_max_blast = 10

[[steer.points]]
point = "pre-push"
role = "ciso"
[[steer.points.triggers]]
signal = "sensitive_path"
paths = ["auth", "crypto", "identity", "billing", "secret"]

[[steer.points]]
point = "pre-solidify"
role = "architect"
[[steer.points.triggers]]
signal = "coupling_slope_gt"
value = 0.3

Multi-repository workspace

A `release` edge determines build and shipping order. A `contract` edge documents a shared contract but does not block ordering.

[[workspace.depends]]
from = "api-gateway"
on = "billing"
kind = "release"   # billing must ship first

[[workspace.depends]]
from = "web"
on = "api-gateway"
kind = "contract"  # shared contract only, no ordering

Adopt controls as a maturity ladder

Day 1: use default gating, shipped secret/PII policies, and warning-level invariants. In weeks 2–4, enable trust. Require acceptance-criteria review once teams write criteria consistently. Enable steering only after each role has a named owner. Add `workspace.toml` after the second repository.

Enterprise packs and extensions

A versioned `pack.toml` bundles policies, invariants, and playbooks. Verify before installation, then install it. The policy layer activates automatically; invariants and playbooks stay explicit and must be added once by each downstream team. Packs may require role gates; teams may tighten, never weaken, company controls. Custom policy files auto-load from `[aram] policies_path`; invariants use `[invariants.rule_definitions.<id>]`; playbooks compose existing verbs. Use `[[languages]]` for simple adapters or the WASM SDK for AST-level adapters.

nool admin pack verify <dir>
nool admin pack install <dir>