> ## 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.

# From decision to delivery

> How Triage, composerID, Manuscript and Conductor connect workforce decisions to delivery, oversight and reporting.

**Triage is a decision intelligence platform for workforce and services. composerID connects its decisions to the systems that carry out the work.**

[Triage](https://www.addtriage.com) helps people explain the work they need, answer the right questions and apply their organisation's policies. It identifies mismatches and supports a recommendation across five channels: permanent, outsourced, contingent, services via SoW and AI agents. Country screening, drafting and reporting can support that journey where configured.

The result is a recommendation and a record of how it was reached. One **Intent ID** links that decision to what happens next. The reference connects the records; the answers and evidence stay behind it.

## Four clear jobs

| Product | What it does | What the buyer gets |
| - | - | - |
| Triage | Understands the requirement and supports the decision. | A clear next step, with reasons and evidence. |
| composerID | Carries the Intent ID into a configured destination and, at the next level, checks it arrived. | A connection between the decision and the resulting requisition, request or contract. |
| Manuscript | Makes authorised decision detail available for reporting and analysis. | Questions, answers, outcomes and recorded timings, linked by the same Intent ID. |
| Conductor, behind Triage Desk | The intended operational service for reviewing decisions, managing exceptions and tracking actions. | Oversight of what needs attention and what happened next. |

The destination system keeps its own record number, approvals and delivery process. The Intent ID is the shared reference back to Triage. Use **Intent ID** for the reference and **composerID** for the integration platform; they do not introduce two business identifiers.

## Choose how far to connect

| Size | Plain-English promise | What happens |
| - | - | - |
| S: Standalone | Open and paste. | The requester follows a configured link and copies the Intent ID into an agreed field. |
| M: composerID | Open and pass. | The configured connection opens the appropriate destination workflow or existing template and passes the Intent ID. |
| L: composerID with confirmation | Pass and confirm. | The same handoff adds a check that the destination record exists and contains the Intent ID. |
| XL: Manuscript | Connect the decision detail to reporting. | Adds an authorised reporting feed of the underlying assessment, alongside the configured handoff and confirmation. |

[Compare the four sizes](/tiers). Conductor is arranged separately; it is not a fifth integration size.

## What "one field" means

The integration centres on one shared decision reference. It does not require the downstream system to receive the questionnaire or reproduce Triage's decision logic.

Some vendor operations also require a template identifier, an owner or native request fields before they can create a record. Those requirements must come from agreed client configuration or the destination's normal intake. A one-field reference does not mean every vendor accepts a one-property API request. The present sandbox also demonstrates richer request payloads; the narrow launch-and-reference journey must be tested for the selected platform.

## What a template promise means

Opening a published template, creating a request from it and creating a new template definition are three separate capabilities. A vendor may support one and restrict another. The [platform assessment](/platform-assessment) records them separately, alongside documentation and test-environment access.

<Note>
  The commercial model above defines the intended service. The Intent API currently runs against mock destinations in the hosted reference sandbox; a documented vendor field does not establish a live connection. Manuscript has its own API and programme access. Conductor's initial source adapter is implemented, but its operational API is not yet deployed. Each platform needs its own configuration and test evidence.
</Note>

<Columns cols={2}>
  <Card title="For commercial teams" icon="layers" href="/tiers">
    Explain S, M, L and XL through the customer's next step.
  </Card>

  <Card title="For implementation teams" icon="plug" href="/guides/connect">
    Choose the API, webhook, middleware or manual connection path.
  </Card>

  <Card title="Platform assessment" icon="clipboard-check" href="/platform-assessment">
    Check documentation, templates, sandboxes and access evidence.
  </Card>

  <Card title="Conductor and Triage Desk" icon="panels-top-left" href="/concepts/conductor">
    Understand operational oversight and its current build status.
  </Card>
</Columns>


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