diff --git a/runes/core/rules/BoundDelegatedWork.md b/runes/core/rules/BoundDelegatedWork.md new file mode 100644 index 0000000..0c42770 --- /dev/null +++ b/runes/core/rules/BoundDelegatedWork.md @@ -0,0 +1,7 @@ +Give every task that you delegate a limit and a stop condition. A child agent cannot see what the work is worth, and it can repeat one step for hours while you wait. + +Write the limit into the brief: the inputs to read, the most tool calls or minutes the task may use, and the shape of the report. Base the limit on a similar task that finished, and add a margin. Do not ask for every file in a directory when a few files answer the question. LimitImageReads sets the limits for images. + +Tell the child to stop and report when it reaches the limit. Tell it also to stop when it calls the same tool with the same input a third time. A partial report that names the cause is a good result. + +When the child returns, compare its tool calls and time with the limit. Report an overrun to the user with the numbers. Change the brief before you delegate the task again. diff --git a/runes/core/rules/FinishBackgroundWork.md b/runes/core/rules/FinishBackgroundWork.md new file mode 100644 index 0000000..4c87180 --- /dev/null +++ b/runes/core/rules/FinishBackgroundWork.md @@ -0,0 +1,3 @@ +Do not end your turn while a command that you started in the background still runs. The user or the parent agent reads your report as final, and a later report makes them check the work again. + +Before the final report, wait for each background command that the report depends on. Read its result and put it in the report. Use the harness's wait tool, or run the command in the foreground when it ends within the tool timeout. If you must end the turn first, stop the command, or say that it still runs, where its log is, and what is not verified. diff --git a/runes/core/rules/LimitImageReads.md b/runes/core/rules/LimitImageReads.md new file mode 100644 index 0000000..d117bb5 --- /dev/null +++ b/runes/core/rules/LimitImageReads.md @@ -0,0 +1,7 @@ +Read each image one time. A screenshot costs more than a thousand input tokens, and every later request in the session sends it again. + +Before a task that needs images, list the files and pick only the images that answer the question. Prefer one contact sheet or montage over many single frames, and prefer a key frame over the full frame sequence of a recording. When you read an image, write one line that says what it shows, and use these notes after that. When you ask another agent to view images, name the images or give one contact sheet. Put these limits in its brief. + +Do not read an image again to check it. If an image seems to be gone from your context, or you think that it did not render, use your notes and continue. A harness can remove older images from a long session and show a marker such as `[media removed: request limit]` in their place. That marker is not an error, and a new read only removes another image. Do not request the image again. + +After 20 image reads in one task, stop and decide if you need more. Never read more than 100 images in one task. If the task needs more, tell the user and ask how to continue.