Nexus Plugin Architecture

How Aura extends domain behavior without forcing every integration into the core language.

aura-nexus is a workspace component for plugin manifests and integration. The primary CLI resolves plugin information and can make plugins visible to build/verification paths.

Why a plugin layer

A systems language quickly accumulates domain pressure: UI, AI, IoT, platform integrations and external libraries. Nexus provides a route for those capabilities without making each one a permanent core grammar commitment.

Current workspace plugin surfaces include:

aura-plugin-lumina
aura-plugin-ai
aura-plugin-iot

Verification-aware extensions

Aura’s z3 feature wiring also enables verifier-related plugin features in the AI/IoT paths. Public claims should remain tied to the concrete plugin/module/example rather than implying that every possible domain program is automatically verified.

Stability

Nexus is a meaningful implementation surface, but Aura remains pre-stable. Plugin manifest/protocol compatibility should be treated as evolving until a stable release contract is published.