Repository observation

F-architecture

Candidate 6c2989a12dd35cdc29b0ccafa8ec6166d43a3560 Source 107dff0e0ba5f55cf68dd2897d438088894433877fedce095d58c30dd3ceaac3 Dirty True

Independent verdicts

PASS

Scan complete

observation_complete

All source files under shop were read and parsed; no source file beside them was read.

PASS

Rules followed

declared_rules

No declared-rule violation was found.

NOT APPLICABLE

Change as declared

expectation_fulfilled

Report mode does not evaluate a published expectation.

One repository snapshot. This report checks declared rules, not change against an earlier revision or runtime behavior. 4 recorded analysis limits; 7 of 59 calls unresolved. These counts are not declared-rule violations.

Check evidence

Failures

None.

Diagnostics

None.

Component dependencies

How to read this report

In the component diagram, connections show observed imports and which components depend on each other. Select a component or connection for details; double-click, press Enter, or use Open selected to explore one level. A circle marks a provided interface; a socket marks a declared dependency. Arrows point from importer to provider. Teal means the displayed imports were checked with no violation or relevant UNKNOWN; red means a rule fails, amber means a decision is needed, and grey shows imports within a component. Unassigned modules and physical folders are navigation only; they do not create component boundaries or owners. UNKNOWN findings remain in the report's evidence sections; Details shows evidence for the selected item. The Actual view lists observed modules. Target connections show declarations, not observed imports or execution order. Diff keeps violations, UNKNOWN evidence, unmapped modules, and absent targets distinct. The import evidence below works without JavaScript.

Declared-rule violations

None.

Declared rules · 39

PASS requires evidence that this rule was checked. Permissions define allowed paths; they are not checks. FAIL may also include undecided evidence.

