internal/

Package backend selects between the two ways mcp-server can talk to a Tiny Systems cluster: directly via kubeconfig, or indirectly through the hosted platform-api with a developer token.

Package catalog resolves a module NAME to the coordinates `tiny` needs to install it, using the public, unauthenticated Tiny Systems catalog at api.tinysystems.io.

Package flow is tiny's local implementation of the platform FlowService — the gRPC/gRPC-web API the browser editor talks to.

Package installer implements sdktools.ModuleInstaller for kubeconfig mode: it lets an agent install a capability module on the fly, mid-build, through the MCP endpoint — resolving from the configured repos (default: the public index) and helm-installing via the exact same repo-model path as `tiny install`.

Package kube wires up the Kubernetes client used by all adapters.

Package mcp implements a minimal Model Context Protocol server.

Package project resolves the active project for a tiny session.

Package prompt holds the public-MCP-specific appendix that is appended to the SDK's core prompt when get_instructions is called.

Package provision installs the Tiny Systems runtime and capability modules onto a cluster by embedding the Helm Go SDK (via mittwald's go-helm-client) — no shelling out to a `helm` binary, no hosted platform.

Package repo implements the decentralized, Helm-style module distribution client described in docs/design/module-distribution-v2.md: repos are static index files, the source of truth is the module repo + its signed image, and the platform is demoted to an optional aggregator.