Agent Kanban

The evidence shows authenticated access, tenant/owner isolation, Agent-to-runtime binding, rejection of cross-owner relationships, and separation between assignee and reviewer. Human review gates, idempotency guidance, migration preflight checks, and read-only public views further constrain external operations. The Worker–D1–Realmroot–Enbor–GitHub boundaries are described clearly enough for full data-flow-transparency credit. Deductions apply because the supplied material does not enumerate minimum scopes for every operation; Board deletion is not shown to require confirmation, soft deletion, or recovery; sensitive-data guidance covers secret storage, key format, and authentication but not rotation, log redaction, or incident handling; and dependency controls show frozen installation, CI, and some pins but no lockfile excerpt, vulnerability scanning, SBOM, or remediation policy. Authorship, copyright, and ecosystem attribution are stated, but the publisher is unverified and some provenance claims lack matching implementation evidence in the supplied files.

The README, package scripts, CI matrix, tests, version requirements, architecture terms, and lifecycle are strongly consistent. The upgrade tests also demonstrate specific blocking diagnostics, supporting full self-consistency credit. Frozen dependency installation and exact environment requirements help availability, but full operation relies on Realmroot, Enbor, GitHub, and Cloudflare, with no demonstrated outage degradation, retry ceiling, or recovery policy. The evidence includes 401, not-found, and migration-blocking behavior with all offending task IDs, but does not establish a comprehensive error-message convention across ordinary APIs, streams, external adapters, and deployment failures.

The source clearly separates worker, maintainer, single-task, and multi-task Agent roles and covers creation, claiming, execution, observation, review, dependency, and public-view scenarios. Responsibility boundaries among Agent Kanban, Enbor, and Realmroot are explicit, while lifecycle rules and automatic-versus-explicit skill invocation make triggers precise. Environment-fit credit is reduced because deployment is tightly coupled to Cloudflare Workers, D1, Wrangler, Realmroot, and Enbor; local requirements are documented, but no alternative database, offline mode, or other-cloud adaptation path is shown.

The README has a coherent documentation index, directory responsibilities, architecture, lifecycle, development commands, deployment steps, and contribution entry points. Installation prerequisites, tool versions, key formats, and migration order are concrete. Product/resource naming is stable across the supplied files, and the full license agrees with package metadata and the badge, justifying full marks there. Deductions apply because there is no dedicated FAQ or substantial troubleshooting section; limitations are scattered across service requirements, Cloudflare coupling, and the v1-to-v2 migration gate rather than catalogued comprehensively; tag releases generate changelogs but no actual changelog, compatibility policy, or version history is supplied; and authorship and contribution paths are visible without a complete maintainer roster, support channel, response commitment, or security-reporting owner.

Resource-oriented commands, JSON output, event streaming, an OpenAPI source of truth, dependencies, review gates, and execution bindings make the outputs highly usable by Agents. Modeling Agent identity, claims, runtime provenance, task communication, and independent review as first-class concepts demonstrates clear marginal value over a human-only board. Cost-benefit is reduced because operation requires Node 24, pnpm, Wrangler, D1, several external identity/execution services, and multiple secrets, while the material does not quantify deployment cost, operational burden, throughput constraints, or when a simpler workflow would be preferable.

The README connects behavior to spec/*.feature and describes [spec: capability/scenario] markers; the supplied SSE and migration tests actually use those markers, and CI runs distinct integration, migration, adapter, and core suites. Ownership isolation, authentication, and migration blocking also have concrete test examples, giving strong claim traceability and cross-source corroboration. Fact/inference separation is reduced because phrases such as “verified execution provenance,” “safe lifecycle transitions,” and “source of truth” are stated definitively without supplied implementation evidence for every property. Static source evidence also cannot independently establish badge status, live-service behavior, or that the test suite passed.