Every row behind this page: archkeel report --topology --output report.json --format json
Architecture
4 components, 9 modules. 1 with a violation, 0 with an open gap. This page shows one part of the system: its dart modules. Another part has its own run and contract; a system document joins the parts into one page. Open a box to see its parts; As-Is, Target and Diff switch the view.
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.
Modules, files and imports of each component with an exception
Open a component for its modules and files, and for its imports with file and line. The frame holds no level below a file.
1 of 4 components have a violation or a gap. All tables for 1 component. The others are in the Explorer. Every row: archkeel report --topology --output report.json --format json
WITH A VIOLATION · 1
componentdomain3 modules · uses 0 · used by 21 violationFAIL