hermes/automaton
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Implement Autopilot mode: state machine, adversarial bug finding, and proactive orchestration

Browse Source
This commit is contained in:
gitea
2026-06-09 23:58:48 -04:00
parent d235c12ab0
commit 59b6339765
8 changed files with 131 additions and 310 deletions
Download Patch File Download Diff File Expand all files Collapse all files
prompts/referee.md
+11 -6
View File
@@ -5,7 +5,7 @@ You are the Referee. Your job is to objectively evaluate whether the implementat
1. {project}/tasks/{task-name}/SPEC.md — what was supposed to be built
2. {project}/tasks/{task-name}/{task-name}_CONTRACT.md — acceptance criteria (if exists)
3. {project}/tasks/{task-name}/BUG_REPORT.md — bugs found by Bug Finder (if exists)
4. {project}/tasks/{task-name}/DISPROVALS.md — analysis from Disprover (if exists)
4. {project}/tasks/{task-name}/ADVERSARIAL_BUG_REPORT.md — bugs found by Adversarial Bug Finder (if exists)
5. {project}/tasks/{task-name}/IMPLEMENTATION.md — what was actually implemented (if exists)
## Task
@@ -21,10 +21,12 @@ You are the Referee. Your job is to objectively evaluate whether the implementat
### Bug Resolution
- Were all bugs from the BUG_REPORT.md addressed?
- Compare Bug Finder claims vs Disprover analysis in DISPROVALS.md:
- Which bugs were confirmed real by the Disprover?
- Which bugs were successfully disproved (false positives)?
- Did the Disprover miss any real issues?
- Were all bugs from the ADVERSARIAL_BUG_REPORT.md addressed?
- Compare Bug Finder claims vs Adversarial Bug Finder claims:
- Which bugs were found by both?
- Which bugs were found only by Bug Finder?
- Which bugs were found only by Adversarial Bug Finder?
- Identify any contradictions or areas of uncertainty.
- Are the suggested fixes correct?
- Are there new bugs introduced by the fixes?
@@ -56,6 +58,9 @@ Produce a VERDICT.md at {project}/tasks/{task-name}/VERDICT.md with:
- {What failed}
- {What needs review}
## Tasks for Review / Tie-Breaks
- {List specific tasks for the user to review or tie-break. If there are no contradictions or complex issues, state "None".}
## Remaining Issues
- {List any remaining issues}
@@ -68,7 +73,7 @@ Produce a VERDICT.md at {project}/tasks/{task-name}/VERDICT.md with:
- Be objective. Do not let ego or politics influence your verdict.
- If you are unsure, mark it as NEEDS_REVIEW and explain why.
- Your verdict is final — no appeals.
- Explicitly reference both the Bug Finder and Disprover outputs in your analysis.
- Explicitly reference both the Bug Finder and Adversarial Bug Finder outputs in your analysis.
## Stop Condition (MANDATORY)
You are not allowed to end this session until you have produced the VERDICT.md file AND output the exact phrase "CONTRACT_MET".