A project's context as one markdown text: company and project briefs, working notes, open handoffs, what each status means, the template's fields and the default role rules (D86).

The fastest way to get a project's context: company brief, project brief, working notes and the open handoffs, then what each of the project's statuses means and the default role rules (spec D86), as ONE markdown text. The status table uses each column's own meaning when the team set one (D102) and shows its WIP limit. After it comes the project's template (scrum, kanban, pipeline, sales_billing, service_desk, budget_planning or roadmap_goals) with its custom fields — id, type, options, which issue types each applies to, required — and the flags the template computes (overdue, bill_due, sla_over, off_track …; spec D129/D130/D131): a project whose issues link to other projects also gets a "linked projects: …" line (names + keys) — those are the projects a linked[] target or a delivers release may live in. take the field ids from there for create_issue / update_issue fields and for search_issues fields / sort_field; on Sales & Billing, installments are subtasks of the deal. Useful before working on a project you do not know. docs lists what is included, in order. truncated: true means the text hit its 2 MB cap — read the missing docs with get_doc. It carries no versions: call get_doc before you change a doc.

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