Lane Vocabulary
Holon uses the word "lane" in several distinct ways. In canonical docs, every occurrence must carry a qualifier. Unqualified "lane" is ambiguous and must not appear in docs/system/**.
Lane Taxonomy
Qualified Terms
| Qualified term | Meaning | Current reality |
|---|---|---|
| Child lane | Bounded delegated execution scope owned by a parent goal turn. | One sequential read-only child lane per parent turn, depth 1. |
| Agent lane | Catalog/routing identity such as main-chat or summary-scout. | main-chat and summary-scout implemented; others are design-only or blocked. |
| Pilot lane | Software interaction mode for piloting external targets. | Live execution only for api and file_format; all others blocked at readiness. |
| Tool execution lane | Capability/package execution path metadata: API, MCP, CLI, plugin, file format, built-in, or frozen tool. | Catalog/discovery is broader than live execution. Unsupported lanes fail closed. |
| Bridge lane | Transport/session/readiness classification for adapter bridge bindings. | Mostly contract/readiness state; API is the live floor. |
| Product lane | Frontend product-routing label for workspace display. | UI projection only; no runtime execution authority. |
| Distribution channel | Package trust/distribution labels: local-draft, private-org, personal-private. | Do not call these execution lanes. |
Read Next
- Tooling Taxonomy — canonical definitions for agents, tools, skills, capabilities
- Orchestration Lifecycle — intent-to-evidence lifecycle
- Architecture — architecture hub