Skip to main content

Elegy Distribution Bootstrap

Holon consumes Elegy through a repo-local install root under tools/elegy.

The supported setup path is:

pwsh ./scripts/bootstrap-elegy-distribution.ps1 -Force

What The Bootstrap Does​

The bootstrap script:

  • reads the pinned downstream config from scripts/elegy-bootstrap.config.json
  • installs the configured Elegy release assets into tools/elegy
  • validates the install receipt and required governed contract entries
  • runs the existing Holon consumption proof
  • writes tools.elegy.executablePath into Holon Desktop app config so desktop observation capture can invoke the installed umbrella elegy binary

The seeded desktop app config path follows the desktop shell app-data root:

  • Windows: %APPDATA%\com.holon.desktop\app_config.json
  • macOS: ~/Library/Application Support/com.holon.desktop/app_config.json
  • Linux: ${XDG_DATA_HOME:-~/.local/share}/com.holon.desktop/app_config.json

Local Artifact Validation​

When validating unpublished local Elegy artifacts, point the bootstrap at Elegy/artifacts/distribution:

pwsh ./scripts/bootstrap-elegy-distribution.ps1 -LocalArtifactsRoot ../Elegy/artifacts/distribution -Force

Manual Fallbacks​

If you are not using the supported bootstrap lane, Holon Desktop can still resolve Elegy through:

  1. tools.elegy.executablePath in desktop app config
  2. ELEGY_CLI_PATH
  3. dev-only ELEGY_REPO_ROOT

The bootstrap flow is preferred because it uses the receipt-backed installed umbrella CLI and keeps Holon's observation setup aligned with the repo-local tools lane.