run-bridge

You can automate sprint planning and review cycles by invoking the run-bridge command to start an autonomous iteration loop that coordinates planning, red-team checks, and Bridgebuilder reviews across multiple development iterations.

A Bridgebuilder loop is an autonomous improvement process that continuously plans, reviews, and documents software iterations by coordinating sprint planning, vision capture, and grounded truth generation under configuration-driven guardrails.

You generate grounded truth artifacts and vision outputs by running the autonomous loop, which captures vision, grounds insights, and stores provenance in grimoires and loa directories throughout the iteration cycle.

Yes, you can enforce protected branch safeguards and time-bound constraints because the loop applies configuration-driven guardrails and gated execution to prevent unauthorized changes during the orchestrated software iterations.

No, the autonomous iteration loop does not require external dependencies, as it operates entirely through provided scripts and configuration files to manage run-state, vision outputs, and provenance storage.

You should avoid using an autonomous improvement loop when your project lacks clear configuration-driven guardrails or when your development workflow cannot accommodate gated execution and time-bound iteration constraints safely.