augment-it/loops
- Path
- loops/index.md
Loops
- Adopt CardRow and a SelectWrapper in one member - The pilot executor. Three members answer the open decisions with evidence; everything mechanical is inherited from the Button loop.
- Adopt Selector in one member - The test comes before the refactor. This is the first organ whose defects are invisible — a broken keyboard renders perfectly.
- Adopt the shared Button in one member — the per-member executor for the Button rollout - One member per run, never a sweep. Replace the buttons, delete the recipes they made redundant, raise everything else.
- Adopt the shared Chip in one member - The per-member executor for the Chip rollout. Inherits every probe and verification rule from the Button loop; what differs is the judgement about what a chip even is.
- Converge the federated design system — scan members for organs, fingerprint them, and triage divergence into five verdicts - Creativity is the default and stays the default. The loop’s job is to notice when two teams solved the same problem twice without meaning to.
- Create or Update Archify Diagrams - The repeatable procedure for turning a unit — or the whole system — into a validated, explorable Archify diagram that reflects real code rather than a plausible story.
- Endow a Component With Its Own Contracts - The repeatable procedure for giving one unit — service, remote, package, or shell — the four firsts it owes. One unit per run, never a sweep.
- From a Raised Issue to Fixed-and-Shipped — the bug-to-ship loop - A raised issue becomes a context-v issue doc, a gh issue, then an attempt→verify cycle that safety-commits every failed try and milestone-commits the win — closing with a changelog beat and an offer to bump semver + tag.
- Implement-Feature Loop — plan → gh tickets → code/verify/changelog/commit per ticket → human browser test → ship - The generic feature-execution cadence: a signed-off plan becomes gh tickets, each ticket lands as verified code + a changelog beat + a conventions-clean commit, and the run closes with a human browser test and a ship() commit.
- Loop through a spec — write the plan, implement, test, changelog, commit, repeat until Shipped - The phase loop that took Augment-From-DB-Flow from Signed-Off to Shipped in one day: plan, implement, prove, changelog, commit — per phase.
- Sweep — Local & Federated Design System for Fidelity - The repeatable procedure for checking a member’s CSS against the federal contract. The one sanctioned exception to the two-file rule.