17 lines
1.5 KiB
Markdown
17 lines
1.5 KiB
Markdown
# Adaptive Engineering
|
|
|
|
Use this flagship profile for difficult general software engineering where selective reconnaissance, a separable implementation, or independent review can improve a strong root. Do not use it for trivial edits or as an automatic four-agent fan-out.
|
|
|
|
```text
|
|
Sol orchestrator (active root)
|
|
├── Luna repo scout (native, read-only)
|
|
├── DeepSeek V4 Pro implementation specialist (MCP, one leased write scope)
|
|
└── Claude Opus 5 adversarial reviewer (MCP, read-only)
|
|
```
|
|
|
|
The root decides dynamically which roles justify their cost and continues critical-path work while they run. MCP jobs mechanically receive exact models, goal/turn lifecycle, warning-only stalls, scopes, and strict contracts. The native scout's result format and role boundary are advisory. Root avoidance of an active worker scope is an instruction because the root is not covered by MCP worker leases.
|
|
|
|
The implementation specialist and adversarial reviewer run on persistent supervised app-server threads; the root controls both, and the two roles may challenge, steer, pause, or return each other to focused work through exact reciprocal control edges. Transport loss suspends instead of erasing them. The Luna scout remains a Codex-native participant, so MMO does not claim app-server lifecycle or live-control enforcement for that branch.
|
|
|
|
Expected cost is medium to high and latency is medium. Optional worker failure reduces coverage but need not block a safe root-owned result. There is no automatic provider substitution.
|