Skip to the result

ArchKeel.

Report · FAIL · commit 18a2d2a8e

Verdict: FAIL

FAIL

1 rule violated in 1 place, 0 unknown, 1 gap with no rule

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

Rules PASS
11
Rules FAIL
1
Rules UNKNOWN
0
Gaps with no rule
1

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: 16 of 57 resolved (28.1%); 0 partly resolved, 10 builtin, 10 outside the scan, 21 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. Remove the cause that keeps the run open (1 gap): contract hygiene graph.drift: architecture-contract.json/components docs/target.md (component graph): The marked component graph differs ….
  3. Every row behind this page: archkeel report --topology --output report.json --format json

Architecture

9 components, 25 modules. 1 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 gap of the run name no component: see Unknown. 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

orders.api imports orders.storage

  1. componententry
  2. moduleorders.api
  3. fileorders/api.py
  • IMPORTSline 8
  1. componentReceipt repository
  2. moduleorders.storage
  3. fileorders/storage/__init__.py

Evidence: orders/api.py:8

  • Violates REQUIRES-COMPLETE · complete requires · cause: undeclared component dependency · requires: entry, checkout

Unknown

The run is not decided, and a run that is not decided is not a pass.

contract hygiene graph.drift: architecture-contract.json/components docs/target.md (component graph): The marked component graph differs …

1 named gap
What the core says

contract hygiene graph.drift: architecture-contract.json/components docs/target.md (component graph): The marked component graph differs from observed imports; drawn and not found: none; found and not drawn: entry->storage.

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 9 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

componententry2 modules · uses 4 · used by 01 violationFAIL
Modules: 2 of 2
Module FileException
orders.apiorders/api.py1
ordersorders/__init__.py
Imports of other components: 4 of 4
TargetImportsFirst evidence
Checkout operation3orders/api.py:4, orders/api.py:5
common1orders/api.py:6
pricing1orders/api.py:7
Receipt repository1orders/api.py:8

Rules

11 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 · 3 rules
  • ASSIGNMENT-COMPLETE
  • checkout:ASSIGNMENT-COMPLETE
  • storage:ASSIGNMENT-COMPLETE
complete requires · 2 rules
  • checkout:REQUIRES-COMPLETE
  • storage:REQUIRES-COMPLETE
interface boundary · 3 rules
  • INTERFACE-BOUNDARY
  • checkout:INTERFACE-BOUNDARY
  • storage:INTERFACE-BOUNDARY
no component cycles · 3 rules
  • COMPONENT-NO-CYCLES
  • checkout:COMPONENT-NO-CYCLES
  • storage:COMPONENT-NO-CYCLES