Rule	Kind	Status	Violations / undecided	Details
`APP-TYPES-NOT-DICT`	boundary_types	PASS	0 violations · 0 undecided	Scope, decision and evidence Decider architect Rationale shop.app's functions take and return typed models, never a bare dict standing in for one. Provenance `docs/architecture/shop.md` Scope root Components app Assessment The evaluator completed this rule's observed scope without violations.
`ASSIGNMENT-COMPLETE`	complete_assignment	PASS	0 violations · 0 undecided	Scope, decision and evidence Decider architect Rationale A module without one owning component escapes every boundary rule. Provenance `docs/architecture/shop.md` Scope root Components — Assessment The evaluator completed this rule's observed scope without violations.
`COMPONENT-NO-CYCLES`	no_component_cycles	PASS	0 violations · 0 undecided	Scope, decision and evidence Decider architect Rationale Components stay layered so each one can be reviewed and replaced in dependency order. Provenance `docs/architecture/shop.md` Scope root Components — Assessment The evaluator completed this rule's observed scope without violations.
`CONSTRUCT-NO-ANY`	forbidden_construct	PASS	0 violations · 0 undecided	Scope, decision and evidence Decider architect Rationale A value that crosses a module boundary carries a type the reader can follow; Any hides exactly what the boundary exists to state. Provenance `docs/architecture/shop.md` Scope root Components — Assessment The evaluator completed this rule's observed scope without violations.
`CONSTRUCT-NO-ASSERT`	forbidden_construct	PASS	0 violations · 0 undecided	Scope, decision and evidence Decider architect Rationale Invariants are checked where values are built, because assert statements vanish under python -O. Provenance `docs/architecture/shop.md` Scope root Components — Assessment The evaluator completed this rule's observed scope without violations.
`CONSTRUCT-NO-BROAD-EXCEPT`	forbidden_construct	PASS	0 violations · 0 undecided	Scope, decision and evidence Decider architect Rationale Failures stay typed and visible; only the CLI error boundary, main's own body, turns any failure into an exit code. Provenance `docs/architecture/shop.md` Scope root Components — Assessment The evaluator completed this rule's observed scope without violations.
`CONSTRUCT-NO-DYNAMIC`	forbidden_construct	PASS	0 violations · 0 undecided	Scope, decision and evidence Decider architect Rationale Static architecture evidence remains explicit and mechanically traceable. Provenance `docs/architecture/shop.md` Scope root Components — Assessment The evaluator completed this rule's observed scope without violations.
`CONSTRUCT-NO-PLACEHOLDER`	forbidden_construct	PASS	0 violations · 0 undecided	Scope, decision and evidence Decider architect Rationale A function whose body is pass, ellipsis or a lone NotImplementedError reports capability it does not have, and its callers are written against that promise. Provenance `docs/architecture/shop.md` Scope root Components — Assessment The evaluator completed this rule's observed scope without violations.
`CONSTRUCT-NO-STRING-LITERAL-COMPARE`	forbidden_construct	PASS	0 violations · 0 undecided	Scope, decision and evidence Decider architect Rationale A closed vocabulary is an enum or Literal the type checker follows; a value compared with a string literal is a vocabulary nobody declared. Provenance `docs/architecture/shop.md` Scope root Components — Assessment The evaluator completed this rule's observed scope without violations.
`DEP-APP-ALLOWS-MODEL`	allowed_dependency	DECLARATION	0 violations · 0 undecided	Scope, decision and evidence Decider architect Rationale Use cases construct orders from domain values. Provenance `docs/architecture/shop.md` Scope root Components app, model Assessment Permission declaration; it does not evaluate conformance.
`DEP-APP-ALLOWS-STORE`	allowed_dependency	DECLARATION	0 violations · 0 undecided	Scope, decision and evidence Decider architect Rationale Use cases persist and load orders through the repository. Provenance `docs/architecture/shop.md` Scope root Components app, store Assessment Permission declaration; it does not evaluate conformance.
`DEP-APP-NO-CLI`	forbidden_dependency	PASS	0 violations · 0 undecided	Scope, decision and evidence Decider architect Rationale Use cases remain callable without command-line orchestration. Provenance `docs/architecture/shop.md` Scope root Components app, cli Assessment The evaluator completed this rule's observed scope without violations.
`DEP-APP-NO-RENDER`	forbidden_dependency	PASS	0 violations · 0 undecided	Scope, decision and evidence Decider architect Rationale Use cases return typed values; only the composition root decides how to project them. Provenance `docs/architecture/shop.md` Scope root Components app, render Assessment The evaluator completed this rule's observed scope without violations.
`DEP-APP-NO-STORE-BACKEND`	forbidden_dependency	PASS	0 violations · 0 undecided	Scope, decision and evidence Decider architect Rationale The file layout behind the repository is the store's own business; use cases reach persistence through OrderRepository, never through its backend. Provenance `docs/architecture/shop.md` Scope root Components app, backend, store Assessment The evaluator completed this rule's observed scope without violations.
`DEP-APP-NO-STORE-SQLITE`	forbidden_dependency	PASS	0 violations · 0 undecided	Scope, decision and evidence Decider architect Rationale Only the maintenance use case may run store housekeeping; ordinary order use cases stay on the repository. Provenance `docs/architecture/shop.md` Scope root Components api, app, store Assessment The evaluator completed this rule's observed scope without violations.
`DEP-CLI-ALLOWS-APP`	allowed_dependency	DECLARATION	0 violations · 0 undecided	Scope, decision and evidence Decider architect Rationale The composition root invokes the order use cases. Provenance `docs/architecture/shop.md` Scope root Components app, cli Assessment Permission declaration; it does not evaluate conformance.
`DEP-CLI-ALLOWS-RENDER`	allowed_dependency	DECLARATION	0 violations · 0 undecided	Scope, decision and evidence Decider architect Rationale The composition root prints the rendered order. Provenance `docs/architecture/shop.md` Scope root Components cli, render Assessment Permission declaration; it does not evaluate conformance.
`DEP-CLI-NO-MODEL`	forbidden_dependency	PASS	0 violations · 0 undecided	Scope, decision and evidence Decider architect Rationale The composition root reaches domain values only through the use cases it calls. Provenance `docs/architecture/shop.md` Scope root Components cli, model Assessment The evaluator completed this rule's observed scope without violations.
`DEP-CLI-NO-STORE`	forbidden_dependency	PASS	0 violations · 0 undecided	Scope, decision and evidence Decider architect Rationale The composition root reaches persistence only through the use cases it calls. Provenance `docs/architecture/shop.md` Scope root Components cli, store Assessment The evaluator completed this rule's observed scope without violations.
`DEP-MODEL-NO-APP`	forbidden_dependency	PASS	0 violations · 0 undecided	Scope, decision and evidence Decider architect Rationale Value types remain reusable without depending on the use cases that construct them. Provenance `docs/architecture/shop.md` Scope root Components app, model Assessment The evaluator completed this rule's observed scope without violations.
`DEP-MODEL-NO-CLI`	forbidden_dependency	PASS	0 violations · 0 undecided	Scope, decision and evidence Decider architect Rationale Value types remain independent of command-line composition. Provenance `docs/architecture/shop.md` Scope root Components cli, model Assessment The evaluator completed this rule's observed scope without violations.
`DEP-MODEL-NO-RENDER`	forbidden_dependency	PASS	0 violations · 0 undecided	Scope, decision and evidence Decider architect Rationale Value types remain independent of how orders are projected as text. Provenance `docs/architecture/shop.md` Scope root Components model, render Assessment The evaluator completed this rule's observed scope without violations.
`DEP-MODEL-NO-STORE`	forbidden_dependency	PASS	0 violations · 0 undecided	Scope, decision and evidence Decider architect Rationale Order and Line value types stay independent of any persistence mechanism. Provenance `docs/architecture/shop.md` Scope root Components model, store Assessment The evaluator completed this rule's observed scope without violations.
`DEP-RENDER-ALLOWS-MODEL`	allowed_dependency	DECLARATION	0 violations · 0 undecided	Scope, decision and evidence Decider architect Rationale Text projection reads the values it renders. Provenance `docs/architecture/shop.md` Scope root Components model, render Assessment Permission declaration; it does not evaluate conformance.
`DEP-RENDER-NO-APP`	forbidden_dependency	PASS	0 violations · 0 undecided	Scope, decision and evidence Decider architect Rationale Text projection stays a pure view over values, not a caller of use cases. Provenance `docs/architecture/shop.md` Scope root Components app, render Assessment The evaluator completed this rule's observed scope without violations.
`DEP-RENDER-NO-CLI`	forbidden_dependency	PASS	0 violations · 0 undecided	Scope, decision and evidence Decider architect Rationale Text projection remains reusable without command-line composition. Provenance `docs/architecture/shop.md` Scope root Components cli, render Assessment The evaluator completed this rule's observed scope without violations.
`DEP-RENDER-NO-STORE`	forbidden_dependency	PASS	0 violations · 0 undecided	Scope, decision and evidence Decider architect Rationale Text projection consumes typed values without touching persistence. Provenance `docs/architecture/shop.md` Scope root Components render, store Assessment The evaluator completed this rule's observed scope without violations.
`DEP-STORE-ALLOWS-MODEL`	allowed_dependency	DECLARATION	0 violations · 0 undecided	Scope, decision and evidence Decider architect Rationale Persistence serialises the domain values it is given. Provenance `docs/architecture/shop.md` Scope root Components model, store Assessment Permission declaration; it does not evaluate conformance.
`DEP-STORE-NO-APP`	forbidden_dependency	PASS	0 violations · 0 undecided	Scope, decision and evidence Decider architect Rationale Persistence stays a leaf dependency and never calls back into use cases. Provenance `docs/architecture/shop.md` Scope root Components app, store Assessment The evaluator completed this rule's observed scope without violations.
`DEP-STORE-NO-CLI`	forbidden_dependency	PASS	0 violations · 0 undecided	Scope, decision and evidence Decider architect Rationale Persistence stays callable without command-line orchestration. Provenance `docs/architecture/shop.md` Scope root Components cli, store Assessment The evaluator completed this rule's observed scope without violations.
`DEP-STORE-NO-MONEY`	forbidden_dependency	PASS	0 violations · 0 undecided	Scope, decision and evidence Decider architect Rationale Persistence serialises whole orders and must not compute or interpret money amounts itself. Provenance `docs/architecture/shop.md` Scope root Components model, store Assessment The evaluator completed this rule's observed scope without violations.
`DEP-STORE-NO-RENDER`	forbidden_dependency	PASS	0 violations · 0 undecided	Scope, decision and evidence Decider architect Rationale Persistence remains independent of how orders are displayed. Provenance `docs/architecture/shop.md` Scope root Components render, store Assessment The evaluator completed this rule's observed scope without violations.
`EXTERNAL-COMPLETE`	complete_external_scope	PASS	0 violations · 0 undecided	Scope, decision and evidence Decider architect Rationale A dependency no rule names is a dependency nobody chose, and a package that does not exist looks exactly the same from inside the code. Provenance `docs/architecture/shop.md` Scope root Components — Assessment The evaluator completed this rule's observed scope without violations.
`EXTERNAL-JSON-STORE`	external_dependency_scope	PASS	0 violations · 0 undecided	Scope, decision and evidence Decider architect Rationale Only the store component chooses the JSON file format; other components stay format-agnostic. Provenance `docs/architecture/shop.md` Scope root Components store Assessment The evaluator completed this rule's observed scope without violations.
`INTERFACE-BOUNDARY`	interface_boundary	PASS	0 violations · 0 undecided	Scope, decision and evidence Decider architect Rationale Components communicate only through declared interfaces, so reaching into another component's internals requires a visible contract change. Provenance `docs/architecture/shop.md` Scope root Components — Assessment The evaluator completed this rule's observed scope without violations.
`MODEL-TYPES-IN-ENTITIES`	symbol_placement	PASS	0 violations · 0 undecided	Scope, decision and evidence Decider architect Rationale Every order, line and money type shop.model owns lives in one module, not scattered across the package. Provenance `docs/architecture/shop.md` Scope root Components model Assessment The evaluator completed this rule's observed scope without violations.
`ROOT-LAYOUT`	root_layout	PASS	0 violations · 0 undecided	Scope, decision and evidence Decider architect Rationale The shop root exposes only its declared top-level components. Provenance `docs/architecture/shop.md` Scope root Components app, cli, model, render, store Assessment The evaluator completed this rule's observed scope without violations.
`STORE-PEERS-ISOLATED`	sibling_isolation	PASS	0 violations · 0 undecided	Scope, decision and evidence Decider architect Rationale Persistence and maintenance are peers behind the store's entry point, so neither reaches into the other. Provenance `docs/architecture/shop.md` Scope root Components api, repository, store Assessment The evaluator completed this rule's observed scope without violations.
`store:STORE-REQUIRES-COMPLETE`	complete_requires	PASS	0 violations · 0 undecided	Scope, decision and evidence Decider architect Rationale Inside the store the same principle holds as above it: an import nobody asked for is an accident, so each part names what it needs and absence refuses the rest. Provenance `docs/architecture/shop.md` Scope store Components — Assessment The evaluator completed this rule's observed scope without violations.

Cross-component imports

Observed imports, not runtime calls or proof of a declared public interface.

All 6 component pairs · 11 imported names

app → model3 imported names

shop.model.entities:Line dataclass
shop.model.entities:Money dataclass
shop.model.entities:Order dataclass

app → store3 imported names

shop.store.sqlite:Connection dataclass
shop.store.sqlite:vacuum function (connection: Connection) → None
shop.store:OrderRepository class

cli → app1 imported names

shop.app.orders:place_order function (store_dir: Path, order_id: str, description: str, quantity: int, unit_price_cents: int) → Order

cli → render1 imported names

shop.render.text:render_order function (order: Order) → str

render → model1 imported names

shop.model.entities:Order dataclass

store → model2 imported names

shop.model.entities:Order dataclass
shop.model.entities:OrderPayload class

Public API measurements

Observed from declared facades and imports: exported-name count, re-exports, names defined in the facade, unused re-exports, consumers per exported name and coupling width. They do not claim a barrel is complete (AD-88); validate holds declared facade and coupling budgets to them (AD-99).

Facades · 5

Component	Module	Exports	Defined	Unused re-exports
`app`	`shop.app.orders`	1	place_order	—
`model`	`shop.model.entities`	5	Line, LinePayload, Money, Order, OrderPayload	—
`render`	`shop.render.text`	1	render_order	—
`store`	`shop.store.repository`	1	OrderRepository	—
`store`	`shop.store.sqlite`	2	Connection, vacuum	—

Export consumers · 10

Component	Export	Consumers	Components
`app`	`shop.app.orders:place_order`	1	cli
`model`	`shop.model.entities:Line`	1	app
`model`	`shop.model.entities:LinePayload`	0	—
`model`	`shop.model.entities:Money`	1	app
`model`	`shop.model.entities:Order`	3	app, render, store
`model`	`shop.model.entities:OrderPayload`	1	store
`render`	`shop.render.text:render_order`	1	cli
`store`	`shop.store.repository:OrderRepository`	1	app
`store`	`shop.store.sqlite:Connection`	1	app
`store`	`shop.store.sqlite:vacuum`	1	app

Coupling width · 6 pairs

Component pair	Distinct names	Names
`app → model`	3	shop.model.entities:Line, shop.model.entities:Money, shop.model.entities:Order
`app → store`	3	shop.store.repository:OrderRepository, shop.store.sqlite:Connection, shop.store.sqlite:vacuum
`cli → app`	1	shop.app.orders:place_order
`cli → render`	1	shop.render.text:render_order
`render → model`	1	shop.model.entities:Order
`store → model`	2	shop.model.entities:Order, shop.model.entities:OrderPayload

Known unknowns · 4

Recorded analysis limits, not declared-rule violations.

Inspect all 4 records

