Build Week: Correlate cross-agent incident lifecycle - #53
Merged
CodeBuildder merged 2 commits intoJul 18, 2026
Merged
Conversation
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
Turns explicitly related Argus and Phoenix findings into one inspectable Sentinel incident lifecycle while keeping standalone evidence out of incident counts.
Why
Sentinel previously displayed SOG findings and SOG incidents side by side without enforcing a correlation contract. This allowed a Phoenix evidence count to look like a Phoenix incident even when no scenario-backed incident existed.
Correlation rules
Sentinel creates a derived correlated case only when:
correlation_id; andTime proximity, matching severity, and similar resource names never fabricate a relationship.
Changes
Verification
5 passedgit diff --checkpassedLive producer proof
The actual Argus and Phoenix World Model clients published two explicitly non-live records with correlation ID
build-week-case-20260718. Sentinel produced exactly one case:resolvedcriticalargus,phoenix2replayed,simulatorThis proves cross-agent correlation without presenting deterministic demo evidence as observed production telemetry.
Dependencies
After #51 merges, this PR should be retargeted to
main.Closes #52