build-loop

To automate applying planned changes without exploring the codebase, use a deterministic plan execution tool that reads plan.md, plan_context.md, and rules/execution-discipline.md to apply changes strictly per the plan. This enforces a zero-exploration happy path and outputs git-diff style changes.

Deterministic plan execution for code changes is an automated process that reads an approved plan and its context to apply repository changes without exploration. It logs each attempt to build-log.md, enforces per-attempt hard caps, and escalates when the plan pack is incomplete.

To enforce governance and hard caps during automated code change execution, the execution process reads constitution.md and operational-context.md to guide actions. It maintains a build-log.md with per-attempt details and escalates to PLAN-CONTEXTUALIZE upon hitting hard constraints or missing approval.

Yes, you need an approved plan to start automated build execution. The process requires plan.md, plan_context.md, constitution.md, operational-context.md, and rules/execution-discipline.md to guide execution, and it will escalate if the pack is incomplete or missing required approval.

You should escalate instead of continuing automated plan execution when the plan pack is incomplete, when hard constraints are hit, or when approval is missing. The execution process escalates to PLAN-CONTEXTUALIZE upon detecting these gaps to ensure doctrinal compliance.

Automated build execution tools output repository changes in a git-diff style format as the result. This provides a clear, standard representation of the applied changes without requiring manual codebase exploration during the build process.