Developer overview
Ta treść nie jest jeszcze dostępna w Twoim języku.
Developer overview
Section titled “Developer overview”LM Nexus uses FastAPI on the backend and Vue/TypeScript on the frontend.
Architecturally it is a static modular monolith: one application made from modules with explicit boundaries.
The public developer docs are still growing, but a few rules are already stable.
Product bundles assemble the app
Section titled “Product bundles assemble the app”The backend and frontend product bundles choose and order module manifests.
Feature logic, UI, state, services, and clients should stay in the module that owns them rather than drifting into the bundle layer.
Cross-module work uses public boundaries
Section titled “Cross-module work uses public boundaries”Modules should integrate through:
- declared dependencies;
- public capabilities;
- registered contributions;
- Agent Tool contracts where appropriate.
Avoid importing another module’s private implementation just because it is convenient.
Runtime data stays outside the repository
Section titled “Runtime data stays outside the repository”Source, tests, fixtures, documentation, and committed assets belong in Git.
Normal user/runtime data belongs in per-user app-data, config, cache, or state locations.
Supported development runtime
Section titled “Supported development runtime”Current development uses exact CPython 3.14.7 with the standard GIL plus the repository’s pinned Node/npm toolchain.
Platform claims should distinguish Linux, WSL, and native Windows rather than treating “Windows support” as one undifferentiated thing.
More developer docs
Section titled “More developer docs”This section will grow to cover:
- module authoring;
- capability contracts;
- Agent Runtime/tool contracts;
- package installation, updates, trust, and permissions;
- API/reference material;
- contribution workflow.
Only implemented, reviewable contracts should move into public reference docs.