> ## Documentation Index
> Fetch the complete documentation index at: https://www.composer.id/llms.txt
> Use this file to discover all available pages before exploring further.

# Conductor and Triage Desk

> Conductor is the intended operational service behind Triage Desk: review decisions, manage exceptions and track actions.

**Conductor helps the teams responsible for workforce and services turn Triage decisions into controlled action. Triage Desk is the workspace they use.**

The intended service brings completed requests into an operational queue, applies the programme's handling rules, records human decisions and tracks the handoff. Requests can pass straight through where policy allows; people intervene when a request needs review.

| Commercial need | Conductor's intended responsibility | Boundary |
| - | - | - |
| See what needs attention | Case ownership, queues and review state | The original assessment remains authoritative in Triage and Manuscript. |
| Handle exceptions | Assignment, escalation and reasoned changes | Preserve the original recommendation and the reason for any override. |
| Follow through | Delivery jobs, status and action history | composerID performs the agreed destination handoff. |
| Measure interventions | An authorised operational reporting projection | Manuscript supplies decision evidence; reports use the same Intent ID. |

Conductor is an operational service within the Triage offering. It is arranged separately from the S, M, L and XL connection sizes. Its name does not create a new decision identifier, and it does not replace the downstream system's recruiting, contracting or engagement processes.

## Current implementation

Reviewed on 29 September 2026 against the Triage Desk repository:

* The Desk interface provides controller journeys using exemplar data and browser storage.
* Conductor has an initial, read-only Manuscript source adapter and offline tests.
* A deployed Conductor API, durable operational case store and live source-to-case-to-report loop remain to be delivered.
* Domo demonstration imports are separate from that loop. Their existence does not prove automatic Conductor reporting.

There is no live Conductor endpoint reference to publish yet. Its API reference belongs here once the implemented service and contract are verified.

## Acceptance for the first connected service

The first operational release should demonstrate a source import, a case that survives restart, a reasoned controller action that preserves the original decision, denied cross-tenant access and a recoverable export to a separate test dataset. Each step retains the same Intent ID.

See [the product overview](/product-overview) for the commercial explanation and [Manuscript](/api-reference/manuscript/overview) for the existing source API.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.