Resolve a gate
The Validate pane of a Studio plan lists every gate with its status chip (green / amber / red), the gate ID, and a detail string. Clicking the row opens the inspector against the offending node. This guide is the shape of the fix; the specifics per gate are in the Gate catalog.
1 · Read the detail
Section titled “1 · Read the detail”Every failed gate writes a detail string — for example @Analytics.dataCategory: #CUBE missing on cube node or source release state is C0. The detail names the condition, not the fix. Look up the gate ID in the Gate catalog for what the gate protects and where the fix belongs in the plan.
2 · Open the offending node
Section titled “2 · Open the offending node”The Validate row links into the plan canvas with the node pinned in the inspector. Errors focus on the single node that fails; warnings and source gates focus on the binding or the annotation set.
3 · Fix the cause
Section titled “3 · Fix the cause”Depending on the gate, the fix lands in one of three places:
- Plan graph. Add, remove, or rewire a node — breaking a cycle (
T-02), adding a DCL artifact (A-02), shortening a name (N-01). - Binding. Swap the source candidate for one with a higher release contract (
S-02), or bind the cube to a different released view entirely (S-01). - Annotations. Edit the view’s header annotations directly — add
@Analytics.dataCategory: #CUBE(C-02), change#NOT_REQUIREDto#CHECK(A-01), and so on.
4 · Regenerate
Section titled “4 · Regenerate”Hit Generate again. Atlas re-runs POST /api/atlas/studio/scaffold and re-evaluates the gate matrix. Every gate runs on every generation — there is no partial re-check.
5 · If the gate is a warning, override with a reason
Section titled “5 · If the gate is a warning, override with a reason”warning gates (currently S-02) are the only ones that accept an override at Validate time. An override is a written justification attached to the plan’s evidence trail; the 20-character minimum is enforced. Follow the contract described in Gates are non-bypassable — a sentence, not a two-word excuse. The override caps the plan’s achievable mode at one step below the mode the gate blocks; it does not make the gate green.
error gates cannot be overridden. Fix the cause or drop the node from the plan.
6 · Confirm the achievable mode
Section titled “6 · Confirm the achievable mode”After a regeneration, the Validate pane summary shows the new achievable quality mode: HEURISTIC_DRAFT, EVIDENCE_GROUNDED, ACTIVATION_CANDIDATE, or TRANSPORT_CANDIDATE. Transport is eligible only at TRANSPORT_CANDIDATE.