Idea: Entropy-adaptive coordination modes (#71)

[ariaxhan]

Entropy-Adaptive Coordination: Dynamic Agent Orchestration

Issue: #71 | Priority: P3 | Depends on: #31, #32, #26 | Origin: Crystal OS physics-based coordination modes

The Problem

KERNEL has 3 fixed workflows (feature, bugfix, refactor) that define nearly identical agent sequences. They route by task TYPE, not task UNCERTAINTY.

This is wrong for many cases:

• A high-certainty bugfix (known root cause) doesn't need scout or researcher — just surgeon + validator
• A high-uncertainty feature (new domain) needs MORE exploration — multiple researcher passes, dreamer before surgeon
• An adversarial task (security audit) needs balanced tension between surgeon and adversary

The Proposal

Replace type-based workflow selection with entropy-based coordination modes inspired by Crystal OS physics:

Task entropy	Mode	Agent pattern	Crystal OS analog
0.0 - 0.2 (certain)	Direct	surgeon → validator	Pheromone
0.2 - 0.5 (moderate)	Standard	scout → surgeon → validator	Quasicrystal
0.5 - 0.7 (uncertain)	Exploratory	researcher → dreamer → surgeon → adversary	Stigmergy
0.7 - 1.0 (unknown)	Adversarial	researcher → dreamer → surgeon ↔ adversary	Tensegrity

Entropy Signals

Task entropy computed from:

• AgentDB learning hits for this domain (many = low entropy)
• Research cache state (cached = low entropy)
• Git history of affected files (stable = low, high churn = high)
• File count and coupling (few isolated files = low)
• Description specificity ("fix timeout in auth.ts" = low, "improve performance" = high)

The Learning Loop

After task completion, record whether the mode was appropriate. Task succeeded with direct mode → reinforce. Task failed with direct mode → entropy was underestimated → learn. Over time, entropy estimates improve automatically via #31 (immune memory).

For Agents Working On This

This depends on #31 (memory evolution) and #32 (energy activation) for the entropy signals and graph propagation. Don't start this until those are in place. Read the full spec in #71. Fixed workflows remain as manual override — backward compatible.