Triage decides, composerID publishes. This page explains what each layer does: deciding, publishing and executing. For the question design system, see Questions; for the publish pipeline, see Downstream; for the business case, start on the home page.
01
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.
02
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.
03
Execution layer
Your systems handle the transactions: requisitions, work orders, timesheets, invoices, compliance checks, approvals and supplier contact.
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.
Each part has its own page, with a working demo.
Questions
29 question types Triage can score and composerID can map onto fields in the destination system. Explore all 29 →
Upstream
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
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 →