Read this page when you need the current canonical answer for who owns AI behavior in Holon, where structured output is already required, and what minimum proof is expected before claims about AI-facing contract surfaces should be trusted.
This page describes the high-level system shape and authority boundaries.
Holon consumes Elegy through a repo-local install root under tools/elegy.
Authority Split
Holon is an expert automation product focused on turning human intent into reliable outcomes.
This guide explains how HolonClient resolves runtime configuration in production builds and what patterns MUST NOT be used. Read this before adding or changing environment variables in the HolonClient renderer.
Use this guide when you need evidence about the actual HolonDesktop shell instead of renderer-only behavior.
Use this guide for the current Holon production release contract.
rust-code-tool is Holon's current compiled-code frozen-tool implementation kind. It lets a workspace persist a governed Rust CLI tool as managed source, build it under runtime control, validate it with tests and fixtures, and project it into the runtime tool catalog only after artifact readiness is proven.
This page describes the system as layered runtime responsibilities.
This page defines the vocabulary shared by Elegy (contract substrate) and Holon (runtime authority). Every term has a precise owner and a boundary that must not be crossed.
This page defines the canonical workflow model for Holon.