Skip to main content
Every workforce decision produces two things, and composerID keeps them apart on purpose. This page defines the score and the manuscript, the path each takes, and the one identifier that joins them. Read it if you are reviewing what composerID sends where.
  • The score is what a destination system receives: a valid request carrying the Intent ID. It is enough for the destination to do its job and nothing more.
  • The manuscript is everything behind that request: the scored diagnostic, the answers, the ranked outcomes, the documents, the workflow and its signed PDF. It belongs to the programme and is served by the Manuscript API to the programme’s managed service provider (MSP) and its reporting suites.

​
Path 1: destinations get the score

When composerID publishes into Beeline, SAP Fieldglass, Coupa or any other destination, the record carries the Intent ID and the fields the destination needs to be valid. It never carries diagnostic content.
The boundary is structural rather than procedural. The payload an adapter publishes from contains only request fields, so there is no configuration path from an answer or a score to a destination field.
Every destination page in this documentation states what is sent, what is read back and what is never sent, built from the destination’s own create schema. Start from the destinations index.

​
Path 2: the MSP gets the manuscript

The programme’s MSP needs the evidence: which answers led to the decision, how the options scored, what was overridden and why. That evidence lives in Deployed’s production backend (WorkAuthor) and is served by the Manuscript API at https://deployed.workauthor.com/api/v1: assessments, documents, surveys and workflows, with signed webhooks for change. Access is granted per programme with per-customer API keys.

​
One identifier joins the two

The Intent ID is written into the manuscript’s externalId when the decision is made, and into the destination record when it is published. Ask either side with the one identifier and you reach the other half: the score in the system of record, the manuscript behind it, and one reference between them, with no lookup table.
The two paths are an invariant, not a preference. No diagnostic payload ever crosses into a destination system, and the Manuscript API is never exposed to a destination.

​
Next steps

The Compliance File

The evidence pack assembled from both paths under one Intent ID.

Manuscript API

Assessments, documents, surveys, workflows and signed webhooks.

Destinations

What each destination is sent, reads back and never receives.