aSPARK-ci
Gate and policy enforcement inside existing CI/CD platforms — not a replacement for them.
aSPARK never replaces CI/CD. aSPARK-ci brings gate and policy enforcement to where the pipeline already runs: GitHub Actions, GitLab CI, Azure DevOps, Jenkins.
That makes the gate state the same locally and in the build — and a release missing evidence fails in the pipeline instead of in a reviewer's memory.
- ◆
Enforcement in existing platforms
GitHub Actions, GitLab CI, Azure DevOps, Jenkins — a step in the pipeline you already have, not an engine of its own.
- ◆
Release validation
Checks before release whether gates are met and policy rules honoured — naming the policy and rule behind each finding.
- ◆
Builds on graph and policy
Uses graph and policy as its data source. Without both there is nothing to check.
This product is planned, not implemented. It sits on the roadmap behind what Core has to prove first — a sibling of aSPARK-insights, which advances independently of it.
Each product has one responsibility and stable interfaces. A weakness in one must never require changes in another.
Does this fit your delivery process?
Start with Core on a pilot project. The workflow, knowledge graph and policy packs are all open on GitHub.
No public repository yet.