A release signal built from evidence, not opinion
Release-readiness intelligence is a later-stage capability. This screen shows the designed shape of it, computed from the demo project's real coverage, gate results and open findings.
Concept — future stage. The first release stops at pull-request generation. Test execution, defect intelligence and release readiness sit in the commercial stage of the roadmap. This is not a built capability; it is what the data already being collected makes possible.
The signal is derived, not declared. Every input below is a number SALC already holds because the lifecycle was governed on the way here.
- 2 quality principles failed (QP-03, QP-04)
- 1 unresolved gap on a high-risk requirement
- 2 open contradictions
- Human approval not recorded
35 of 37 chains trusted
86 of 147 cases
surfaced, awaiting a human decision
quality findings on high-risk requirements
What feeds the signal
- Quality gateREVIEW REQUIRED
- Human approvals0/3
- Automation pull requestNot generated
- Change impactNo change analysed
- Test executionNot in scope for the first release
Where this sits on the roadmap
Contracts, orchestrator, gateway, ingestion, product knowledge, test intelligence, quality principles, approvals, export
Azure DevOps publishing, Playwright TypeScript generation, GitHub pull requests, design-conformance demonstrator
Secure execution runner, results and defect intelligence, release readiness, enterprise connectors, visual canvas, SSO and RBAC
If the commercial stage never funds, Ring A plus Ring B is still a working product: it produces approved, traceable test cases, publishes them, and raises automation pull requests.