Repository Semantic Review v0.6
/mnt/data/cisg_repolumen_poc/mutation_slice
Technical evidence view →

Project Review

● 4 confirmed defects

Confirmed by current deterministic rules in the analyzed static scope.

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
29
Functions
4
Confirmed defects
16
Hotspots
9
State regions
162
Boundary calls
16
Motifs
34
Resolved calls

Review first

Review breadth is prioritization metadata, not defect truth.

#TargetBreadthFilesState coupledBoundaries
1
repo_semantic/historical_timeline.py
383024
2
repo_semantic/grounding.py
352022
3
repo_semantic/grounding.py
352022
4
repo_semantic/architecture_reconstruction.py
332021
5
repo_semantic/semantic_diff.py
322021
6
repo_semantic/execution_paths.py
271020
7
repo_semantic/semantic_diff.py
262020
8
repo_semantic/architecture_reconstruction.py
242016
9
repo_semantic/semantic_diff.py
222016
10
repo_semantic/execution_paths.py
211017
11
repo_semantic/execution_paths.py
211017
12
repo_semantic/semantic_diff.py
202015

Current findings

Confirmed defects: 4

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

SeverityClassTypeLocationSymbolEvidence statement
highdefectmutable_defaultrepo_semantic/incremental.py:19_injected_mutable_defaultMutable default argument can retain state across calls.
highdefectunreachable_statementrepo_semantic/incremental.py:21_injected_mutable_defaultStatement follows an unconditional terminator in the same lexical block.
mediumdefectmodule_import_cycle:Loaded modules form a static import cycle.
mediumdefectbare_exceptrepo_semantic/incremental.py:26_injected_bare_exceptBare except catches every exception type.
infohotspothigh_call_fanoutrepo_semantic/architecture_reconstruction.py:_flow_descriptionHigh static call fan-out; review as an orchestration/hotspot node.
infohotspothigh_call_fanoutrepo_semantic/architecture_reconstruction.py:_uncertaintiesHigh static call fan-out; review as an orchestration/hotspot node.
infohotspotboundary_heavyrepo_semantic/architecture_reconstruction.py:_uncertaintiesMany calls cross the resolved graph boundary.
infohotspothigh_call_fanoutrepo_semantic/architecture_reconstruction.py:reconstruct_architectureHigh static call fan-out; review as an orchestration/hotspot node.
infohotspothigh_call_fanoutrepo_semantic/execution_paths.py:build_execution_pathsHigh static call fan-out; review as an orchestration/hotspot node.
infohotspotboundary_heavyrepo_semantic/execution_paths.py:build_execution_pathsMany calls cross the resolved graph boundary.
infohotspothigh_call_fanoutrepo_semantic/grounding.py:build_grounding_catalogHigh static call fan-out; review as an orchestration/hotspot node.
infohotspotboundary_heavyrepo_semantic/grounding.py:build_grounding_catalogMany calls cross the resolved graph boundary.
infohotspothigh_call_fanoutrepo_semantic/historical_timeline.py:build_historical_timelineHigh static call fan-out; review as an orchestration/hotspot node.
infohotspotboundary_heavyrepo_semantic/historical_timeline.py:build_historical_timelineMany calls cross the resolved graph boundary.
infohotspothigh_call_fanoutrepo_semantic/limits.py:skip_reasonHigh static call fan-out; review as an orchestration/hotspot node.
infohotspotboundary_heavyrepo_semantic/limits.py:skip_reasonMany calls cross the resolved graph boundary.
infohotspothigh_call_fanoutrepo_semantic/semantic_diff.py:_lesson_invalidationsHigh static call fan-out; review as an orchestration/hotspot node.
infohotspotboundary_heavyrepo_semantic/semantic_diff.py:_lesson_invalidationsMany calls cross the resolved graph boundary.
infohotspothigh_call_fanoutrepo_semantic/semantic_diff.py:build_semantic_diffHigh static call fan-out; review as an orchestration/hotspot node.
infohotspotboundary_heavyrepo_semantic/semantic_diff.py:build_semantic_diffMany 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

MotifInstances
boundary_orchestration12
orchestration_fanout2
resource_scope1
read_modify_write1

Program structure

Resolved local calls: 34

Boundary calls: 162

State regions: 9

State writes: 7

Effect relations: 1

Open full node/data/state graph

Source identity

PathBytesSHA-256
repo_semantic/architecture_reconstruction.py51452c70301670ace276f0…
repo_semantic/execution_paths.py5894608725e724891c0bf5…
repo_semantic/grounding.py7189981aae9fc01d427317…
repo_semantic/historical_timeline.py27292693e3fd967ac481be…
repo_semantic/incremental.py10016f24db1f386eb42763…
repo_semantic/limits.py403936c30278003ea4891e…
repo_semantic/semantic_diff.py4890dafdcb13775c679731…

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