Create a doc (members; viewers are read-only). Only for brief, notes and handoffs — the company brief is edited by company admins in the web app.

Create a project doc of kind brief, notes or handoffs (not company_brief — company admins edit that in the web app). Doc kinds: brief = why the project exists — its goals and the business and technical structure; notes = working notes — progress, status, rules and gotchas people and agents keep for the next person; handoffs = a hand-over of work to a team or to the whole project (open → acknowledged → closed); company_brief = the company's rules and how it uses BoardMark (read-only here). body is markdown; one doc is at most 1 MB (413 doc_too_large — split it into several docs). slug (brief, notes) defaults to one derived from the title; 409 doc_exists means that slug is taken — get_doc it and update it instead. Handoffs are numbered H-{n} by the server; to = team ids it is for (copy them from the to of an existing handoff — there is no tool to list teams) — omit it or pass [] to address the whole project; issues = related issue keys. Say in message what you wrote (shown in the doc history). Viewers are read-only (403). Optional colour (D137, use sparingly; markdown stays the main format): <mark>text</mark> highlights (yellow; or <mark data-color="green">), <span data-color="red">text</span> colours text; colours yellow, green, red, blue, purple (e.g. green = passed / expected, red = bug / actual, purple = question); any other HTML is shown as plain text; keep the open and close tag in the same paragraph.

You act with exactly the rights of the user who owns this token; a project you cannot see returns not_found.