[Epic] Loop Engineering — design the system that prompts your agents

[dkling-it]

Summary

Loop engineering replaces you as the person who prompts the agent — you design the system that does it instead: the schedule, state, and verification chain that keeps an autonomous workflow running correctly over time.

Harness = single session / single run
Loop    = harness + schedule + state + verification chain
Fleet   = many loops/agents + registry + identity + org-wide control

Scope

• Init / scaffolding — loop init (loop-init)
• Audit / scoring — loop doctor, loop-audit (Loop Ready score)
• Cost tracking — loop-cost
• Sync / worktree isolation — loop-sync, loop-worktree
• Context & MCP surface — loop-context, loop-mcp-server

See the Quickstart and CLI front door.

Stack position

Loop Engineering is the layer directly below Fleet Engineering (many loops/agents + registry + org-wide control). A stable loop is a prerequisite before adopting fleet patterns.

Companion epic: cobusgreyling/fleet-engineering#3

[dkling-it]

Closing — opened in error / not proceeding with this epic tracking here.