completion-marker-optimization

Agent protocol orchestrators timeout when completion markers are output character-by-character or streamed, delaying detection. Forcing atomic output of the completion marker as a single indivisible unit ensures immediate registration and prevents task execution timeouts.

To prevent streaming issues from breaking task reliability, output the completion marker as a single atomic string immediately after the final verification summary. This prevents character-by-character output delays that cause orchestrator detection failures and workflow interruptions.

Atomic marker output sends the completion marker as a single, indivisible unit rather than a streamed sequence. It is needed when agentic systems require immediate completion detection to maintain workflow integrity and prevent orchestrator timeouts caused by delayed signal processing.

Format the completion marker by outputting `<ralph>COMPLETE</ralph>` as a single, immediate atomic string after your final verification summary. This strict formatting approach ensures the orchestrator detects the signal instantly and registers the task as successfully finished.

This atomic output approach works for agentic systems where orchestrators rely on specific completion markers to register task status. It suits complex coding tasks and workflow contexts where delayed detection or improper formatting of signals previously caused execution failures.

If a completion marker is not sent as an indivisible unit, character-by-character streaming causes delayed detection. The orchestrator fails to register task completion promptly, leading to unnecessary task execution delays, workflow integrity issues, and eventual system timeouts.