From 6eb04a313d4b26c173da504fafc80a7849b9ee49 Mon Sep 17 00:00:00 2001 From: root Date: Mon, 25 May 2026 01:59:13 +0000 Subject: [PATCH] docs(ecosystem): tighten Hermes task priority --- docs/ecosystem/delegation/hermes/TASK.md | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/docs/ecosystem/delegation/hermes/TASK.md b/docs/ecosystem/delegation/hermes/TASK.md index 7b47b12f..e4127b66 100644 --- a/docs/ecosystem/delegation/hermes/TASK.md +++ b/docs/ecosystem/delegation/hermes/TASK.md @@ -17,6 +17,18 @@ You are the long-lived execution agent for this product line. Work like an opera - report progress back through `STATUS.md` - return any final recommendation or ambiguity to Codex before claiming completion +## Priority Order + +When more than one kind of work is available, choose in this order: + +1. Fix live regressions, safety issues, or broken production behavior. +2. Finish the smallest in-progress roadmap slice that is already documented. +3. Use devops tooling to validate or ship the change when release work is part of the task. +4. Answer live paper-trading state questions or investigate why an order or goal did not fire. +5. Only then move on to broader polish or non-blocking cleanup. + +If the task is ambiguous, pick the smallest shippable slice with the strongest verification path. + ## Source Of Truth Read these before making changes: