Bounded agent loops

Security loops

A loop is not installed. It is pasted.

What makes it a loop is the stop condition.

Browse 7 loops Rules of engagement

7 loops5 phases35 steps0 installs required4 scanners · clean

Anatomy of a loop

4 parts

01Scope: What it may touch, and what it must not.
02Cycle: The steps it repeats while evidence improves.
03Escalation: The decisions it hands back to you.
04Stop condition: What has to be true for it to finish.

Engagement chain

filter the register by phase

Reconmap the surface1 loop Exploitprove the impact1 loop Hardenclose the gap2 loops Respondcontain the event2 loops Attestprove it to auditors1 loop · clear

The register

1 of 7

/

1 of 7

RefLoopStop conditionStepsCopiesOpen

Attestprove it to auditors

0x07Control evidence collectionEvery control has period-covering, attributable evidence, or a named gap with an owner and a date.5 steps1 copyopen →

Rules of engagement

Every loop here assumes a repository or project you are authorized to change, and each one is written to stop and ask rather than take a major upgrade, touch production, or accept a risk on your behalf. Read the prompt before you paste it — you are handing it to an agent that acts with your credentials.