internal/

Package app assembles Ripen from its parts and answers the reads.

Package backend is the orchestrator seam of the Transaction: the port every backend (Portainer API, compose runtimes) implements, reshaped around what one Transaction needs — observe a stack, deploy a compose document, and prove the stack's services are running.

Package cli is Ripen's command surface.

Package compose is the compose-runtime backend: one adapter driving a compose CLI, with docker-compose and podman-compose as thin constructors over the same code.

Package composefile reads and edits Compose documents as text.

Package config loads and validates the Ripen policy file.

Package daemon runs Ripen on a schedule.

Package domain holds the core vocabulary of Ripen: modes, backends, actors, result codes, and image references.

Package event is Ripen's Event stream: one stream, many sinks.

Package github opens digest-pin Proposals as pull requests.

Package health runs the functional health checks a Transaction verifies against.

Package mcpserver is Ripen's MCP surface: stdio, tools only, and a strict subset of the CLI.

Package notifier is the webhook sink of the Event stream: the one outbound Notifier Ripen ships with.

Package portainer is the Portainer API backend.

Package proposal is the vocabulary of Git-native updates: the change Ripen asks a forge to open, and the Proposal that now exists.

Package registry is a deliberately minimal OCI registry client for digest observation: resolve what digest a tag points at, per platform.

Package response is Ripen's wire surface: the Response envelope every verb answers in, and the typed payloads inside it.

Package state persists Baselines, Candidates, and coordination state in SQLite.

Package updater is the Transaction engine: the deep module that owns one complete Monitor or Apply run.

Package version holds the build metadata stamped into release binaries.

Package webui is the optional read-only Web UI, embedded in the binary and served inside `ripen daemon`.