PLESTY's quality gate system ensures that every module meets consistent standards for correctness, security, and documentation. Gates are organized by scope and tier, running at different stages of development.
Gate overview
| Gate |
Name |
Scope |
Tier |
| 1 |
Metadata & Namespace |
SDK |
pixel |
| 2 |
Code Hygiene & Tooling |
SDK |
pixel |
| 3 |
API Interface Matching |
SDK |
nebula |
| 4 |
Data Layer Compliance |
SDK |
nebula |
| 5 |
Documentation Completeness |
SDK |
nebula |
| 6 |
Dependency Coexistence |
SDK |
nebula |
| 7 |
Automated Test Coverage |
SDK+CI |
quantum |
| 8 |
Semantic Versioning |
SDK+CI |
quantum |
| 9 |
Licensing Compliance |
SDK+CI |
quantum |
| 10 |
Vulnerability Audit |
SDK+CI |
quantum |
| 11 |
Docs Build |
SDK |
quantum |
| d1 |
Device API Pipeline |
Device |
quantum |
| d2 |
Device Status Contract |
Device |
quantum |
| d3 |
Device Docs |
Device |
quantum |
| e1 |
Experiment Contract |
Experiment |
quantum |
| e2 |
Experiment Persistence |
Experiment |
quantum |
| 12 |
Docs Deploy |
CI |
ci |
| 13 |
SAST Secret Detection |
CI |
ci |
| 14 |
Build & Release |
CI |
ci |
Gate tiers
- pixel — gates 1–2, runs pre-commit
- nebula — gates 1–6, runs pre-push
- quantum — gates 1–11 + d1–d3/e1–e2, full local verification
- ci — gates 1–14, runs in GitLab CI
Sections
| Page |
Description |
| Pixel & Nebula |
Gates 1–6 — fast checks for early development |
| Quantum |
Gates 7–11 + device/experiment gates |
| CI Only |
Gates 12–14 — deploy, security, and release |
Next steps