engineering-agent

Self-hosted, persistent engineering-agent service for supervised ZaveStudios engineering work.

Repository Classification

• Category: platform-service
• deploys_runtime: Yes
• mutates_shared_infrastructure: No
• provides_reusable_capability: Yes
• consumes_shared_workflows: Yes

engineering-agent provides a reusable operator-driven engineering capability. It is not a tenant workload, portfolio site, infrastructure repository, or POC.

Architecture

The initial design is documented in engineering-agent-architecture.md.

The v1 architecture uses:

• OpenCode as the engineering-agent runtime
• llm-platform as the model-access gateway
• GitHub as durable source-control and collaboration state
• CI/CD as the authoritative build, validation, review, and delivery path
• persistent OpenCode session/history state
• isolated, disposable task workspaces for repository edits

Boundaries

OpenCode does not:

• merge protected branches
• bypass llm-platform
• own model-provider routing, credentials, quota, policy, or observability
• replace CI/CD validation or production delivery
• subsume Mia/OpenClaw

Billy remains the merge authority for production-impacting change.