GitHub README / operator's tally and failure examples · Source language: English
Even when several AIs share the work, the judgment of completion is made separately
The maker of Orka adds review by a different model and checks against the original requirements in development that uses several AIs.
- Who:
- Orka's maker and operator, and GitHub user ugorur
- Scope:
- Eight projects by the same operator. The README and tally material are treated as one observation
- Source published:
- First publication date unconfirmed
- Period observed:
- August–October 2026 / later tally September 28–October 10
- Editorial check:
- 2026-10-23
Only the source ID is saved in this browser. Nothing syncs across devices.
What was confirmed
- The public tally covers 8 projects and 1,035 runs. In the later 6 projects, 100 of 111 first reviews asked for fixes.
- They record finding defects through acceptance checks, review and screen checks even in work that ended normally.
Who, and in what situation
In eight projects from August to October 2026, development, review and screen checks were divided among AIs.
What they needed
Managing AI usage quotas and context capacity while finding defects that slip past a normal exit or a completion report.
What they tried
Work is split across branches and important changes are reviewed by a different model. The original request is compared with the deliverable, and checking is redone.
What this source lets you read
As you add more division of labor, one design to consider is separating the work report from the acceptance decision.
What to check next
Who checks the conditions the implementing AI overlooked, and with what evidence?
Limits of this source
- This is a report by the operator of a tool they made themselves, not an independent user evaluation.
- Projects and assigned models differ in conditions, and there is no comparison control.
- The exact first publication date is unconfirmed. The record also notes the problem of the supervising AI skipping verification steps.
Read the primary source
Links use the original title or a HAKOMIRO source description. Japanese originals retain their published wording.
Orka — coding agents in parallel git worktrees (opens in new tab) ↗
ugorur/Orka / First publication date unconfirmed
An explanation of a self-made tool. It does not run the setup steps or independently verify the product's effect.
Evidence: what the numbers in the README come from (opens in new tab) ↗
ugorur/Orka / First publication date unconfirmed
Figures recorded by the operator. This is not an independent audit of the full raw logs and not a comparative trial.