Athas Boilerplate

Athas Boilerplate

Overview Canonical Scope Architecture Backend Patterns Frontend Patterns API Interfaces Modular Composition Audience Projections Development Flow Getting Started Feature Scaffolding Backend Module Workflow Database Migrations Module Composition Guide Docs Information Architecture Starter CLI Workflows Runtime Feature Flags (OpenFeature)UI Library Hardening Performance Guidelines Runtime Telemetry @athas/shared-api @athas/contracts @athas/db @athas/auth-core capabilities @athas/shared-utils @athas/notifications-core @athas/integrations-core AI-Assisted Docs Workflow Module Profiles Hard-Remove Workflow Commerce Sprint Plan Foundation Closeout

Modular Composition

shared

How modules are soft-disabled, hard-removed, and packaged for starter profiles.

Composition layers

backend runtime flags (BACKEND_MODULE_*)
frontend runtime flags (VITE_MODULE_*)
hard-remove workflow for permanent pruning

Soft-disable semantics

code remains in repo
disabled surfaces are hidden/gated
modules can be re-enabled without recovery work

Hard-remove rule

soft-disable first
operate safely in disabled mode
remove contracts/routes/module code with migration plan
update docs and roadmap in same PR

Never hard-remove from fully enabled state.

Compatibility guarantees

projection policy still applies (public/client/admin)
contract-first integrity must remain intact
env templates must reflect module switches

Related deep reference

See docs/architecture/40-modular-composition.md and /docs/module-profiles.

API Interfaces

Contract-first API model using oRPC for first-party and HTTP/OpenAPI for external consumers.

Audience Projections

Policy for public/client/admin contract projections.

On this page

Composition layers Soft-disable semantics Hard-remove rule Compatibility guarantees Related deep reference