Specs

Tuist · Public · [!IMPORTANT] Verified against the codebase and against the prior art on 2026-08-26, not measured here. The server is already build-system agnostic: Tuist.Tests.Test carries build_s

Tuist · Public · [!IMPORTANT] Nobody is choosing regions today. On 2026-08-20, nine of the ten live customer Kura instances belonged to accounts whose storage-region setting was "all regions", 47 o

Tuist · Public · Summary The per-account cache master introduced by spec #76 is a single sparse APFS disk image, content-addressed by its inventory digest, and every convergence re-pulls the whole

Tuist · Public · Summary This RFC pivots the macOS runner module-cache architecture from on-host Kura serving (spec #75, PR tuist/tuist#11701) to per-account cache volumes: an APFS disk image per a

Tuist · Public · Summary Kura's replication and bootstrap decide whether to move an artifact by comparing version_ms, a wall-clock stamp assigned at write time. For the content-addressed artifact c

Tuist · Public · Summary The Kura version scheduler refuses to schedule a new runtime image for a server while any deployment row for that server is open (:pending or :running). A deployment stays

Tuist · Public · Summary Today a new Kura runtime image reaches the entire managed fleet in a single reconciler tick: the control plane schedules a deployment for every eligible server at once, eve

Tuist · Public · Summary This RFC proposes a remote container build service for Tuist customers: a per-account BuildKit builder, running inside a runner microVM with a persistent per-account cache

Default project · Public · Why Tuist already runs its own compute fleet on Kubernetes. Today it serves a single workload: CI runners. The fleet has two pools, both schedulable through the standard Kubernetes

Default project · Public · Why Hive is the central hub for agentic product orchestration. External agents (Claude Code today, in-process Hive workers later) connect over MCP, browse and modify specs, and rea