Status of a build started by writ_website_to_api. Terminal states: succeeded, failed, cancelled. Resting state: needs_guidance — Writ's mechanical rungs are done and the build is the caller's to finish; it carries map (endpoints seen, specs, candidate functions), and writ_website_to_api mode=guided build_id= continues it. A rung the ladder replaced reports superseded=true with fallback_build_id; with wait=true this tool follows that pointer and answers with the rung now running (followed_from lists the ids it walked; the returned build_id is the current one from then on). escalations lists every earlier rung with the real reason it handed over (robots.txt refused the crawl, no pages fetched, nothing matched the goal, no structured list...), i.e. why a browser was needed. On success it returns the workflow_id, the surfaces mapped, and verified — false for a fast/browser map, whose functions are candidates until a real run proves them. Any function runs with writ_run_workflow (function_name); the generated API docs (OpenAPI 3, Markdown or a Postman collection, all pointing at the real Writ endpoint) are at GET /api/v1/workflows/{workflow_id}/api-docs.