Fingerprint	Finding	Subjects	Evidence
`UNKNOWN-BOUNDARY-TYPE-POSITION-6f4acc9ca5130f7b`	shop.app.orders.place_order store_dir: external_type	`shop.app · shop.app.orders · shop.app.orders.place_order`	`shop/app/orders.py:18`
`UNKNOWN-BOUNDARY-TYPES-d4c18ad1fb20590a`	APP-TYPES-NOT-DICT decided 5 of 6 declared facade type positions	`shop.app`
`UNKNOWN-CONTEXT-DATAFLOW`	Context read/write topology excludes unproven dynamic aliases	`shop`
`UNKNOWN-PYTHON-DYNAMIC-CALLS`	Python dynamic behavior prevents a complete call graph	`shop`

More measurements and review claims

Measurements

Measurement	Value
`violations`	0
`cycle_edges`	0
`private_crossings`	0
`typing_positions`	0
`calls_unresolved`	7
`coverage_failures`	0
`untyped_private_accesses`	0
`unknown_positions`	0
`calls_total`	59
`unresolved_ratio`	7/59

Coverage

Coverage dimension	Evidence
Status	`PASS`
Rules coverage	`PASS`
Files discovered	`12`
Files read	`12`
Files parsed	`12`
AST coverage	`12/12`
Calls resolved	`42/59 (71.19%)`
Calls partially resolved	`10`
Calls unresolved	`7`

