Marketplace & extensions

Marketplace & extensions

LM Nexus already has a working Marketplace with install, update, rollback, and package-management flows inside the current product.

What it does not have yet is a mature public extension ecosystem. That distinction matters.

What exists today

Current LM Nexus development includes:

• Marketplace/package browsing;
• install, update, and rollback flows;
• checksum and archive validation;
• explicit trust and permission approval;
• dependency checks;
• installed-extension management;
• module bundle/profile export tools.

These flows are designed around controlled package sources and verified package files.

What is not being claimed yet

LM Nexus does not currently claim:

• a mature public hosted Marketplace;
• arbitrary unsigned runtime code loading;
• sandboxed third-party execution;
• transparent hot-load/hot-unload of frontend modules;
• a finalized public extension API compatibility promise.

Those need more product, trust, compatibility, and release work before they can be presented as public features.

How extensions fit into LM Nexus

Extensions use the same module boundaries as the rest of the application: declared dependencies, capabilities, and contribution points.

Read Module model for the architecture behind that.