How composerID works

Triage decides, composerID publishes. This page explains what each layer does: deciding, publishing and executing.

Architecture

Who does what: decide, publish, execute.

Map & decide

Decision intelligence

Triage diagnoses the request, classifies the work, identifies constraints and recommends the fulfilment path, based on your own supply chains and systems. Upstream connectors (beta) ask the same questions inside Microsoft Teams, where the request starts.

Compose & publish

Publishing layer

composerID turns the decision into a portable record, checks it against your programme rules and publishes it into each system that needs it.

Execute & transact

Execution layer

Your systems handle the transactions: requisitions, work orders, timesheets, invoices, compliance checks, approvals and supplier contact.

Channel Map

The Channel Map decides where each decision goes.

Each Intent Record carries the answers, the score and the reasons behind the decision. The Channel Map (your routing rules) sends it to the right destination by region, category and policy.

Channel Map: Intent Record

intent_id

intent_3kF9xQm2

work_type

Contingent labour

region

EU · United Kingdom

channel

SAP Fieldglass (EU tenant)

route_type

Single-step publish

status

✓ Routed

Explore

Explore each part in detail.

Each part has its own page, with a working demo.

Questions

The question design system

29 question types Triage can score and composerID can map onto fields in the destination system. Explore all 29 →

Upstream

Where requests start

The Triage interface, Microsoft Teams (beta), and Slack (roadmap): the surfaces where the diagnostic questions are asked and the decision is made. See the surfaces →

Downstream

The publish pipeline

What happens after Triage decides: the lifecycle demo, Intent ID tracking, Channel Map routing and the Compliance File of evidence. See it end to end →

Give every system the same decision.

Read the docs →Explore platforms