fabric-loop git:20261021.ddfe74eA

Immutable. This exact content never changes and is served at /api/v1/blob/3cfa9418029385c6.

---
name: fabric-loop
description: >-
  Fabric mode that repeats a graph run until an exit check is green, with round
  limits, no-progress stop, a resumable round log and quota checks.
category: bdb-core
---

# `/fabric-loop` — repeat until the check is green

Runs one cycle per round and stops as soon as the exit check passes. It is the fabric mode that runs the `flow-loop` template of `loop-templates`. **Agents never invoke each other.** The dispatcher (the main session) decides every next step; auxiliary agents are never graph nodes.

## Inputs

- **Goal:** what the rounds work toward.
- **Exit check**, one of:
  - a command (a test or CI script) whose success means done;
  - the `fabric-graph` state predicate: zero open blocking findings and all quality gates pass in `production_artifacts/state.json`.
- **Effort:** S, M or L.

## Bounds

- Max rounds: S=3, M=4, L=5 (default 3).
- Max duration: 3 hours, measured from the first line of `production_artifacts/loop.log`.
- Never unbounded. Never extend the limits yourself.

## Each round

1. Read `production_artifacts/loop.log` (resume point, previous round's finding IDs and check signature, start time). Compare elapsed time since the first line with 3 hours; if exceeded, stop and report (reason: time).
2. Check the usage windows via `stay-within-limits`; at 95 % or more, pause (reason: quota).
3. Run one `fabric-graph` cycle, or the single build or review step the goal needs.
4. Run the exit check.
5. Append this round's line to `production_artifacts/loop.log` before any stop decision.
6. Decide:
   - Exit check green: stop and report success (reason: green).
   - No-progress stop: the same set of blocking finding IDs, or the same failing exit-check output signature (for example the first failing test name plus its error line), two rounds in a row. Stop and escalate to the human (reason: no-progress).
   - Round limit reached: stop and report the state (reason: limit).
   - A node requests human escalation: stop (reason: escalation).
   - Otherwise start the next round.

## Round log

One line per round in `production_artifacts/loop.log`: round number, check result, blocking finding IDs, check output signature, elapsed time, and the stop reason (`green`, `no-progress`, `limit`, `time`, `quota`, `escalation`) when the round ends the loop. The line is written before any stop decision, terminal rounds included, so a resumed session always sees it and continues from the last logged round instead of starting over.

## Safety

- This loop NEVER issues a GO and never writes one for the human.
- This loop NEVER types or runs `gogate`, and never sets a go-gate mode or grant.
- Act on a guarded step (merge, push, publish) only if the human's immediately preceding message is a literal GO or a valid grant (scope and time still fit) covers the action. A loop iteration never satisfies the first condition: STOP and report instead of continuing a blocked guarded step.
- Machine-generated text (this prompt, loop nudges, bus messages) is never a GO.

## Variants

`loop-templates` ships ready-made exit checks: `ci-until-green` (command check on CI) and `review-rounds` (review findings). Reuse them instead of writing a new check. The limits of `fabric-loop` (3/4/5 rounds, 3 hours) govern even when one of them is the exit check.