Gate catalog
The gate catalog lists every validation gate the Studio pipeline can emit. Each entry documents what the gate checks, when it fires, the exact failure detail, and the resolution path.
Gates are generated from the registry in internal/sap/validate/validate.go. The ID prefix determines the category: N = naming, S = source, A = authorization, C = annotation, T = transport.
For the general resolution flow, see How to resolve a gate. For the rule itself — why gates cannot be skipped silently — see Gates are non-bypassable.
Catalog
Section titled “Catalog”| ID | Name | Category | Severity | Blocks mode |
|---|---|---|---|---|
| N-01 | CDS entity name length | naming | error | HEURISTIC_DRAFT |
| S-01 | Source candidate per cube | source | error | HEURISTIC_DRAFT |
| S-02 | Selected source is C1 or C2 | source | warning | ACTIVATION_CANDIDATE |
| A-01 | No #NOT_REQUIRED on business views | authorization | error | EVIDENCE_GROUNDED |
| A-02 | DCL role present for #CHECK views | authorization | error | EVIDENCE_GROUNDED |
| C-02 | Cube has @Analytics.dataCategory #CUBE | annotation | error | EVIDENCE_GROUNDED |
| C-03 | Query has @Analytics.query true | annotation | error | EVIDENCE_GROUNDED |
| T-02 | Activation order has no cycles | transport | error | HEURISTIC_DRAFT |
Severity and quality mode
Section titled “Severity and quality mode”An error gate drops the plan’s achievable mode to HEURISTIC_DRAFT until resolved. A warning gate caps the achievable mode at one step below the mode it blocks — a red S-02 caps the plan at EVIDENCE_GROUNDED.
Quality modes, lowest to highest: HEURISTIC_DRAFT → EVIDENCE_GROUNDED → ACTIVATION_CANDIDATE → TRANSPORT_CANDIDATE. Only TRANSPORT_CANDIDATE plans are eligible to emit a transport.