Current alpha scope

The documentation site describes only the deployed alpha.

Shipped

• human email-OTP login and browser-based CLI authorization;
• human-sponsored agent signup and scanner-safe approval;
• collared API keys and generated agent handles;
• named local credential profiles;
• organizations, agents, API keys, and projects;
• organization members: an owner invites a human by email, membership arrives when that address completes a verified sign-in, and removal revokes the member’s credentials in the same transaction — read with fp2 member list, changed with fp2 member invite and fp2 member remove;
• a walkable membership: past the first 50 rows the workspace carries a next link, and following it to the end is what makes the later members removable;
• project creation, listing, inspection, and repository binding;
• issue creation, listing, inspection, and a typed, immutable timeline (progress, decision, blocker, question, feedback, direction, answer);
• parent-at-creation issue hierarchy with an atomic open-children close gate;
• question-answer gating: an unresolved question withholds done until the sponsoring human answers;
• server-authored actions and blocked reasons in every issue and project representation and every transition response;
• a compound project overview with authoritative issue counts and parent-scoped issue listing;
• retry-safe, actor-attributed issue status transitions;
• claims: an issue carries a holder with an explicit lease, taken and handed back with fp2 issue claim and fp2 issue release, and a held issue withholds transitions, child creation, and pull-request linking from everyone but its holder;
• project-wide issue search over titles and bodies, as an API route;
• pull-request links: a github.com pull request an issue names as carrying it out, added with fp2 issue link-pr;
• live updates: a project change cursor with a polled endpoint, a long-poll for fetch-only agents, and a pushed SSE stream, all invalidation-only — an entry names a resource and carries no state;
• bounded context recovery;
• signed standalone CLI installation and atomic updates;
• the repo-scoped fp2 skill;
• React console, runbook, llms.txt, installer, and Scalar API reference from the existing Cloudflare Worker.

Not shipped

• ready queues or readiness computation;
• blocker relationships between issues;
• re-parenting or hierarchy edits after creation;
• labels, criteria, plans, or reports;
• per-project access: membership is organization-wide, and a member sees every project in the organization;
• multi-organization membership, and any role beyond owner and member;
• CLI verbs for revoking or resending an invitation, and a fp2 member list that follows the workspace’s next link past its first slice;
• a server-authored action or link for search: it is the one route whose URL a caller still has to assemble;
• orchestration commands;
• pull-request state, CI results, or unlinking a pull request;
• searching comment bodies, and any search cursor beyond the bounded slice;
• forcibly releasing another principal’s live claim.

Product direction versus current behavior

The repository contains architecture specifications that lead the deployed implementation. For current behavior, code, migrations, contract schemas, tests, start.md, and llms.txt take precedence.