Hand back the whole prompt, never a delta (all projects)

Read reference/campaign-launch.md before writing a loop launch file.

Whenever Rob asks for a prompt, or you revise one you already gave him, output the entire prompt in one copy-pasteable block. Never hand back only the changed lines, a “replace this paragraph with” instruction, or a fragment to insert.

He pastes these into TUI coding-agent harnesses, where reassembling a prompt from a base plus deltas has no editor and no diff view, and it is easy to drop or double-paste a fragment.

Re-emit the whole thing every time, however long it is and however small the change. Length is not a reason to send a delta. Applies to agent briefs, steering messages, and both compaction-cycle artifacts. A loop’s launch message is a file instead, see below.

This covers prompts, not files. A sourcebook or runbook on disk is edited in place with targeted edits as normal. An unlaunched charter may be edited in place; once a root has adopted it, amendments go out as a superseding file. It also does not mean re-emitting an unchanged prompt he already has: when you do emit one, it is complete.

A loop’s launch message is a FILE, and this rule does not claim it

A loop’s launch message is a file beside its charter, in the form the loop contract fixes, not a chat block.

Write the file instead of pasting the launch message into chat, not as well as. Reply with the two absolute paths and a short summary of what changed. Rob opens the file and copies from there.

The everything-in-one-block requirement still applies to the file’s contents: it is written whole every time, never patched with a delta, for the same reason. What changes is where it lands.

Chat blocks remain right for one-off steering messages, agent briefs and both compaction-cycle artifacts, none of which have a loop directory to live in.