Size and coupling

Measured per component and per package: how many modules a scope holds, how many imports stay inside it, how many cross its edge, and how many of its calls the analyzer could not resolve. These numbers are shown, never gated on.

Scope	Level	Modules	Inside	Incoming	Outgoing	Unresolved calls
`app`	component	2	0	1	4	3 of 9
`cli`	component	1	0	0	2	0 of 6
`model`	component	1	0	4	0	2 of 15
`render`	component	1	0	1	1	0 of 6
`store`	component	7	6	3	2	2 of 23
`shop`	package	1	0	1	1	no calls
`shop.app`	package	2	0	1	4	3 of 9
`shop.cli`	package	1	0	0	2	0 of 6
`shop.model`	package	1	0	4	0	2 of 15
`shop.render`	package	1	0	1	1	0 of 6
`shop.store`	package	4	3	3	4	1 of 15
`shop.store.backend`	package	2	0	2	0	1 of 8

Review claim: symbols nobody references

8 of 40 symbols are named by no call, reference or import inside the scan scope; 4 were set aside as runtime dispatch or declared interface. A consumer outside the scan scope, such as a test, is invisible here, and 7 of 59 calls stay unresolved, so these are candidates for review, never a verdict.

Symbol	Kind	Visibility
`shop.app.maintenance.run_maintenance`	function	public_name
`shop.app.orders.describe_connection`	function	public_name
`shop.app.orders.summarize`	function	public_name
`shop.cli.main.main`	function	public_name
`shop.model.entities.Discount`	class	public_name
`shop.model.entities.Discount.apply`	method	public_name
`shop.store.repository.OrderRepository.load`	method	public_name
`shop.store.repository.OrderRepository.save`	method	public_name

Review claim: components larger than their level

1 components hold more modules than the contract has components, or more edges among their modules than it has component edges. The top level holds 5 components and 6 edges between them. Naming a size is evidence; giving one of them a level of its own is a decision (AD-20, AD-33).

Component	Modules	Edges inside
store	7	6

Review candidates: unread parameters and locals

None recorded: no unread-binding candidates across 28 functions and methods. This does not establish that every unlisted binding is read; removal safety is not assessed.

Review claim: logic repeated outside its owner

None: across 28 functions and methods, nothing outside the 1 declared owners repeats the structure of anything inside them.

Review claim: types crossing the most component boundaries

2 of 10 annotated positions on functions and methods crossing a component boundary name a type passed across 2 or more distinct component pairs. A broad context or a service locator shows up as a wide count here; what it means is the architect's to decide, never a verdict.

Type	Component pairs
`Order`	2
`str`	2

Complete scan inventory

Open canonical architecture.json. The JSON remains the source for complete records and evidence.

Scan section	Records
`metrics`	18
`declarations`	58
`scope_observations`	39
`packages`	5
`modules`	12
`symbols`	40
`imports`	50
`dependency_edges`	21
`transitive_paths`	2
`path_observations`	3
`cycles`	0
`calls`	59
`references`	35
`bindings`	0
`typing_signals`	0
`constructs`	1
`contexts`	1
`context_evidence`	0
`violations`	0
`unknowns`	4

Observed module tree · 12 modules

shop
- app
  - maintenance
  - orders
- cli
  - main
- model
  - entities
- render
  - text
- store
  - backend
    files
    paths
  - codec
  - repository
  - sqlite

Reproduction metadata

Command	`report`
Exit code	`0`
Analyzer	`archkeel-python-analyzer 0.63.0`
Analyzer digest	`c2e05f4ac71d3bb4c5e4ada3f5f225f0f7080762fda5695c94589ad8f474cc18`
Python	`3.11.12`
Contract	`architecture-contract.json`
Contract digest	`1d60193ae8e2aa143c01255b1d08d81dd7e7708a85cbc1878a878a6bbf1b9521`