Skip to the result

ArchKeel.

Report · FAIL · commit 7ac3a66c3

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
9
Rules FAIL
1
Rules UNKNOWN
0

NEXT

  1. Remove 1 violated place. Evidence: 1.
  2. 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.

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

shop.domain.repository imports dart.io

  1. componentdomain
  2. moduleshop.domain.repository
  3. filelib/domain/repository.dart
  • IMPORTSline 6
  1. moduledart.io

Evidence: lib/domain/repository.dart:6

  • Violates DEP-DOMAIN-NO-DART-IO · forbidden dependency · cause: forbidden dependency · forbids: domain to

Components with an exception

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
Modules: 3 of 3
Module FileException
shop.domain.repositorylib/domain/repository.dart1
shop.domain.domainlib/domain/domain.dart
shop.domain.entitieslib/domain/entities.dart
Imports of other components: 1 of 1
TargetImportsFirst evidence
outside the contract2lib/domain/repository.dart:5, lib/domain/repository.dart:6
Imports by other components: 2 of 2
SourceImportsFirst evidence
data3lib/data/http_order_repository.dart:8, lib/data/http_order_repository.dart:9
presentation2lib/presentation/order_page.dart:9, lib/presentation/order_tile.dart:6

Rules

9 rules hold, 0 rules declare a permission, 1 fail, 0 are unknown.

The rules that hold, by kind: one line each

RULES THAT HOLD

complete assignment · 1 rule
  • ASSIGNMENT-COMPLETE
complete external scope · 1 rule
  • EXTERNAL-COMPLETE
complete requires · 1 rule
  • REQUIRES-COMPLETE
external dependency scope · 2 rules
  • EXTERNAL-FLUTTER-UI
  • EXTERNAL-HTTP-DATA
interface boundary · 1 rule
  • INTERFACE-BOUNDARY
no component cycles · 1 rule
  • COMPONENT-NO-CYCLES
root layout · 1 rule
  • ROOT-LAYOUT
sibling isolation · 1 rule
  • DATA-PLATFORMS-ISOLATED