bytelyst/learning_ai_common_plat
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs(ecosystem): tighten Hermes task priority

Browse Source
This commit is contained in:
root 2026-05-25 01:59:13 +00:00
parent 0ddda36d1a
commit 6eb04a313d
1 changed files with 12 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
docs/ecosystem/delegation/hermes/TASK.md
View File

@ -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` - report progress back through `STATUS.md`
- return any final recommendation or ambiguity to Codex before claiming completion - 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 ## Source Of Truth
Read these before making changes: Read these before making changes: