The quantum standard is the full local verification tier. It includes all nebula gates plus gates 7–11 and the device/experiment-specific gates (d1–d3, e1–e2). This is the default standard for plesty check.
Gates 7–11
Gate 7: Automated Test Coverage
Runs pytest with coverage and enforces a minimum threshold.
What it checks:
pytest --cov=plesty --cov-fail-under=80- Test coverage is at least 80%
- Tests actually run and pass
Why it matters:
Adequate test coverage ensures your module works correctly and continues to work as changes are made.
Gate 8: Semantic Versioning
Reminds you to tag the current version before publishing.
What it checks:
- Current version has a corresponding git tag
- Version follows semver conventions
Why it matters:
Semantic versioning communicates the nature of changes to users and enables automated release workflows.
Gate 9: Licensing Compliance
Runs REUSE lint to verify license information.
What it checks:
- Every file has a license header or
.licensecompanion - REUSE configuration is valid
- Authorship information is current
Why it matters:
Proper licensing is required for open-source compliance and the GitLab-for-Open-Source program.
Gate 10: Vulnerability Audit
Runs pip-audit to check for known vulnerabilities.
What it checks:
- All dependencies are scanned against vulnerability databases
- No known CVEs in the dependency tree
Why it matters:
Using dependencies with known vulnerabilities puts users at risk. Network access is required for this gate.
Gate 11: Docs Build
Builds Sphinx documentation and checks for warnings.
What it checks:
- Sphinx build completes without errors
- Zero documentation warnings
Why it matters:
Broken documentation is worse than no documentation. This gate is skipped in CI (local-only).
Device gates
Gate d1: Device API Pipeline
Runs 8 mock pipeline gates against the device implementation. See Gate d1 for details.
Gate d2: Device Status Contract
Ensures telemetry overrides preserve schema annotations.
What it checks:
- Device state keys match schema definitions
- Telemetry values are within schema-specified ranges
- Type annotations are preserved
Gate d3: Device Docs
Generates zero-effort device documentation from doc_model().
What it checks:
doc_model()produces valid output- Documentation covers all parameters and operations
Experiment gates
Gate e1: Experiment Contract
Validates that the experiment implements the required contract.
What it checks:
- Experiment class exists
- Required methods are present
- Device interaction follows conventions
Gate e2: Experiment Persistence
Ensures experiments use save_result() for data persistence.
What it checks:
- No ad-hoc file I/O for measurement data
- All persistence goes through
save_result
Running quantum
# Default standard is quantum
uv run plesty checkNext steps
- Explore CI-only gates — deploy, security, and release
- Set up the CI pipeline