Skip to the result

ArchKeel.

Report · FAIL · commit 76f1a493d

Verdict: FAIL

FAIL

4 rules violated in 3 places, 1 unknown, 2 gaps with no rule

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

Rules PASS
5
Rules FAIL
4
Rules UNKNOWN
1
Gaps with no rule
2

Stated assumption: code outside the scan roots hands in no global or platform object and replaces no global, and addresses that a framework renders from data hold no javascript: code

NEXT

  1. Remove 3 violated places. Evidence: 1, 2, 3.
  2. Remove the cause that keeps the run open (1 gap): contract hygiene closed_world.observed_forbidden: architecture-contract.json/rules domain -> data: An observed component dependency is also ….
  3. Remove the cause that keeps the run open (1 gap): contract hygiene graph.drift: architecture-contract.json/components docs/architecture/shop.md (component graph): The marked component graph ….
  4. 1 job more: see the causes.
  5. Every row behind this page: archkeel report --topology --output report.json --format json

Architecture

4 components, 7 modules. 2 with a violation, 0 with an open gap. This page shows one part of the system: its typescript 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. 2 gaps 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

3 places in the code, 4 rules broken. One block for each place; a place lists each rule that fails there.

1

shop.src.domain.order.ts imports shop.src.data.local.ts

  1. componentdomain
  2. moduleshop.src.domain.order.ts
  3. filesrc/domain/order.ts
  • IMPORTSline 7
  1. componentdata
  2. moduleshop.src.data.local.ts
  3. filesrc/data/local.ts

Evidence: src/domain/order.ts:7

  • Violates DOMAIN-NO-DATA · forbidden dependency · cause: forbidden dependency · forbids: domain to data
  • Violates REQUIRES · complete requires · cause: undeclared component dependency · requires: app, presentation, data
2

Cycle of 2 members

2 members are in this cycle. Shortest closed path shown: 2 steps. Step 2 imports data, where step 1 starts.
StepFromToImports
1datadomainsrc/data/remote.ts:5, src/data/local.ts:5
2domaindatasrc/domain/order.ts:7
  • Violates COMPONENT-CYCLES · no component cycles · cause: dependency cycle
3

Cycle of 3 members

3 members are in this cycle. Shortest closed path shown: 3 steps. Step 3 imports src/data/local.ts, where step 1 starts.
StepFromToImports
1src/data/local.tssrc/domain/repository.tssrc/data/local.ts:5
2src/domain/repository.tssrc/domain/order.tssrc/domain/repository.ts:5
3src/domain/order.tssrc/data/local.tssrc/domain/order.ts:7
  • Violates MODULE-CYCLES · no module cycles · cause: dependency cycle

Unknown

1 rule cannot be decided, from 3 causes. An UNKNOWN rule is not a pass.

contract hygiene closed_world.observed_forbidden: architecture-contract.json/rules domain -> data: An observed component dependency is also …

1 named gap
What the core says

contract hygiene closed_world.observed_forbidden: architecture-contract.json/rules domain -> data: An observed component dependency is also forbidden.

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

1 named gap
What the core says

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

the UML target: 9 assessments cannot be decided: absent symbol: the symbol inventory is not complete, relationship endpoints cannot be …

1 rule

Holds UML-TARGET-a2e40c5592b1b06a

What the core says

the UML target: 9 assessments cannot be decided: absent symbol: the symbol inventory is not complete, relationship endpoints cannot be identified uniquely, unresolved calls site, unresolved references site

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.

2 of 4 components have a violation or a gap. All tables for 2 components. The others are in the Explorer. Every row: archkeel report --topology --output report.json --format json

WITH A VIOLATION · 2

componentdomain3 modules · uses 1 · used by 22 violationsFAIL
Modules: 3 of 3
Module FileException
shop.src.domain.order.tssrc/domain/order.ts1 3
shop.src.domain.repository.tssrc/domain/repository.ts3
shop.src.domain.index.tssrc/domain/index.ts
Imports of other components: 1 of 1
TargetImportsFirst evidence
data1src/domain/order.ts:7
Imports by other components: 2 of 2
SourceImportsFirst evidence
data2src/data/local.ts:5, src/data/remote.ts:5
presentation1src/presentation/page.ts:5
componentdata2 modules · uses 1 · used by 21 violationFAIL
Modules: 2 of 2
Module FileException
shop.src.data.local.tssrc/data/local.ts3
shop.src.data.remote.tssrc/data/remote.ts
Imports of other components: 1 of 1
TargetImportsFirst evidence
domain2src/data/local.ts:5, src/data/remote.ts:5
Imports by other components: 2 of 2
SourceImportsFirst evidence
app1src/main.ts:5
domain1src/domain/order.ts:7

Rules

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

The rules that hold, by kind: one line each

RULES THAT HOLD

complete assignment · 1 rule
  • ASSIGNMENT
complete external scope · 1 rule
  • EXTERNAL-COMPLETE
external dependency scope · 1 rule
  • EXTERNAL-SHOP
root layout · 1 rule
  • LAYOUT
sibling isolation · 1 rule
  • DATA-PEERS