Files
crimson_leaf_publishing/templates/chapter_roundtable.yml
David Baity 4c9222960d fix: template prompt bloat and variable substitution failures
- chapter_polish: remove sections:deliverables — chapter text already in
  {chapter_text}; this caused 150KB+ prompts for late chapters (40MB logs)
- chapter_roundtable: require structured CONSENSUS REACHED block so
  key_changes is always formatted as an extractable string; change
  key_changes schema from list to string to match
- book_chapter: remove sections:history to reduce context; restructure
  Pass 0 to plan-only (no prose output) so the chapter is only written
  once in Pass 1 instead of twice; add explicit instruction in package
  hint to copy full chapter_text into spawn context
- short_story: remove sections:history and sections:deliverables (standalone
  task, needs neither); restructure Pass 0 to plan-only, Pass 1 to write;
  add note to handle literal {genre_name} placeholders gracefully
- recipe_develop, ai_article_write, blog_write: remove sections:history
  (these standalone tasks do not need full project conversation history;
  deliverables kept so they can read the research/plan file)

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
2026-03-12 09:05:45 -04:00

96 lines
2.7 KiB
YAML
Raw Blame History

This file contains ambiguous Unicode characters

This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.

name: chapter_roundtable
description: >
Editorial roundtable — available editors debate the chapter in 23 structured rounds.
Each round, each participant responds to the others' most recent positions.
The output is a consensus critique (or documented disagreement) for the polish step.
debug: true
participant_prompt:
- "= identity.md"
iteration_limit: 3
convergence_signal: "CONSENSUS REACHED"
sections:
- agent
- project
- participants
- participants_prompt
- message
- instructions
steps:
- type: think
rotate_participants: true
loop:
max_iterations: 9
hint: |
You are {agent.name}, an editor in the editorial roundtable for this chapter.
{agent.identity}
CHAPTER REFERENCE: {chapter_ref}
GENRE: {genre_name} | AUDIENCE: {genre_audience}
---
CHAPTER TEXT:
{chapter_text}
---
Round {task.iteration} of the editorial debate.
Read the chapter carefully from your editorial perspective.
React to what other editors have written in prior rounds above.
Where you agree, say so clearly. Where you disagree, argue your position
with evidence from the text. If you have changed your mind, say so.
Cover the areas most relevant to your role:
- Story structure and pacing
- Character voice and consistency
- Line-level clarity and prose quality
- Continuity with prior chapters and world rules
If the group has reached sufficient consensus for the polish step,
end your response with this EXACT block — no variations, no paraphrasing:
CONSENSUS REACHED
CRITIQUE: [One concise paragraph summarizing the full editorial consensus]
KEY CHANGES:
- [Specific change 1]
- [Specific change 2]
- [Specific change 3 if needed]
VERDICT: [PASS / REVISE / REWRITE]
- type: package
schema:
consensus_critique: string
chapter_verdict: string
key_changes: string
spawn:
- task_type: chapter_polish
task_name: "Polish: {chapter_ref}"
agent_name: Iris
context:
chapter_text: "{chapter_text}"
consensus_critique: "{consensus_critique}"
key_changes: "{key_changes}"
chapter_verdict: "{chapter_verdict}"
genre_name: "{genre_name}"
genre_audience: "{genre_audience}"
chapter_ref: "{chapter_ref}"
adjudication:
enabled: true
pass_threshold: 60
deliverable_type: coordination
criteria:
completeness:
weight: 40
description: "All viewpoints and concerns addressed"
consensus_clarity:
weight: 35
description: "Clear outcome or decision documented"
actionability:
weight: 25
description: "Next steps are concrete and assignable"