1.3 KiB
1.3 KiB
Architecture Deepening
Goal
Increase depth, locality, and testability in the existing Meshnet runtime without changing its domain behavior or reopening accepted architecture decisions.
Scope
This feature backlog is derived from the Graphify code graph and the architecture review. It targets three high-coupling modules:
- Distributed Route Session execution in the node HTTP path.
- Node startup orchestration.
- Tracker request intake and HTTP dispatch.
Constraints
- Preserve ADR-0009: the Tracker is the control plane and public proxy; workers own tokenizer and model execution.
- Preserve the active Distributed GGUF Runtime plan: DGR-040 owns native-worker supervision; DGR-041 owns native capability registration. Do not duplicate or redesign those stories.
- Preserve existing Transformers behavior and backend-agnostic Tracker routing, billing, admission, telemetry, and relay semantics.
- Each task starts with focused characterization tests, then moves behavior behind one deep module interface.
Order
- Route Session execution, because it has the clearest seam and lets distributed execution be tested without HTTP.
- Node startup orchestration, using the existing capability-validator adapters.
- Tracker intake, only after the first two establish the preferred deep-module style.