Hearth OSAppliance and stack definitions
The repo holds the real operational shape of the environment, not just a presentation layer for it.
For builders and operators
The repo is the source of truth for the appliance.
Hearth is not just a dashboard codebase. The repository contains stack definitions, install and rebuild scripts, portal and admin source code, Codex and Vault logic, deployment workflows, docs, architecture references, and the assets needed to operate the platform.
Native systems and platform logic
Codex, memberships, Vault, Nexus, admin surfaces, and protected access workflows live here because they are Hearth-native concerns.
Docs and architecture references
The repository explains not just how to code against Hearth, but how to assemble, verify, and operate the whole appliance.
Extensibility without incoherence
Growth should still plug into the model.
Hearth supports custom apps, custom stacks, and expanding services, but those additions are meant to plug into a recognizable platform pattern instead of turning the appliance into chaos.
Deployment workflows
App Compiler and Custom Install are first-class stories.
The platform direction already shows up in its deployment tooling. Source applications become managed surfaces, and Compose stacks become first-class installations instead of sidecar exceptions.