Using Valinor
Capabilities
Everything Valinor governs on your repo, in one place. Each capability is a collapsible row: expand it to see what it checks, preview how it behaves at each posture, and dial it Off, Advisory, or Enforced. Your choices accumulate into a complete governance.config.yml you can copy or download.
This page is a projection of the source of truth — it is generated directly from Valinor's capability registry, so it lists every governance concern with its default posture and dialability, and can never silently fall behind the code. (The site-freshness gate fails the build if it drifts.)
How the postures map
Off skips the gate. Advisory reports findings without blocking (the config value is warn). Enforced blocks the merge (the value is error). A few integrity-class gates (🔒) are locked to Enforced in code and can't be dialed down. The scaffolded process gates (research ledger, plan hygiene, empty-catch) start at Advisory — they report on every run; raise them to Enforced to block. Declaration-gated opt-ins start Off until you declare their config. Governance-meta checks (Valinor's self-checks) carry no consumer dial.
Compliance & accessibility
Docs & narrative
Governance meta
Release & deploy
Repo & process discipline
Security & dependencies
Sites & surfaces
Testing & API contracts
Using the builder
- Group by Domain or Lifecycle — the pivot re-groups every capability; the other dimension shows as the per-row tag.
- Copy gate — each expanded row copies just its own
gates:snippet, ready to paste. - Copy config / Download — the sidebar accumulates every posture you've changed into one config. By default it emits only the deltas (the gates you moved off their default); toggle all defaults to emit every gate explicitly.
For what each field means, see the config reference; for the per-command detail, the CLI reference.