Capability Library
A coding path that must prove the work
A build request can move beyond code-shaped prose into an account-bound workspace where files, checkpoints and verification remain attached to the task. Agent Workspace requires an active Nexus plan or higher.
The outcome this serves
Create or modify a bounded software project, preserve context across a longer run and receive evidence of what changed and what was tested.
Account requirement: Agent Workspace requires Nexus or higher. Signal and Echo can still use the core answer and other included AOS surfaces, but cannot start an Agent job. The membership center shows plan comparison and current purchasing state; new self-service checkout is paused until a same-release production payment receipt is verified.
Start with a verifiable request
Build a small [tool] in a bounded workspace and show the tests and delivery receipt.
- Completion evidence
- The interface must show the genuinely completed result; external, paid, delayed or downloadable delivery must also expose the relevant runtime evidence or receipt.
- Failure state
- A refusal, boundary or error must remain visible and may not be labelled complete; failed delivery may not be charged as success.
- Public capability basis
agent.workspaceskill.forge· Open the live capability and evidence registry
How the request moves
- Compile the build contract
EVO identifies the requested behavior, affected files, acceptance criteria, risk and permissions before editing.
- Work through checkpoints
Long tasks preserve state and compact context so the next step is controlled by the task, not by a drifting transcript.
- Run gates before handoff
A claimed implementation should include the relevant tests, build result, known limits and recovery path.
What you receive
- A workspace containing the changed project or private tool
- A concise change report with verification results
- A preview or AOS micro app when the task is suitable for the sandboxed app path
What EVO will not pretend
- Signal and Echo do not include Agent Workspace; no Agent job or file mutation begins on those plans.
- The web workspace is not an unrestricted personal computer.
- External credentials, production deployment and consequential actions require separate authority.
- A passing local test does not prove every production environment.
Common questions
- Can EVO build a small app from one request?
- For bounded tasks, it can frame requirements, create workspace files, run available checks and return a preview or handoff.
- Does it expose private tool source for download?
- Private generated AOS tools remain within the bounded account runtime; ordinary project files follow the applicable Workspace and export rules.