Skip to the result

ArchKeel.

Report · FAIL · commit adafb9683

Verdict: FAIL

FAIL

1 rule violated in 1 place, 0 unknown

A violation is a fact of this run. An unknown rule is not a pass.

Rules PASS
0
Rules FAIL
1
Rules UNKNOWN
0

Stated assumption: Code outside the scan roots, including test code, hands in no module object of the scan and writes no binding of a module or class of the scan.

Calls: 3 of 4 resolved (75.0%); 0 partly resolved, 1 builtin, 0 outside the scan, 0 unresolved.

An unresolved call has no proven target and is no edge. A rule that reads calls cannot decide from it and stays UNKNOWN; a rule of imports does not read it.

NEXT

  1. Remove 1 violated place. Evidence: 1.
  2. Every row behind this page: archkeel report --topology --output report.json --format json

Architecture

1 component, 3 modules. 0 with a violation, 0 with an open gap. This page shows one part of the system: its python modules. Another part has its own run and contract; a system document joins the parts into one page. 1 violation outside any component (the module has no owner in the contract): assign the package of its module to a component of the contract, a root package too. See the violations below. Open a box to see its parts; As-Is, Target and Diff switch the view.

Skip the Explorer

Component dependencies

How to read this report

Components are declared responsibility and ownership boundaries, not classes or files. Packages here are namespace groups; they do not prove a directory or __init__.py. Modules represent source units: in Python, normally a .py file, including __init__.py. Details shows recorded file paths and separates the view group from the code container. Component roles describe architecture responsibilities; an interface node describes a language interface, such as a Python Protocol.

Gold and the component glyph mark architecture boundaries. Blue document glyphs mark modules; grey folder glyphs mark namespace groups. Classes use purple compartments, interfaces use teal circles, enumerations use pink compartments. Functions use ƒ and methods use (). Visibility: + public, − private, # protected, ~ package, ? unknown. These conventions do not claim Python access enforcement. Border verdicts and edge styles are separate from element types. Mixins appear as their own classifier and use a directed edge distinct from inheritance. Use the relationship legend to filter edges.

As-Is uses observed source facts with declared boundaries for navigation. Target uses independent declarations; missing file paths remain undeclared. Diff uses recorded Core assessments. Select for details; double-click, press Enter or Open selected to explore one level. Breadcrumbs include the kind. Drag the background to pan; use Zoom or Fit overview to change scale. Arrows run from source to target. Allowed component imports are permissions, not proof of a call or import.

Worth a look

Legend

Violations

1 place in the code, 1 rule broken. One block for each place; a place lists each rule that fails there.

1

run imports demo.core.Client.run

  1. modulerun
  2. filedemo/core.py
  • IMPORTSline 20
  1. moduledemo.core.Client.run

Evidence: demo/core.py:20

  • Violates UML-TARGET-a2e40c5592b1b06a · uml target · cause: return annotation differs