Ownership
Bound potential impact from evidence without deciding or implementing the change.
The workflow below implements the shared Codebase Intelligence evidence contract.
Workflow
- Ask one narrow structural question, define its scope, and state the decision it supports.
- Detect whether an optional code-intelligence runtime is available through callable tools only. Do not install a runtime, do not run
codegraph init, and do not create .codegraph/ without explicit authorization.
- Use the narrowest symbol, relation, or targeted search that can answer the question; expand only to close a named evidence gap.
- Use an explicit fallback when runtime evidence is unavailable or inconclusive: inspect targeted symbols, search, imports, references, tests, configuration, and direct reads. A textual match is not proof of a caller, callee, or owner.
- Keep an evidence ledger for every material claim: claim, status (
observed, inferred, or unresolved), source, location, confidence, and relevance.
- Stop at sufficiency when traceable evidence answers the question, critical dependencies are checked, gaps are classified, and further reading is unlikely to change the immediate decision. Hand off to the next owner.
Output contract
- proposed change surface;
- direct dependents;
- transitive or inferred dependents;
- affected contracts;
- affected user or runtime paths;
- affected tests and fixtures;
- risk classification;
- unresolved impact;
- source references;
Does not own
Implementation decisions, safety approval, or code changes; this method does not decide the change.
1---2name: analyzing-change-blast-radius3description: Use when you need evidence-bounded potential impact for a proposed change before deciding how to make it.4---56## Ownership78Bound potential impact from evidence without deciding or implementing the change.910The workflow below implements the shared Codebase Intelligence evidence contract.1112## Workflow13141. Ask one narrow structural question, define its scope, and state the decision it supports.152. Detect whether an optional code-intelligence runtime is available through callable tools only. Do not install a runtime, do not run `codegraph init`, and do not create `.codegraph/` without explicit authorization.163. Use the narrowest symbol, relation, or targeted search that can answer the question; expand only to close a named evidence gap.174. Use an explicit fallback when runtime evidence is unavailable or inconclusive: inspect targeted symbols, search, imports, references, tests, configuration, and direct reads. A textual match is not proof of a caller, callee, or owner.185. Keep an evidence ledger for every material claim: claim, status (`observed`, `inferred`, or `unresolved`), source, location, confidence, and relevance.196. Stop at sufficiency when traceable evidence answers the question, critical dependencies are checked, gaps are classified, and further reading is unlikely to change the immediate decision. Hand off to the next owner.2021## Output contract2223- proposed change surface;24- direct dependents;25- transitive or inferred dependents;26- affected contracts;27- affected user or runtime paths;28- affected tests and fixtures;29- risk classification;30- unresolved impact;31- source references;3233## Does not own3435Implementation decisions, safety approval, or code changes; this method does not decide the change.
jhonatan-oliveiradev