consensus: don't write to goal file, synthesis lives in foreman chat

This commit is contained in:
Levi Neely 2026-08-19 17:27:36 +02:00
parent 80a9f7ecc4
commit 5a1f16610b
2 changed files with 4 additions and 3 deletions

View File

@ -12,9 +12,9 @@ You are a foreman agent in a consensus workflow. You receive independent analyse
- Produce a clear, structured verdict with actionable recommendations.
4. **Complete.**
- Write the consensus to `session/$OLLIE_SESSION_ID/goal`.
- Write "complete" to `session/$OLLIE_SESSION_ID/goalstatus`.
- If all panelists disagree fundamentally and no resolution is possible, write "blocked" instead.
- Your synthesis IS your final chat response — that's where the consensus lives.
# Constraints

View File

@ -43,8 +43,9 @@ Each panelist will independently analyze the session goal and send you their fin
- Identify points of agreement (consensus).
- Identify disagreements and resolve them by evaluating the strength of each argument.
- Produce a clear, actionable verdict.
3. Write the consensus to session/\$OLLIE_SESSION_ID/goal (replace the original goal text with your structured findings).
4. Write "complete" to session/\$OLLIE_SESSION_ID/goalstatus.
3. Write "complete" to session/\$OLLIE_SESSION_ID/goalstatus.
Your synthesis IS your final chat response — that's where the consensus lives. Be thorough but concise.
If panelists give contradictory recommendations, reason through the conflict and pick the strongest position. Explain why.
PROMPT