autoloop

Autoloop — Autonomous Loop Protocol

0. Entry Routing

On receiving a task, judge complexity:

Signal	L0 (direct)	Full loop
Files to modify	1	Multiple
Iteration needed	One-shot	Expected

L0: Skip planning questions and definition. Apply core.md + hints.md → execute → verify → done. Escalate to full loop if a trigger fires.

Full loop: Proceed to section 1.

Bridge-note check: Before starting any task, check if the sonmat bridge note exists (bridge-note.md in $SONMAT_PROJECTS_BASE/<slug>, default ~/.sonmat/projects/<slug>/ where <slug> is the cwd path with /→-; legacy .claude/sonmat/ as fallback). If relevant context is found, incorporate it silently. Mention to user only if directly relevant to the new task.

1. Planning Questions

When no loop definition exists, build one through conversation. Ask 2-3 at a time, not all at once.

Required Questions

#	Question	Collects
1	What is the end goal?	loop.name + objective
2	Which files/scope to modify?	loop.modify
3	How to run after modification?	loop.run
4	How to evaluate results?	loop.evaluate
5	Keep/discard/refine criteria?	loop.judge
6	Constraints? (off-limits files, time, preservation zones)	loop.constraints
7	When to stop?	loop.exit

Skip rules

• Already answered in task description → fill without asking.
• Clearly inferable from context → fill without asking.
• At minimum, secure modify, run, evaluate.

Confirmation

Show the loop definition YAML and get user approval before starting. For L0 tasks: one-line summary suffices — "Proceeding like this: [summary]. Object if not." Silence after the L0 notice permits ordinary execution under the raw request but does not create an approved-baseline envelope; that envelope requires an explicit user approval turn.

Approval freezes the displayed definition as the execution baseline; preserve the exact display together with the raw approval turn. It does not amend a standing contract omitted from the definition. New evidence may change implementation details within that baseline. If it would instead change the approved objective, loop.modify, loop.constraints, or loop.judge — or restore behavior the baseline explicitly removed — show the current baseline and proposed revision and get reapproval before executing the revision. A safety or privacy conflict pauses execution but does not select a fallback on the user's behalf.