Read project work recommendations with inspectable reasons
A read-only API ranks eligible project work using visible blockers, milestones, explicit strategy links, due dates, and priority.
API clients can read a small, ordered set of eligible project issues at GET /api/orgs/{id}/projects/{projectId}/work-recommendations. Each recommendation includes an action kind, contributing reasons, and limitations. The response uses the caller's current project and strategy permissions.
Inspect the facts behind the order
Visible urgent downstream work and overdue active milestones come first. Explicit links to active initiatives, current KPI evidence, due dates, and issue priority follow. Creation time and issue ID make ties stable. Text similarity does not affect the order, and no AI score is exposed. Stale or unknown KPI evidence is marked as a limitation.
Read within a clear boundary
The API returns up to five issues per page and only aggregate counts for excluded work. Each request evaluates the complete bounded project source. A request that exceeds the evidence limits returns an error instead of a partial recommendation. Cursors expire after 15 minutes; they do not freeze project state or grant permission to change it.
This release adds a REST read. It does not assign, start, or execute issues, and the existing heartbeat recommendation remains unchanged. Dedicated CLI and MCP access will be handled in a later slice.