Architecture
Headless Daemon API Contract
Homeboy is CLI-first, but the daemon is the stable local UI and automation surface for clients that should not shell...
Runner contract
The contract between Homeboy core and runner scripts: what capabilities exist, what env vars flow in, what sidecar files scripts...
Trace Probes
Trace probes are passive observation helpers that run beside a trace workload and emit events into the existing trace timeline...
Runner Connection Bootstrap
homeboy runner connect <runner-id> uses the first-class runner registry added for issue #2526. Registry Contract Runner configs are JSON files...
Keychain and Secrets Management
Homeboy securely stores sensitive credentials using OS-native keychain/credential manager systems. Overview Homeboy never stores secrets in plaintext configuration files. All...
API Client System
The API client provides HTTP request capabilities with template-based authentication per project. Overview Homeboy projects can configure an API client...
Scope Model
Homeboy commands operate on different kinds of things. The shared scope model makes those things explicit so project/site workflows do...
JSON output contract
Homeboy prints JSON to stdout for most commands. Exceptions: homeboy docs prints raw markdown (or newline-delimited topic names for homeboy...
CI result JSON contract
Homeboy CI results are exposed through the existing global --output <path> flag. The flag writes the same JSON envelope Homeboy...
Rig Matrix Axis Composition
Design for deriving rig variants from one base rig plus explicit axis overlays. Tracked by Extra-Chill/homeboy#1844. Problem Rigs currently model...
Execution Context
Execution context is the environment Homeboy passes to extension runners and extension-backed pipeline steps. Overview When Homeboy executes an extension,...
Release Pipeline System
The release pipeline provides configurable, local orchestration for managing component releases without CI/CD systems. Overview Homeboy's release pipeline is a...