Add classifier fail-closed policy foundation#51
Merged
yanny-sec merged 4 commits intoJun 18, 2026
Merged
Conversation
Contributor
|
The PR looks good so far. A few things:
|
Contributor
Author
Thanks for the feedback, I added embedded migration tests for a populated pre-002 DB, made migration 002 recover cleanly after an interrupted run, and switched setup.py to parameterized queries. |
yanny-sec
previously approved these changes
Jun 17, 2026
Contributor
|
@Muhammad-usman92 please run |
Contributor
Author
|
yanny-sec
approved these changes
Jun 18, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds the status-first foundation for classifier failures. Classifier outages are now represented as ERROR verdicts with empty MAD codes, backed by additive proto fields, generated bindings, ledger-tracked migrations, store/API support, and engine error semantics that no longer fabricate benign M0 results.
Test plan
go test ./...frombackendChecklist