Skip to content

Disclose stateless-signal limitation in README #1

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
abishekgiri merged 1 commit into from
Jun 6, 2026
Merged

Disclose stateless-signal limitation in README #1

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 7 additions & 0 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -100,6 +100,13 @@ No ReleaseGate server access is required to verify.
hello@releasegate.io.
- It does not yet support Kubernetes admission control. See the
main repo for the roadmap.
- The risk score in stateless customer-side runs does not include
historical signal enrichment (churn, hotspot density, prior-
incident proximity). Those signals require persistent history
across runs, which the customer CI runner does not have. The
decision gate, policy evaluation, and signed attestation are
fully functional; only the risk-score amplification is reduced.
Server-side dashboard runs include the full signal set.

## Security

Expand Down
Loading