Beyond Delegate
Beyond Delegate turns a request written in your own words into approved, planned and delivered work done by external AI agents, with a person deciding at every gate.
- Availability: Experimental
- Evidence: Read from source
- Explanation
What you can do here
Choose the task you came for.
| You want to | Go to |
|---|---|
| Reach the application, sign in and find your way around | Get started with Delegate |
| Invite people, understand seats and roles, give someone access to a project | Workspace and collaboration |
| Write a request, import one, answer the questions of the analysis | Requests |
| Approve or return a proposed requirement, plan and prioritize releases | Review and planning |
| Launch development with an external agent, answer its blockers, accept or return its results | External work |
| Create a version, request a test deployment, read its status and evidence | Versions and delivery status |
| Know what Delegate tells you, and what it never sends | Notifications and communication |
| Recover from an ended session, a refusal, a conflict or an uncertain outcome | Delegate recovery |
| Check a limit before you rely on something | Supported limits |
How work moves
Delegate keeps one rule throughout: an agent proposes and does work, and a person decides. Nothing moves to the next stage without a recorded human decision, and no external action is repeated automatically when its outcome is unknown.
| Stage | What happens | Who acts |
|---|---|---|
| Request | Someone writes what they need, in their own words. The words are kept exactly as written | A person with permission to register requests |
| Analysis ("intake") | An external intake agent reads the repository, may ask questions, and proposes a requirement | The agent; a person answers its questions |
| Human evaluation | The proposed requirement is approved, returned with a reason, or the request is dismissed | A person with permission to take decisions |
| Planned release | Approved requirements are selected into a release, ordered, and the scope is approved | A person |
| Development | A person launches development; an external agent works, may get blocked and ask, and reports a result | The agent; a person answers blockers and accepts or returns results |
| Version and test | A version binds the finished release to an exact commit; a person requests a test deployment, then accepts or rejects what was deployed | A person; a delivery worker carries out the request |
| Production | A person approves the tested version. That approval is a record. Nothing is published to production, because no production executor exists | A person |
The words request, approval, dispatch and verified completion mean four different things, and the interface never uses one for another. The work status vocabulary defines them once for every page.
Three contexts that stay apart
- You: your name, language, appearance and sign-in methods, under Personal settings.
- The workspace: its name, its plan, its people and what each of them may do in each project, under Workspace settings.
- The project: one repository and its sections: Overview, Requests, Batches, Requirements, Planned releases, Versions, Manual import and Infrastructure.
A Delegate workspace is not a Beyond Accounts organization, and belonging to one gives you nothing in the other. See Account, organization and product workspace.
What Delegate does not do
Next action
New here? Get started. Setting up a team? Workspace and collaboration.
Related: Beyond Accounts · Identity and resource permissions · Beyond Delegate on the Beyond site · Troubleshooting index