[xqliu]

Adds tools/orbi.md (category orchestrators, classification agent-native, pricing open-source) and the submitter entry in tool-submitters.json generated with npm run sync:tool-submitters.

Orbi takes an Issue labeled ai-ready, runs a coding agent in a worktree created from a frozen base SHA, opens a PR, has a separate review session check and fix it, and merges only through a merge gate (reviewed head, latest base, concluded CI, mergeable). For the coding-orchestrator boundary, the evidence covers:

• Task assignment and isolation: README and the workflow docs (Issue → run_id → branch/worktree → PR)
• Validation evidence: test results and CI recorded on the Issue and PR (example: Issue #1367 / PR #1370)
• Separate review and landing gate: independent review verdict for the current head, plus the merge gate described in https://docs.orbi.build/workflow. The example loop shipped in release v0.5.47

All evidence is first-party (repo, docs, Issue, PR, release, LICENSE), accessed 2026-10-21. I left out reviewedBy/reviewedAt/publishedAt/contentModifiedAt.

Checks run locally on Node 24: npm test (139 pass, 0 fail, 1 skipped) and npm run validate:content -- --require-submitters (passed: 16 categories, 66 tools).

Disclosure: I am the maintainer of Orbi.

[foo-bender]

Outcome: changes-requested

Policy assessment

@xqliu The complete first-submission diff supports agent-native / orchestrators / open-source-framework. This is not just a CLI-agent launcher: the actual Python runner persists run/base/head identity across issue claim, isolated implementation, independent exact-head review, tests/coverage, same-run remediation and guarded merge/blocked states. Official workflow documentation and the concrete issue 1367 -> merged PR 1370 delivery substantiate that outcome. Local/remote-runner interfaces, operator/model prerequisites and the bounded verification level are supportable. No published or open-PR duplicate was found.

Please address both remaining items together:

• websiteUrl contains utm_source/utm_medium/utm_campaign tracking parameters. The README requires the canonical public site; use the site-declared canonical https://orbi.build/ instead of the tracked submission link.
• Narrow or split the licence evidence item as detailed below. The current README does document the SUL alternative alongside AGPL; the issue is that the exact LICENSE evidence URL does not substantiate the README-specific part of its claim. Do not replace the correct AGPL licence URL with a claim that the whole product is proprietary.

Required fields, taxonomy and direct schema/provenance inspection otherwise pass. The contradiction pass covered website, docs, runner source/README, package/release metadata, AGPL/SUL and separate managed-cloud surfaces. Core self-hosted open-source pricing is not a promise of free model usage or free managed-cloud service.

Evidence checked

• https://github.com/orbi-build/orbi — Exact URL HTTP 200: substantive Python runner implementation and README describe local/remote runners, Orbi/pi roles, persisted issue/PR lifecycle, review gates and resumable delivery.
• https://docs.orbi.build/workflow — Exact URL HTTP 200: workflow documents frozen base, run marker, independent exact-head review, test/coverage gates, same-run remediation, live-head/base checks and explicit terminal states.
• orbi setup fails on every retry: its own .orbi/ runtime dir makes the checkout 'not clean' orbi-build/orbi#1367 — Exact URL HTTP 200: the concrete public issue reports setup failure caused by Orbi runtime files and links its delivered fix.
• orbi setup fails on every retry: its own .orbi/ runtime dir makes the checkout 'not clean' orbi-build/orbi#1370 — Exact URL HTTP 200: PR 1370 links issue 1367 and is merged; its Checks surface and GitHub check-run readback show successful tests and macOS compatibility checks.
• https://github.com/orbi-build/orbi/releases/tag/v0.5.47 — Exact URL HTTP 200: v0.5.47 is a real published release with the stated resume and journal fixes. Newer current package/release versions do not negate this explicitly historical claim.
• https://github.com/orbi-build/orbi/blob/main/LICENSE — Exact LICENSE URL supplies AGPL-3.0 legal text but does not contain the claim's separate assertion that the README names a Sustainable Use License alternative. That statement is corroborated by the README, not by this exact submitted source; split or narrow the claim so this evidence item supports its own assertion.

Evidence requiring correction or removal

• https://github.com/orbi-build/orbi/blob/main/LICENSE — Exact LICENSE URL supplies AGPL-3.0 legal text but does not contain the claim's separate assertion that the README names a Sustainable Use License alternative. That statement is corroborated by the README, not by this exact submitted source; split or narrow the claim so this evidence item supports its own assertion.

Please correct or remove each evidence item above.

Checks run

Exact final head 5efbffd merged without committing with current main d5a6bbd in an isolated temporary clone:

• npm run validate:content: passed (17 categories, 67 tools, 1 redirect/retirement).
• npm test: 139 passed, 0 failed, 1 skipped (companion website migration checkout unavailable).
• git diff --check: passed. Node 26.7.0; Bash 5.3.20.
  GitHub enrichment was successful at readback; no completed GitHub content-validation check was returned at inspection. No workflow approval, PR approval, merge or deployment was performed. SEO was not evaluated and no reviewer commit was made.

[xqliu]

Thanks for the review, @foo-bender. Both items are addressed in 0dd5a55:

• websiteUrl is now the canonical https://orbi.build/ (tracking parameter removed).
• The LICENSE evidence claim is narrowed to what that file shows: the repository LICENSE contains the GNU AGPL-3.0 text. The SUL mention is gone from that item; licenseUrl is unchanged.

I also merged current main into the branch (d2aedfa). Locally on Node 24: validate:content --require-submitters passed (17 categories, 67 tools), npm test gave 139 pass, 0 fail, 1 skipped, and git diff --check is clean.

[foo-bender]

Outcome: meets-policy

Policy assessment

Incremental re-review: both previously requested changes are resolved. websiteUrl is the canonical https://orbi.build/; the LICENSE evidence now claims only the AGPL text actually present. Settled inclusion/category analysis remains valid: agent-native / orchestrators / software-application. This is a substantive runner with isolated execution, recorded test evidence, independent exact-head review and guarded merge states, not a CLI launcher. Current core/managed-cloud, licence and release surfaces introduce no unresolved material contradiction. Operator/model prerequisites and documented macOS limitations remain disclosed.

Product fit

• tools/orbi.md: pass-fit (owner-isolated stage preserved). Orbi's core operating model is a runtime and orchestrator for coding agents, providing worktree isolation, run coordination, review sessions, and merge gates. Agent execution is the primary workflow, not secondary API or MCP access to a human-first application.
• Intended user: Developers and engineering teams building automated coding workflows around GitHub Issues and coding agents.
• Core job: Orchestrate coding-agent runs from labeled GitHub Issues through isolated implementation, testing, pull-request creation, independent agent review, and gated merging.
• The fit-bound description and opening operating model are unchanged. No published or competing open-PR duplicate was found.

Evidence checked

• https://github.com/orbi-build/orbi — HTTP 200, claim validated. README and real runner substantiate the ai-ready Issue-to-worktree-to-tested-PR/review/merge lifecycle and periodic local runner.
• https://docs.orbi.build/workflow — HTTP 200, claim validated. Workflow documents frozen-base/run identity, independent exact-head review, coverage and fresh-base/CI/unchanged-head merge gates.
• orbi setup fails on every retry: its own .orbi/ runtime dir makes the checkout 'not clean' orbi-build/orbi#1367 — HTTP 200, claim validated. Concrete Issue1367 contains ai-ready/ai-merged labels and run/base/branch/test/review/merge records.
• orbi setup fails on every retry: its own .orbi/ runtime dir makes the checkout 'not clean' orbi-build/orbi#1370 — HTTP 200, claim validated. Merged PR1370 links Fixes #1367 and the run marker; head check-run readback confirms successful tests and macOS compatibility.
• https://github.com/orbi-build/orbi/releases/tag/v0.5.47 — HTTP 200, claim validated. Historical v0.5.47 release explicitly lists Issue1367 and PR1370; newer current releases do not negate this dated claim.
• https://github.com/orbi-build/orbi/blob/main/LICENSE — HTTP 200, claim validated. Exact LICENSE file supplies AGPLv3 legal text; the revised claim no longer attributes the separate README SUL statement to it.

All submitted evidence items were checked at their exact URLs without substituting redirected/canonical sources. The independent contradiction pass covered the official product site, docs, repository/README and implementation, release/package channels, and applicable pricing/licensing/linked first-party surfaces. Verification remains documentation-reviewed; no live agent integration, security benchmark or production execution was exercised.

Reviewer-owned SEO metadata

tools/orbi.md

• agentSummary: accepted. Final value: Orbi is for maintainers who want coding agents to work from GitHub Issues. A scheduler tick claims an Issue labeled ai-ready, creates a branch and worktree from a frozen base SHA, and runs a coding agent that plans, implements, and tests. The runner opens the PR; a separate review session checks the exact base and head SHAs, and a merge gate checks CI and mergeability before merging.
  The README and workflow establish the maintainer workflow, frozen-base isolation and exact-head review/merge gates; the 67-word summary adds lifecycle detail to the preserved short description.
• seoTitle: accepted. Final value: Orbi: GitHub Issue Orchestration for Coding Agents
  Names Orbi and its supported GitHub-Issue coding-agent orchestration capability without a quality claim.
• seoDescription: accepted. Final value: Explore how Orbi assigns labeled GitHub Issues to coding-agent runs in isolated worktrees, records test evidence, and merges only after an independent review and merge gate.
  Summarizes the validated worktree, recorded-test and independent-review/merge workflow as a factual reason to inspect the profile; its modest length over the target is not a hard policy failure.

Reviewer commit: 2e3ee60
2e3ee60
All three contributor suggestions were accepted as the complementary set. The existing description, body and all other non-editorial bytes were preserved exactly; the focused commit adds only reviewedBy and reviewedAt (2026-10-23). Both Git identities resolve to foo-bender, and the commit is the live PR head and a direct child of the submitted head.

Checks run

Final head 2e3ee60 merged without committing with current main 6fe956f in an isolated detached worktree:

• npm run validate:content: passed (17 categories, 67 tools, 1 redirect/retirement).
• npm test: 143 passed, 0 failed, 1 skipped (companion website migration checkout unavailable).
• git diff --check and staged-diff whitespace check: passed.
  Node 26.7.0; Bash 5.3.20. The initial test attempt exposed macOS Bash 3.2 lacking mapfile; the unchanged suite passed after selecting the installed Bash 5.3.20. No workflow/PR approval, merge or deployment was performed.

@bradvin This meets the directory policy and is ready for your inclusion decision.