PASS
Scan complete
observation_complete
All source files under sample were read and parsed; no source file beside them was read.
A
Independent verdicts
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. 2 recorded analysis limits; 0 of 3 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 · 0
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 |
|---|
Cross-component imports
Observed imports, not runtime calls or proof of a declared public interface.
No cross-component imports were observed.
Known unknowns · 2
Recorded analysis limits, not declared-rule violations.
Inspect all 2 records
| Fingerprint | Finding | Subjects | Evidence |
|---|---|---|---|
UNKNOWN-CONTEXT-DATAFLOW | Context read/write topology excludes unproven dynamic aliases | | |
UNKNOWN-PYTHON-DYNAMIC-CALLS | Python dynamic behavior prevents a complete call graph | sample | |
More measurements and review claims
Measurements
| Measurement | Value |
|---|---|
violations | 0 |
cycle_edges | 0 |
private_crossings | 0 |
typing_positions | 0 |
calls_unresolved | 0 |
coverage_failures | 0 |
untyped_private_accesses | 0 |
unknown_positions | 0 |
calls_total | 3 |
unresolved_ratio | 0/3 |
Coverage
| Coverage dimension | Evidence |
|---|---|
| Status | PASS |
| Rules coverage | PASS |
| Files discovered | 3 |
| Files read | 3 |
| Files parsed | 3 |
| AST coverage | 3/3 |
| Calls resolved | 3/3 (100.00%) |
| Calls partially resolved | 0 |
| Calls unresolved | 0 |
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 |
|---|---|---|---|---|---|---|
sample | package | 3 | 1 | 0 | 0 | 0 of 3 |
Review claim: symbols nobody references
1 of 3 symbols are named by no call, reference or import inside the scan scope; 0 were set aside as runtime dispatch or declared interface. A consumer outside the scan scope, such as a test, is invisible here, and 0 of 3 calls stay unresolved, so these are candidates for review, never a verdict.
| Symbol | Kind | Visibility |
|---|---|---|
sample.work.run | function | public_name |
Review claim: components larger than their level
None: no component holds more than the level containing it. The top level holds 0 components and 0 edges between them.
Review candidates: unread parameters and locals
None recorded: no unread-binding candidates across 3 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
Not claimed: no spot_owner is declared, so none of the 3 functions and methods has an owner to repeat.
Review claim: types crossing the most component boundaries
None: across 0 annotated positions on functions and methods crossing a component boundary, nothing is passed across 2 or more distinct component pairs.
Complete scan inventory
Open canonical architecture.json. The JSON remains the source for complete records and evidence.
| Scan section | Records |
|---|---|
metrics | 18 |
declarations | 1 |
scope_observations | 2 |
packages | 3 |
modules | 3 |
symbols | 3 |
imports | 2 |
dependency_edges | 2 |
transitive_paths | 0 |
path_observations | 0 |
cycles | 0 |
calls | 3 |
references | 0 |
bindings | 0 |
typing_signals | 0 |
constructs | 2 |
contexts | 0 |
context_evidence | 0 |
violations | 0 |
unknowns | 2 |
Observed module tree · 3 modules
samplehelperswork
Reproduction metadata
| Command | report |
|---|---|
| Exit code | 0 |
| Analyzer | archkeel-python-analyzer 0.63.0 |
| Analyzer digest | c2e05f4ac71d3bb4c5e4ada3f5f225f0f7080762fda5695c94589ad8f474cc18 |
| Python | 3.12.14 |
| Contract | docs/architecture/contract.json |
| Contract digest | ba6dccc8cc1aac405d478cb663bef4cb590504a7f851e47a750f19abe92c4a78 |