Overview

Date: 2026-05-11

Time: 15:10

Overview

ftl2-deployments is a collection of self-contained workspaces used for deploying services via the ftl2-ai-loop. Each workspace encapsulates everything needed for a specific deployment — desired state, AI loop rules, environment variables, and runtime-generated state/inventory files. The repository demonstrates real-world production usage of FTL2's AI reconciliation loop for infrastructure deployment.

Key Concepts

• Workspace model — each deployment is isolated in its own directory with independent state, inventory, and rules
• Desired state declaration — each workspace has a desired_state.txt file describing what the AI loop should achieve (declarative intent)
• AI loop rules — workspace-specific rules in a rules/ directory that constrain and guide the AI reconciliation loop
• Runtime-generated state — state and inventory files are not checked in; they are created at runtime by the AI loop
• Environment separation — .env files hold secrets/config per workspace (not committed to version control)

Commands and Syntax

Launching a deployment with the AI loop:

cd cloudflare-stargate
ftl2-ai-loop --incremental "Deploy ftl2-stargate with Caddy..."

• --incremental flag: runs the AI loop incrementally rather than from scratch
• The quoted string provides the deployment goal/intent to the loop

Relationships

• ftl2-ai-loop — the orchestration tool that reads workspace config and drives deployments
• Inventory management — inventory is generated at runtime, not pre-defined (contrast with static YAML inventory in standalone FTL2 scripts)
• Policy/rules engine — workspace rules/ directories are an application of FTL2's policy system scoped to AI loop behavior
• Vault integration — .env files and secrets management tie into how credentials are handled per deployment
• ftl2-stargate — one concrete deployment target (Caddy reverse proxy on Linode using a pre-baked Fedora image)

Exam-Relevant Points

• Workspace structure has four key components: desired_state.txt, rules/, .env, and runtime-generated state/inventory
• State and inventory files are not pre-created — they are generated at runtime
• .env files are excluded from version control (secrets hygiene)
• The --incremental flag enables incremental reconciliation rather than full re-deployment
• Each workspace is fully self-contained — deployments are isolated from each other
• The AI loop takes a declarative goal string as input and reconciles toward it using workspace rules