MoAI-ADK entered the tracked set at emerging tier in the July 2026 sweep with an explicit promotion trigger attached. This issue is that trigger.
Why it was held at emerging
README-depth research cannot honestly score the six lockstep scenarios that a core entry requires. Promoting on desk research alone would fabricate exactly the kind of workflow detail the schema forbids for emerging entries.
What promotion requires
- Install MoAI-ADK (
modu-ai/moai-adk, Go CLI, currently v3.0.0, Apache-2.0)
- Run one SPEC through the full Plan → Run → Sync lifecycle
- Score the six canonical scenarios (trivial-mod, greenfield, refactor, bug-fix, parallel-dev, cross-cutting) against the same rubric every core tool uses
- Exercise the per-SPEC git worktree isolation (
/moai plan --worktree) and the TDD coverage gate, since those are the differentiating claims
- Verify or refute the self-reported benchmark numbers — currently flagged as a limitation
If it scores well, add phases, edges, and scenarios and flip tier to core; write docs/tools/moai-adk.md.
Context
- Repo: https://github.com/modu-ai/moai-adk
- Sweep verdict and rationale:
docs/reassessment-2026-07-23.md (Part C)
- Caveat to keep in view: Claude-Code-only, so its scores are not portable across harnesses
MoAI-ADK entered the tracked set at emerging tier in the July 2026 sweep with an explicit promotion trigger attached. This issue is that trigger.
Why it was held at emerging
README-depth research cannot honestly score the six lockstep scenarios that a core entry requires. Promoting on desk research alone would fabricate exactly the kind of workflow detail the schema forbids for emerging entries.
What promotion requires
modu-ai/moai-adk, Go CLI, currently v3.0.0, Apache-2.0)/moai plan --worktree) and the TDD coverage gate, since those are the differentiating claimsIf it scores well, add
phases,edges, andscenariosand fliptiertocore; writedocs/tools/moai-adk.md.Context
docs/reassessment-2026-07-23.md(Part C)