Skip to main content

Holon

Holon is an expert automation product focused on turning human intent into reliable outcomes.

This surface is the canonical high-level map for how the system is intended to work.

Mission​

Holon exists to make complex work easier to execute safely. It does this by combining guided orchestration, bounded execution, and clear evidence of what happened.

Product Goals​

  • Translate intent into a clear execution path.
  • Keep authority and accountability explicit at every step.
  • Ensure execution is bounded by policy and context.
  • Preserve evidence that supports review and trust.

Canonical Runtime Principles​

  • Intent is interpreted before execution starts.
  • Planning is explicit, bounded, and revisable.
  • Capability use is selected deliberately, not implicitly.
  • Execution is guarded by policy and scope.
  • Evidence is part of completion, not an afterthought.

Reading Path​

New to Holon? Start with Learn for a guided introduction to what Holon is, what harnesses are, and how Holon's harness model works.

  1. Learn — what Holon is, harness engineering, and the Holon harness model.
  2. Architecture — high-level system shape and authority boundaries.
  3. System Topology — layered runtime responsibilities.
  4. Tooling Taxonomy — canonical vocabulary plus implementation status.
  5. Lane Vocabulary — qualified lane terms (child, agent, pilot, tool execution, bridge, product, distribution channel).
  6. Tool Discovery And Orchestration — listing, discovery, and guarded execution.
  7. Workflow Semantics — trigger, activation, execution, and background-work model.
  8. Orchestration Lifecycle — intent through framing, planning, execution, and evidence.
  9. Plugin Packages — V1 package manifest and capability import.
  10. Plugin Marketplace Boundaries — future marketplace and v2-core scope.
  11. Rust Code Tools — compiled Rust CLI frozen-tool implementation.
  12. Elegy Integration — how Holon consumes Elegy contracts.
  13. AI Contract And Conformance Boundaries — host authority and instruction-contract rules.
  14. Desktop Runtime Integration — in-process Rust runtime for Holon Desktop.
  15. CLI Architecture — how the holon CLI exercises the runtime.
  16. Concrete Systems — specialist harness compositions for real task families.
  17. Known Issues — current limitations and workarounds. Read this after the architecture to understand what is implemented vs planned.

Scope Note​

This surface covers high-level design decisions, system architecture, learning material, concrete systems, and the three main runtime axes: the Rust runtime core, the desktop application, and the CLI. Planning and research content remain available in the repository for forward-looking work but are not part of the public documentation surface.