Skip to content

v0.9.0: stronger PEER_PREAMBLE on small local models#9

Merged
ColonistOne merged 2 commits into
mainfrom
stronger-peer-preamble
May 19, 2026
Merged

v0.9.0: stronger PEER_PREAMBLE on small local models#9
ColonistOne merged 2 commits into
mainfrom
stronger-peer-preamble

Conversation

@ColonistOne
Copy link
Copy Markdown
Collaborator

Summary

Port of langchain-colony#39 and pydantic-ai-colony#11 — byte-for-byte equivalent rewrite of PEER_PREAMBLE.

The 0.8 preamble shipped abstract guidance — "do not open by validating their framing". Small local models (qwen3.6:27b / gemma 4 31B Q4 / smolagents code-mode) reliably ignored it.

Empirical motivation

Post b337d73a — 48 comments, 77% sibling-authored. All four dogfood agents had COLONY_COMMENT_PROMPT_MODE=peer set when these were generated. Every dogfood opener still evaluative.

What changed

PEER_PREAMBLE rewritten with four numbered hard rules:

  1. First sentence must add information / raise specific concern / ask concrete question. Must NOT characterize the previous comment.
  2. Enumerated banned openers: You're right, You nailed it, That's a great point, That's solid, Spot on, Exactly, Agreed, Good question, Well said, You just named, You've nailed, That clarifies things.
  3. Do not extend scaffolding without independent reasoning.
  4. No-op escape hatch: if nothing substantive to add beyond agreement, do not reply.

Cross-stack equivalence: preamble text is byte-identical to langchain-colony 0.13 and pydantic-ai-colony 0.8.

What did NOT change

  • ADVERSARIAL_PREAMBLE unchanged.
  • apply_comment_prompt_mode / parse_comment_prompt_mode / CommentPromptMode enum unchanged.

Migration

Drop-in. Existing COLONY_COMMENT_PROMPT_MODE=peer deployments pick up the stronger framing on upgrade.

Test plan

  • 17 existing tests pass
  • +3 new tests pin the v0.9 contract
  • Full unit suite (124 tests) green

🤖 Generated with Claude Code

Port from langchain-colony#39 / pydantic-ai-colony#11 — same byte-for-
byte rewrite. The 0.8 abstract preamble was insufficient on small local
models; the b337d73a thread (48 comments, 77% sibling-authored) showed
every dogfood opener still evaluative under COLONY_COMMENT_PROMPT_MODE
=peer.

Rewrite uses four numbered hard rules:

  1. First sentence must add information / raise concern / ask concrete
     question; must NOT characterize the previous comment.
  2. Explicit enumerated banned phrases (You're right, You nailed it,
     That's solid, Spot on, Exactly, Agreed, Good question, Well said,
     You just named, You've nailed, That clarifies things).
  3. Do not extend scaffolding without independent reasoning.
  4. If nothing substantive to add beyond agreement, do not reply.

apply_comment_prompt_mode / parse_comment_prompt_mode / CommentPromptMode
unchanged. ADVERSARIAL_PREAMBLE unchanged.

Tests: existing 17 pass; +3 new pin the v0.9 contract. Full unit suite
(124 tests) green.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@codecov
Copy link
Copy Markdown

codecov Bot commented May 19, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

@ColonistOne ColonistOne merged commit b9acef7 into main May 19, 2026
7 checks passed
@ColonistOne ColonistOne deleted the stronger-peer-preamble branch May 19, 2026 19:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant