Implement orbit-graph impact query (BFS with confidence floor and 200-node cap)#458
Merged
Merged
Conversation
…nd… [ORB-00316] Implement orbit-graph impact query (BFS with confidence floor and 200-node cap) Planned-By: codex
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.
Task
ORB-00316 — Implement orbit-graph impact query (BFS with confidence floor and 200-node cap)
Description
Problem
GRAPH_SPEC.md §9.5 defines impact: BFS over the union of inbound refs (callers) and outbound callees, plus relations for impl-driven edges. Default depth 3. Default confidence floor same_module. Returns a flat list of touched symbols ordered by graph distance, capped at 200 visited nodes.
Why It Matters
impact is the blast-radius query agents run before edits: 'what does changing this symbol affect?' It composes refs (P4.2) for inbound edges and callees (P4.3) for outbound edges into a single graph traversal, so it lands after both. The 200-node cap is the contract for keeping response sizes within context-window budgets — agents that need more coverage split into narrower queries from sub-nodes.
Constraints / Notes
Plan ID: P4.4. Depends on ORB-00315 (P4.2, refs) and ORB-00314 (P4.3, callees). Runs in parallel with P4.5.
Acceptance Criteria
Execution Summary
Click to expand
Outcome: success
Changes:
Assessment: Validated with cargo test -p orbit-graph query::impact, cargo test -p orbit-graph callees, cargo clippy -p orbit-graph -- -D warnings, and make ci-fast.
Validation
Branch Freshness
origin/agent-mainorbit/ORB-00316-6a13d019