Docs · Issues & drift
Issues, drift & heal
Part of Ops — Issues are judgments over the graph and its Events.
Because the product is a graph, quality is checkable — and much of it is repairable.
Traditional software drifts silently: copy falls out of translation, brand tokens rot into raw hex, SEO metadata goes stale, runs hang. Closure runs drift scans against the graph, opens Issues as first-class DataObjects, and applies tiered heal — with promotion gated on what's still open.
Drift scans
Scans are ordinary governed workflows. Run them from Issues in the console, from your IDE, or on a schedule (Scale).
| Scan | Watches for |
|---|---|
| Ops | Orphaned soft-starts, stale runs, failures, waiting-step SLA, failed integrations |
| i18n | Missing, orphaned, stale, or overflowing locale strings across content bundles |
| Discoverability | Missing/overlong titles and descriptions, OG images, AI policy |
| Brand | Unbound design systems, off-kit components, raw hex where tokens belong |
| Suite | Ops + i18n + discoverability + brand in one pass |
| Contracts | Form framing/modes, component kinds, client scripts, unbound workflows |
| Library | Organism components that don't cite a library component |
| Goals | Stale, thin, or duplicate goals; no active goal |
Each finding becomes an Issue with severity low → critical and a lifecycle: open → acknowledged → resolved / wontfix.
Tiered heal
Not every fix deserves the same autonomy. Heal actions are tiered:
- Tier 0 — programmatic. Deterministic repairs: cancel an orphaned soft-start, truncate overlong SEO metadata, swap raw hex for design tokens, bind a library component.
- Tier 1 — model-assisted. Batch fixes where an LLM drafts the repair (e.g. filling locale gaps).
- Tier 2 — IDE / governed build. Structural changes drafted for a governed build.
- Tier 3 — human only. The system files the Issue and waits for you.
Your plan caps how far autonomy goes (heal_tier_max); everything above the cap stays a manual triage decision. Every heal is an Event.
The promote gate
On Team and above, promotion between environments is blocked while high or critical Issues remain open on the Experience. Quality isn't a dashboard you glance at — it's a gate the graph enforces.
Per plan
| Plan | Scans | Heal | Gate |
|---|---|---|---|
| Build | Ops only | Manual triage | — |
| Team | Core suite | Tiers 0–1 | Yes |
| Scale | Full suite + autonomous schedule | Tiers 0–2 | Yes |
See Plans for the full ladder.