Developers

Navet is organized as a pnpm workspace with deployable applications under apps/ and product, provider, core, and UI packages under packages/.

Set up the repository

Use the contributing guide for prerequisites, local development, and validation expectations.

Maintainers can also send selected issues through Navet’s agentic development workflow.

Architecture direction

• @navet/core owns provider-neutral contracts, IDs, and runtime semantics.
• @navet/ui is the target boundary for provider-neutral shared React UI.
• Provider packages own provider authentication, transport, mapping, and command translation.
• @navet/app owns product composition, runtime selection, settings, and persistence.

Home Assistant is the reference adapter, not the application architecture. New shared work should depend on Navet-owned contracts rather than raw provider payloads.

The app can retain multiple implemented provider sessions and aggregate selected provider collections. Each adapter declares the services and controls it supports; see the capability matrix when implementing or documenting a shared feature.

Detailed maintainer, architecture, testing, release, and AI-agent documents remain available in the repository documentation.