How pathwaycom/serviette is laid out, and where to start for common changes.
A
Architecture grade
score 89/100
2
Import cycles
lower is better
101
Files mapped
199 imports between them
98%
Layering
of imports point one way
From the map of which files import which, built when the code was last read in full. It shows what depends on what, not a reading order.
Module map
Shade byless more
10 modules, 23 links. A link means one module imports another; thicker lines mean more imports. Select a module to trace it: blue lines go to what it uses, orange lines come from what uses it.
ModuleFilesUsed byUsesCommits, 90 daysRole
config2611Shared core
__init__1403Foundation
server21341Orchestrator
indexer7232Orchestrator
frontend3211Shared core
testing1201Foundation
up1231Orchestrator
demo1121Orchestrator
wizard1111Shared core
cli1081Entry or leaf
Where to start reading
Repository root
Repository root
Likely public API
Likely public API
Likely start-up file
Likely start-up file
Suggested starting pointAI
Suggested starting pointAI
Find files for a task
AI
Add Support for a New Vector Database
Add database configuration Pydantic model to config/schema.py with connection parameters and defaults
Register the accessor class in the factory/dispatcher logic in server/main.py or config schema discriminator union
Add a New Retrieval Strategy (beyond Hybrid/BM25)
Add strategy configuration option to serviette/config/schema.py as a new union variant in retrieval config
Integrate strategy instantiation and invocation in serviette/server/main.py query pipeline
Add a New Frontend Feature (Query Type or UI Component)
Define new query request/response schemas in serviette/config/schema.py if needed
Add HTTP endpoint handler in serviette/frontend/main.py that routes to appropriate server logic
Create or modify UI component in serviette/frontend/static/index.html to expose the feature
Add integration test in tests/test_frontend.py verifying endpoint behavior
Add Support for a New Document Source Type
Create new source class in serviette/indexer/sources.py inheriting from appropriate base loader
Add source configuration model to serviette/config/schema.py with connection/path parameters
Integrate source in the Pathway graph in serviette/indexer/graph.py or indexer/main.py
Add unit test in tests/ verifying documents are loaded and chunked correctly
Change the public API
Trace runtime behavior
Add or update tests
Change build or automation
RepoPilot lists up to 500 files, so a file missing here may still exist.
Files marked “likely” are guessed from their names.
Code quality and hotspots
Largest source files
Branch points19 per file on average
Code issues0 errors, 6 warnings
Largest file1,029 lines
Hotspot load0 high-risk files
Static checks on the 15 largest source files.
Tests, CI and tooling
CIGitHub Actions1 workflow
Tests42 test filesPytest · 0.71 test files per source file (file count, not coverage)
Dependency updatesNo config detected
Test folders: tests · benchmarks/realtime-data-indexing