https://composer.id/blog/index.html Workforce systems, in plain English. en-gb https://composer.id/blog/decide-publish-execute.html https://composer.id/blog/decide-publish-execute.html Fri, 04 Sep 2026 09:00:00 GMT Three jobs in a workforce stack: Triage decides how work is done, composerID publishes the decision reference, your systems carry out the work. https://composer.id/blog/one-id-every-system.html https://composer.id/blog/one-id-every-system.html Fri, 04 Sep 2026 09:00:00 GMT One workforce request can appear in several systems, each with its own number. composerID gives the decision one reference they can all share. https://composer.id/blog/the-vms-is-the-wrong-word.html https://composer.id/blog/the-vms-is-the-wrong-word.html Fri, 04 Sep 2026 09:00:00 GMT The VMS is only one part of the workforce story. Different kinds of work land in different systems, and that is why the decision has to come first. https://composer.id/blog/what-crosses-the-boundary.html https://composer.id/blog/what-crosses-the-boundary.html Fri, 04 Sep 2026 09:00:00 GMT composerID does not copy the whole Triage decision into every system. Its current role is simpler: publish the reference that identifies the decision. https://composer.id/blog/integrations-in-plain-english.html https://composer.id/blog/integrations-in-plain-english.html Tue, 09 Sep 2026 09:00:00 GMT An integration is a way for two systems to exchange something they both understand. The hard part is that every system has different rules. https://composer.id/blog/who-pays.html https://composer.id/blog/who-pays.html Tue, 09 Sep 2026 09:00:00 GMT composerID ships as part of Triage today. Triage makes the decision; composerID publishes the decision reference into configured downstream systems. https://composer.id/blog/where-intent-is-born.html https://composer.id/blog/where-intent-is-born.html Fri, 04 Sep 2026 09:00:00 GMT Workforce requests start before anyone opens a workforce system. Triage asks its questions there, so the decision comes before the form. https://composer.id/blog/research-system-of-engagement.html https://composer.id/blog/research-system-of-engagement.html Wed, 09 Sep 2026 18:00:00 GMT Systems of record, engagement, intelligence and action: a deep-research report on where each term comes from and what it should mean. https://composer.id/blog/preflight-before-publish.html https://composer.id/blog/preflight-before-publish.html Fri, 04 Sep 2026 09:00:00 GMT Knowing a vendor's API is not the same as knowing a customer's system. Two companies on one platform can require completely different information. https://composer.id/blog/idempotent-by-design.html https://composer.id/blog/idempotent-by-design.html Fri, 04 Sep 2026 09:00:00 GMT Sometimes a computer sends the same request twice. A publishing service should notice, not act twice. Engineers call this idempotency. A design note. https://composer.id/blog/beeline-field-by-field.html https://composer.id/blog/beeline-field-by-field.html Fri, 04 Sep 2026 09:00:00 GMT We mapped Beeline's published API specifications to learn how a decision reference could be carried. Mapping a spec is not the same as a live integration. https://composer.id/blog/four-reconciliation-postures.html https://composer.id/blog/four-reconciliation-postures.html Fri, 04 Sep 2026 09:00:00 GMT Publishing into another system is one problem. Knowing what happened afterwards is another. Webhooks, polling and events as future options. https://composer.id/blog/why-our-docs-check-their-own-citations.html https://composer.id/blog/why-our-docs-check-their-own-citations.html Fri, 04 Sep 2026 09:00:00 GMT Vendor APIs change and documentation moves. How we keep integration research traceable back to primary vendor sources, and what re-checking found. https://composer.id/blog/a-conformance-pack-instead-of-a-spec.html https://composer.id/blog/a-conformance-pack-instead-of-a-spec.html Fri, 04 Sep 2026 09:00:00 GMT Documentation says what software should do. Tests say whether it does it. If we cannot write an acceptance test for a claim, we should hesitate. https://composer.id/blog/client-credentials-scopes-and-hour-long-tokens.html https://composer.id/blog/client-credentials-scopes-and-hour-long-tokens.html Fri, 04 Sep 2026 09:00:00 GMT A publishing API needs to know who is calling, what they may do and how long that lasts. Our proposed model, explained before the OAuth words.