Architecture
JSON output contract
Homeboy prints JSON to stdout for most commands. Exceptions: homeboy docs prints raw markdown (or newline-delimited topic names for homeboy...
Provider fanout boundary
Homeboy core owns durable orchestration and provider-neutral evidence. Runtime providers own backend-specific execution details. The seam is the AgentTaskRequest/AgentTaskOutcome adapter...
Lifecycle Contracts
Homeboy defines a product-neutral lifecycle contract for workloads that mutate state and need fuzz-safe cleanup. Core owns the vocabulary and...
Runner contract
The contract between Homeboy core and runner scripts: what capabilities exist, what env vars flow in, what sidecar files scripts...
CI result JSON contract
Homeboy CI results are exposed through the existing global --output <path> flag. The flag writes the same JSON envelope Homeboy...
Planned Change Execution
Homeboy's planned-change vocabulary is the shared core language for work that starts as a plan and may eventually mutate files...
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...
Preview Metadata
Homeboy preserves generic preview metadata and can either consume caller-supplied public access or own a native preview tunnel lifecycle for...
Apply And Publish Contract
Homeboy uses a shared execution vocabulary for generated changes: execute produces proposed results. artifact preserves proposed changes with provenance and...
Agent task executor adapter
Agent task executor adapters are the boundary between Homeboy core and the systems that actually run agent work. Core owns...
Secret Env Contract
Homeboy core owns the generic contract for passing required secret environment variables across runners, agent tasks, trace workloads, lab offload,...
API Client System
The API client provides HTTP request capabilities with template-based authentication per project. Overview Homeboy projects can configure an API client...