Nishi FamilyCompare › Autonomous Team and Software Agents

Nishi vs the Field

Autonomous Team and Software Agents — mechanically measured, liar-killed, sovereign.

Nishi vs SWE-agent and OpenHands and Aider and AutoGen

How this is scored. Every Nishi cell is measured: the generator reads the real organ source on disk and requires the implementing symbol to exist (no self-grading). Competitor cells record documented capability presence. Best=leads this axis, Yes=present, Part=partial, No=absent. This is capability presence, not depth or scale: the majors lead on index size and neural ranking. Nishi's genuine exceeds are the sovereignty / neutrality / determinism axes.
CapabilityNishiSWE-agentOpenHandsAiderAutoGenNotes
Autonomous execute-and-verify loop on machine targetsYesYesBestYesYesLIVE-gated 2026-07-06: 3/3 targets advanced (2 evo-synth held-out + compiler-health witness); its own output prints the honest coverage: 0 of 104 stalled workstreams declare a machine-executable target yet
Anti-drift coach gating rung claims (liar-killer)YesNoNoNoNoGate GREEN then census then coach; only COACH-OK claims a rung -- checks U-axes, dated bars, claim-vs-proof ratio, freshness; no field agent gates its own success claims against measured censuses
Work board with heartbeat livenessYesNoPartNoPartThe board refuses to trust a stale ACTIVE label (imports nx_heartbeat_str, wellformed-checked); OpenHands and AutoGen track task state without staleness refusal
Governed scheduler (warden-owned conductor pulses)YesNoNoNoBestRatchet and training pulses run ONLY governed, never ad-hoc; AutoGen is the orchestration-framework bar
Organ lineage genealogistYesNoNoNoNoAncestry and relatedness of organs tracked as data; the field tracks conversation history, not artifact lineage
Honest autonomy meteringYesNoNoNoNoMeasures the Claude-touch bar toward 0 -- the team scores its OWN dependence honestly; no field agent measures its own autonomy
Teacher and practice loopYesNoPartNoPartToy-practice honest (the 07-05 diagnosis); OpenHands and AutoGen have tutorial-ish agent training flows; NOTE this organ is one of the 19 live shadow-name collisions (runtime + _hdl_build copies differ)
LLM-driven code authoring (novel organ building)NoYesBestYesYesTHE headline absent: every novel organ falls to Claude (diagnosis 2026-07-05, unchanged today); LLM code-authorship is the field's entire product
Issue-to-patch repository pipelineNoBestYesYesNoSWE-agent was born from SWE-bench issue resolution
Git-native pair-programming edit loopNoYesYesBestNoAider is the bar: repo-map + diff edits + auto-commit
Sandboxed per-task agent runtimeNoPartBestNoPartOpenHands docker runtime is the bar; our container host exists as a SEPARATE domain (950/1000) but is not wired under the team
Multi-agent conversation frameworkNoNoPartNoBestAutoGen is the bar; our conductor schedules pulses, it does not orchestrate agent dialogue
Long-horizon planning and memory for agentsNoPartPartPartPartHot frontier axis; our WMS registry and memory files serve Claude, not the team organs
Benchmark-scored coding evaluationNoBestPartPartPartSWE-bench pass-rate is how the field proves itself; we have qabench for research, nothing scores team coding
Human-in-the-loop approval flowsNoPartYesYesPartOperator gating exists by DOCTRINE and the workflow domain ships DENY-WINS approvals, but no team organ carries approval flows
Web UI for agent sessionsNoNoBestNoPartOpenHands app is the bar; our /project portal shows projects, not live agent sessions
Cost and token budget managementNoPartPartPartPartEvery field agent meters provider spend; ours has nothing to meter (see the zero-token exceed) -- absent as a feature, moot by construction
Zero-LLM-token sovereign autonomous loopBestNoNoNoNoThe whole execute-verify-advance loop is compiled sovereign organs: 0 tokens, 0 API spend, deterministic, offline; every field agent burns provider tokens per action
Refusal-over-fabrication by constructionBestNoNoNoNoGate-proven neg-control: a non-zero exit NEVER advances -- novel work is refused (NEEDS_TUTOR), not faked; the field's agents are notorious for claiming unverified success
coverage 473/1000EXCEEDS 2PRESENT 7ABSENT 10
Honest verdict. The Nishi team is a REAL governance-and-verification shell around autonomous work -- a zero-token machine execution loop that VERIFIES before advancing and REFUSES to fake novel work (gate-proven neg-control), an anti-drift coach that liar-kills SOTA claims against live censuses, heartbeat-liveness boards, governed conductor pulses, lineage tracking, and an honest autonomy meter. What it is NOT yet is a builder: the 2026-07-05 diagnosis stands unchanged -- zero of the 104 stalled workstreams declare a machine-executable target, the synthesizer covers toy arithmetic, and every novel organ still falls to Claude, while SWE-agent, OpenHands, and Aider ship LLM code-authorship as their entire product. The honest climb: give real workstreams machine-readable targets with heartbeat-on-advance, grow the synthesizer past toys, then wire an LLM-authoring lane UNDER the coach and verify gates the shell already provides -- the governance the field lacks wrapped around the authorship we lack.

Generated by nx_swcompare_matrix (sovereign NishiLang organ) from knowledge/compare/team.matrix — every Nishi cell verified against real organ source on disk. Zero JS, zero trackers.