binaries

What problem does it solve?

Forge users need a clear, repeatable way to decide when a long-running process should be scaffolded as a binary (with its own Deployment) instead of a service, worker, or operator.

Core Features & Use Cases

• Decision guidance: Choose service, worker, binary, or operator based on lifecycle ownership and whether the process needs its own Deployment and scaling.
• Consistent scaffolding: Generate a binary’s cobra subcommand plus the canonical Deps/Runner lifecycle and starter tests (including ctx cancel start/stop and validateDeps coverage).
• Deploy integration: Ensure each binary listed in forge.yaml is rendered into a Kubernetes Deployment that runs the cobra subcommand with the correct deploy story and shared defaults.

Quick Start

Ask the AI: scaffold a long-running Kubernetes-ready reverse-proxy process as a Forge binary named "workspace-proxy" and explain how its lifecycle and deployment should work.