Skip to main content

Architecture

This page describes the high-level system shape and authority boundaries.

New to Holon? Start with Learn before diving into architecture.

Architecture Map​

  • System Topology: conceptual runtime layers and flow of responsibility.
  • Tooling Taxonomy: canonical vocabulary for agents, tools, function calling, skills, capabilities, and frozen tools.
  • Lane Vocabulary: qualified terms for child lanes, agent lanes, pilot lanes, tool execution lanes, bridge lanes, product lanes, and distribution channels.
  • Plugin Packages: V1 package manifest model for importing package capabilities into the unified capability catalog and dry-run discovery flow.
  • Plugin Marketplace Boundaries: accepted future marketplace taxonomy, v2-core scope, core-plugin posture, and deferred extension-family boundaries without changing current V1 behavior claims.
  • Tool Discovery And Orchestration: distinction between low-context tool listing, context-aware discovery, and later guarded execution.
  • Workflow Semantics: canonical workflow model for triggers, activation, alternate starts, waiting, background execution, and workflow-owned data interaction.
  • Rust Code Tools: current compiled Rust CLI frozen-tool implementation, readiness model, and live execution boundaries.
  • Elegy Integration: how Holon consumes Elegy contracts and maps Elegy types into Holon runtime events and evidence.
  • Release And Versioning: the Windows-first GitHub Releases contract, shared Holon semver, and updater distribution shape.
  • HolonDesktop Real Desktop Validation: canonical run discipline for real Tauri and WebView2 desktop end-to-end validation.
  • Orchestration Lifecycle: lifecycle from intent through evidence.
  • AI Contract And Conformance Boundaries: current host-authored instruction-contract rules, structured-output boundaries, and minimum conformance expectations.
  • Desktop Runtime Integration: in-process Rust runtime integration for the Holon Desktop shell (Option A).
  • CLI Architecture: how the holon CLI binary exercises the runtime protocol surface.

Authority Boundaries​

  • User-facing surfaces express intent and present outcomes.
  • Runtime core owns interpretation, planning coordination, and policy enforcement.
  • Capability layer defines what actions are available in-context.
  • Execution layer performs approved work under guardrails.
  • Evidence and state record what was attempted, what happened, and why.

Canonical Rules​

  • Authority must remain explicit at each layer.
  • Selection and execution are distinct stages.
  • Guardrails apply before, during, and after execution.
  • Evidence is required for meaningful completion.