composerID currently ships as part of Triage. Triage is the decision-intelligence product; composerID is the publishing layer that takes the resulting decision reference into configured downstream systems. This article explains how the two fit together, and why the boundary between them is drawn where it is.
Today
composerID only works with Triage. It is not a separate purchase, it has no price list of its own, and you will not find it sold on its own. If you buy Triage, the publishing layer comes with it, as a module of the product within Triage’s own tiers.
Why
The pairing gives Triage a clean boundary between making a decision and publishing it. Triage can concentrate entirely on the quality of the decision: the questions, the classification, the recommendation. composerID can concentrate entirely on carrying the decision reference into other systems correctly. Neither job leaks into the other, and each can improve without breaking the other.
It also keeps accountability simple. One product, one contract, one team responsible for both the decision and its publication.
In future
The publishing layer has the potential to accept decisions from other platforms. The architecture does not depend on Triage being the only source of decisions. But that is a direction, not a current product claim, and we would rather say so plainly than imply a marketplace that does not exist yet.
What we deliberately do not promise here
A blog post is a poor place for pricing policy. Commercial terms, connector costs and packaging belong in proposals, where they can be specific to a customer and a point in time, and where they can change as the product matures. What this page can promise is the shape of the product: Triage decides, composerID publishes the decision reference, and your systems carry on executing.
Written with Claude. This post was drafted with Claude, Anthropic’s AI model, working from the composerID repository: the registry, the schemas, the reference sandbox and the vendor documentation it cites. Edited and published by the composerID team.