Project Review
● No confirmed defects
Within the current Python static-analysis scope; this is not a proof of total correctness.
Analysis cache: cache_disabled
Start here: review confirmed findings first; then inspect the highest review-breadth targets before making broad changes.
What this answers
What needs attention?
What should I review if I change this?
Where is the evidence?
7
Files
27
Functions
0
Confirmed defects
16
Hotspots
9
State regions
160
Boundary calls
16
Motifs
34
Resolved calls
Review first
Review breadth is prioritization metadata, not defect truth.
| # | Target | Breadth | Files | State coupled | Boundaries |
|---|---|---|---|---|---|
| 1 | repo_semantic/historical_timeline.py | 38 | 3 | 0 | 24 |
| 2 | repo_semantic/grounding.py | 35 | 2 | 0 | 22 |
| 3 | repo_semantic/grounding.py | 35 | 2 | 0 | 22 |
| 4 | repo_semantic/architecture_reconstruction.py | 33 | 2 | 0 | 21 |
| 5 | repo_semantic/semantic_diff.py | 32 | 2 | 0 | 21 |
| 6 | repo_semantic/execution_paths.py | 27 | 1 | 0 | 20 |
| 7 | repo_semantic/semantic_diff.py | 26 | 2 | 0 | 20 |
| 8 | repo_semantic/architecture_reconstruction.py | 24 | 2 | 0 | 16 |
| 9 | repo_semantic/semantic_diff.py | 22 | 2 | 0 | 16 |
| 10 | repo_semantic/execution_paths.py | 21 | 1 | 0 | 17 |
| 11 | repo_semantic/execution_paths.py | 21 | 1 | 0 | 17 |
| 12 | repo_semantic/semantic_diff.py | 20 | 2 | 0 | 15 |
Current findings
Confirmed defects: 0
Anomalies: 0
Hotspots: 16
A hotspot means “review-worthy,” not “wrong.” Unknown remains unknown.
Scope
Repository → semantic graph → data/state closure → impact → findings
Python-only, static-first. Dynamic dispatch, reflection, native behavior, precise runtime path probability, and concurrency remain outside the current strong claim.
Findings
| Severity | Class | Type | Location | Symbol | Evidence statement |
|---|---|---|---|---|---|
| info | hotspot | high_call_fanout | repo_semantic/architecture_reconstruction.py: | _flow_description | High static call fan-out; review as an orchestration/hotspot node. |
| info | hotspot | high_call_fanout | repo_semantic/architecture_reconstruction.py: | _uncertainties | High static call fan-out; review as an orchestration/hotspot node. |
| info | hotspot | boundary_heavy | repo_semantic/architecture_reconstruction.py: | _uncertainties | Many calls cross the resolved graph boundary. |
| info | hotspot | high_call_fanout | repo_semantic/architecture_reconstruction.py: | reconstruct_architecture | High static call fan-out; review as an orchestration/hotspot node. |
| info | hotspot | high_call_fanout | repo_semantic/execution_paths.py: | build_execution_paths | High static call fan-out; review as an orchestration/hotspot node. |
| info | hotspot | boundary_heavy | repo_semantic/execution_paths.py: | build_execution_paths | Many calls cross the resolved graph boundary. |
| info | hotspot | high_call_fanout | repo_semantic/grounding.py: | build_grounding_catalog | High static call fan-out; review as an orchestration/hotspot node. |
| info | hotspot | boundary_heavy | repo_semantic/grounding.py: | build_grounding_catalog | Many calls cross the resolved graph boundary. |
| info | hotspot | high_call_fanout | repo_semantic/historical_timeline.py: | build_historical_timeline | High static call fan-out; review as an orchestration/hotspot node. |
| info | hotspot | boundary_heavy | repo_semantic/historical_timeline.py: | build_historical_timeline | Many calls cross the resolved graph boundary. |
| info | hotspot | high_call_fanout | repo_semantic/limits.py: | skip_reason | High static call fan-out; review as an orchestration/hotspot node. |
| info | hotspot | boundary_heavy | repo_semantic/limits.py: | skip_reason | Many calls cross the resolved graph boundary. |
| info | hotspot | high_call_fanout | repo_semantic/semantic_diff.py: | _lesson_invalidations | High static call fan-out; review as an orchestration/hotspot node. |
| info | hotspot | boundary_heavy | repo_semantic/semantic_diff.py: | _lesson_invalidations | Many calls cross the resolved graph boundary. |
| info | hotspot | high_call_fanout | repo_semantic/semantic_diff.py: | build_semantic_diff | High static call fan-out; review as an orchestration/hotspot node. |
| info | hotspot | boundary_heavy | repo_semantic/semantic_diff.py: | build_semantic_diff | Many calls cross the resolved graph boundary. |
Impact Review
Direct means one-hop graph evidence. Derived means bounded resolved call paths plus shared-state coupling.
Functional shapes
| Motif | Instances |
|---|---|
| boundary_orchestration | 12 |
| orchestration_fanout | 2 |
| resource_scope | 1 |
| read_modify_write | 1 |
Program structure
Resolved local calls: 34
Boundary calls: 160
State regions: 9
State writes: 7
Effect relations: 1
Source identity
| Path | Bytes | SHA-256 |
|---|---|---|
| repo_semantic/architecture_reconstruction.py | 5145 | 2c70301670ace276f0… |
| repo_semantic/execution_paths.py | 5894 | 608725e724891c0bf5… |
| repo_semantic/grounding.py | 7189 | 981aae9fc01d427317… |
| repo_semantic/historical_timeline.py | 2729 | 2693e3fd967ac481be… |
| repo_semantic/incremental.py | 644 | 94c006ad1e6bb1857d… |
| repo_semantic/limits.py | 4039 | 36c30278003ea4891e… |
| repo_semantic/semantic_diff.py | 4890 | dafdcb13775c679731… |
Epistemic boundary
observed
- Python AST definitions
- imports
- call syntax
- control syntax
- source spans
- local file hashes
- SSA-like local definitions/uses
- self/cls/explicit-global state accesses
- module-binding reads
- explicit raise/except syntax
- definition-time Python name aliases
strongly_inferred
- local call target resolution
- parameter-container state regions
- effect hints
- branch/loop phi merges
- explicit exception catch matching
- structural motif candidates
unresolved
- runtime dispatch
- reflection
- native extension behavior
- external library semantics
- precise heap points-to beyond definition-time alias
- dynamic exception behavior from calls
- concurrency semantics