🌌 A reproducible developer workstation and self-hosted runtime foundation for projects and organizations.
Realm describes environments as versioned capabilities and composable profiles. One resolved profile can feed several projections—Docker images, Dev Containers, Nix, or Linux workstation setup—without turning a Dockerfile into the source of truth.
catalog/capabilities.jsondefines packages, artifacts, dependencies, platforms, projections, and safety constraints.catalog/tool-evaluations.jsonis the curated admission queue for tools before they become stable profile capabilities.profiles/definesbase, language variants,full, and an explicitservicesboundary.schemas/publishes the v1 catalog, profile, resolved-profile, and tool-evaluation contracts.tools/realm_profiles.pyvalidates and resolves the environment model without third-party dependencies.tools/realm_tool_registry.pyvalidates tool inclusion decisions and renders the review queue.docs/profiles.mdrecords profile semantics and release boundaries.docs/tool-registry.mddocuments tool evaluation, stable-inclusion gates, overlap decisions, and maintenance policy.docs/mantle-shell.mdexplains build-timeSHELLversus an installed interactive Mantle shell.
Validate the contracts and resolve the full Docker projection:
python3 tools/realm_profiles.py validate-catalog
python3 tools/realm_profiles.py validate-profiles
python3 tools/realm_tool_registry.py validate
python3 tools/realm_profiles.py resolve \
--profile "full" \
--platform "linux/amd64" \
--projection "docker" \
--output "/tmp/realm-full.json"
python3 -m unittest discover --start-directory tests --verboseRender the current tool review queue:
python3 tools/realm_tool_registry.py reportThis contract intentionally precedes image generation. A tool must pass the curated inclusion gates before stable profile admission. Published images must be rendered from a resolved profile, built for supported platforms, tested, and then referenced by immutable digest.