Skip to content

feat: v5 evolution layer — EVOLUTION.md, research/, decisions/ — closes #2 - #7

Merged
Stolyarovmn merged 1 commit into
mainfrom
feat/v5-evolution-layer
Apr 29, 2026
Merged

Stolyarovmn merged 1 commit into
mainfrom
feat/v5-evolution-layer

Conversation

@Stolyarovmn

Copy link
Copy Markdown
Owner

Summary

Implements the first set of v5 evolution artifacts from #2. All five open questions were answered in a comment before this PR was opened.

New files:

  • — four-stage evolution protocol: intake → research → decision → promotion
    • — source review infrastructure
    • — design decision records

Updated:

  • — added to mandatory read-order after

Open questions resolved (see #2 comment):

  • EVOLUTION.md is mandatory read-order material (Q1 ✅)
  • chosen over (Q2 ✅)
  • Worktree isolation: parallel tasks only by default (Q3 ✅)
  • Model routing: agent policy docs for now (Q4 ✅)
  • Discussions: informal intake only, Issues remain canonical (Q5 ✅)

PR opened by Claude (coordinator agent, 2026-04-29)

Closes #2

Implements the evolution mechanism from #2:
- EVOLUTION.md: four-stage protocol (intake, research, decision, promotion)
- research/: source review folder with README and template
- decisions/: design decisions folder with README and template
- AGENTS.md: add EVOLUTION.md to mandatory read-order

All open questions from #2 answered before this PR:
- EVOLUTION.md added to read-order after PRINCIPLES.md (Q1)
- decisions/ naming chosen over adrs/ (Q2)
- worktree isolation deferred to parallel-only by default (Q3)
- model routing stays in agent policy docs for now (Q4)
- GitHub Discussions = informal intake only (Q5)

Closes #2

Co-authored-by: Claude (coordinator agent) <noreply@anthropic.com>
@Stolyarovmn
Stolyarovmn merged commit bcb5544 into main Apr 29, 2026
1 check passed
@Stolyarovmn
Stolyarovmn deleted the feat/v5-evolution-layer branch May 25, 2026 08:22
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.

Proposal: MultiAgentSystem v5 layered evolution plan

2 participants