Repository Semantic Review v1.0
/mnt/data/PSMR_Runtime_MVP_v1.0/demo_active_state/active_demo/source
Technical evidence view →

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?

3
Files
3
Functions
0
Confirmed defects
0
Hotspots
0
State regions
3
Boundary calls
0
Motifs
2
Resolved calls

Review first

Review breadth is prioritization metadata, not defect truth.

#TargetBreadthFilesState coupledBoundaries
1
app.py
5203
2
app.py
5203
3
tests/test_app.py
5203

Current findings

Confirmed defects: 0

Anomalies: 0

Hotspots: 0

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
No findings in the current static scope.

Impact Review

Direct means one-hop graph evidence. Derived means bounded resolved call paths plus shared-state coupling.

Functional shapes

MotifInstances
No motif candidates.

Program structure

Resolved local calls: 2

Boundary calls: 3

State regions: 0

State writes: 0

Effect relations: 0

Open full node/data/state graph

Source identity

PathBytesSHA-256
app.py157d56cd9c5c97d5342ea…
tests/__init__.py0e3b0c44298fc1c149a…
tests/test_app.py1525407cdc72d755fe2ba…

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