# The algo records whose domain is governed-plan-loop

This index as JSON: https://banes-lab.com/json/api/facets/algo/domain/governed-plan-loop

## Entries

- [Living Plan State](https://banes-lab.com/records/algo/living-plan-state.md): Treat the plan as durable append/update-only state — tasks carrying status and grounding, a considerations backlog, and a dismissed-key set — maintained every turn and re-delivered on restart, so anything discovered mid-pass is retained instead of falling out of scope.
- [Boundary Reconciliation](https://banes-lab.com/records/algo/boundary-reconciliation.md): Capture considerations during a phase but act on them only at the phase boundary — triage each open consideration against code and canon into a confirmed task or a dismissed resolved-false key, deduping new opens against the confirmed and dismissed sets before triage.
- [Phase Close Gate](https://banes-lab.com/records/algo/phase-close-gate.md): Make completion a gated state of the plan rather than a judgment call — a phase closes only when all tasks are done, a dry reconciliation pass holds, verify is clean for the chosen scope, and the coverage graph confirms the ripple set; otherwise the loop returns to execution.
- [Plan Phase Verification](https://banes-lab.com/records/algo/plan-phase-verification.md): Before a composed plan reaches the developer, the engine loops it back through evidence, completeness, and adversarial-skepticism passes, reconciles the findings into the plan, and increments a loop-owned pass counter the model cannot forge; a render boundary blocks an unverified plan.
- [Governed Autonomous Plan Loop](https://banes-lab.com/records/algo/governed-autonomous-plan-loop.md): Drive a large task to completion under gates — seed per phase, investigate, execute, self-inform from canon and self-audit, capture considerations, reconcile at the boundary, and close only when the plan is a mechanically resolved state, then re-seed the next phase.
- [<Governed Plan Concern>](https://banes-lab.com/records/algo/governed-plan-concern.md): <Seed the phase> → <Investigate and execute under gates> → <Self-inform from canon and self-audit> → <Capture and reconcile considerations at the boundary> → <Close only on a mechanically resolved gated state> → <Re-seed the next phase>