composerID is exclusive to Triage
composerID · the publish pipeline

Downstream.

Triage settles the decision; composerID writes it into the system that executes it — a requisition, a contract, a signature envelope. Publishing is idempotent: a retry updates the same record rather than creating a duplicate, and every record carries the Intent ID.

How a decision gets published.

Each step writes the same Intent ID into the system that will execute the work.

01

Intent Record

The decision saved as a self-contained record under one Intent ID that never changes.

02

Channel Map

Your routing rules set the destination, the field mappings and the mandatory fields.

03

Publish

The adapter publishes idempotently — a retry updates the same record instead of adding a second one.

04

Records linked

The Intent ID goes into the new record; the destination’s own number comes back.

05

Audit trail

Every later event is logged against the same Intent ID.

Follow one decision into SAP Fieldglass.

Step through one contingent hire published into SAP Fieldglass. The walkthrough is a simulation: all identifiers, tenants, timestamps and amounts are illustrative.

composerID — Intent Record
intent_3kF9xQm2 Draft
work_typerole
channelcontingent
confidence0.92
titleData Engineer
locationLondon, GB · hybrid
start_date2026-04-01
duration6 months
cost_center_idCC-4401
risk_posturemedium
defence_filedf_8nWqL2v1.json
intent_3kF9xQm2 Planned
The Channel Map gives this intent one destination and one set of field mappings:
target_systemSAP Fieldglass (EU)
object_typeJob Posting / Requisition
mapping_profilefg_eu_contingent_v3
required_fieldstitle, start_date, cost_center_id, location, duration ✓
preconditionsBudget approval ✓ · HR classification ✓
idempotency_keyintent_3kF9xQm2-v1-fieldglass_eu
update_policyrates, dates mutable · title immutable
intent_3kF9xQm2 Publishing
FG
SAP Fieldglass adapter
14:32:01 Authenticating via OAuth 2.0 (client credentials)…
14:32:01 ✓ Token acquired. Tenant: fg-eu-prod
14:32:02 Mapping standard fields → Fieldglass field names…
14:32:02   start_date → WorkStartDate
14:32:02   cost_center_id → CostObjectID
14:32:02   title → JobPostingTitle
14:32:02 ✓ Payload validated. 12 fields mapped.
14:32:03 POST /api/v1/job_postings
14:32:03   Idempotency-Key: intent_3kF9xQm2-v1-fieldglass_eu
14:32:04 ✓ 201 Created → REQ-40281
14:32:04 Compliance File URL written to CustomField_12
14:32:04 ✓ Publish log entry recorded.
intent_3kF9xQm2 Published
Both records now hold the other’s number. Start from either system and you find the match.
composerID
intent_3kF9xQm2
external_id: REQ-40281
target: SAP Fieldglass (EU)
defence_file: df_8nWqL2v1
⟷
SAP Fieldglass
REQ-40281
CustomField_11: intent_3kF9xQm2
CustomField_12: Compliance File URL
Status: Open
intent_3kF9xQm2 ✓ Synced
14:30:12
Intent created
Decision received from Triage; Compliance File attached.
14:31:05
Plan generated
Channel Map → Fieldglass EU, requisition.
14:32:04
Published
REQ-40281 created. Idempotency key logged.
14:32:05
Linked
Intent ID → REQ-40281 linked. Compliance File URL stored.
15:12:33
Approved
Webhook from Fieldglass. Hiring manager approved.
15:12:34
Timeline updated
Fieldglass events now appear on the composerID timeline.

Trace any object back to its decision.

The same Intent ID sits on the decision, the evidence, each record created and each approval logged afterwards.

composerID — Intent Lineage
intent_3kF9xQm2 Origin
Decision
Decision made
Contingent, Data Engineer, London, 6 months
Evidence
Compliance File
df_8nWqL2v1.json
intent_3kF9xQm2
Execution
Destination objects
Requisitions, work orders, assignments
Audit
Events & approvals
Every status change logged
Financials
Costs & invoicing
Linked to original decision
Search the Intent ID in any connected system and you reach the decision that created the object, and the evidence behind it.
intent_3kF9xQm2 Execution
Three objects across two systems — all carrying the same Intent ID.
FG
SAP Fieldglass · Requisition
Data Engineer — London
REQ-40281
FG
SAP Fieldglass · Work Order
J. Martinez — Data Engineer
WO-90114
ERP
SAP S/4HANA · Purchase Order
Staffing Services — CC-4401
PO-772891
Trace it from either end. Search intent_3kF9xQm2 in any connected system and see the full chain: decision → requisition → work order → purchase order.
intent_3kF9xQm2 Events
The audit trail: who did what, when, and in what role.
14:30:12
Intent created
Triage completed the classification; composerID attached the Compliance File.
⚙ composerID · automated
14:45:33
Budget approved
Cost centre CC-4401 confirmed as within the Q3 budget.
👤 Sarah Chen · Finance BP
15:12:07
Hiring manager approved
REQ-40281 approved in SAP Fieldglass; Fieldglass notified composerID.
👤 Tom Richards · Engineering Dir
3 Apr
Worker assigned
J. Martinez accepted. Work order WO-90114 created.
⚙ Fieldglass · webhook
3 Apr
Rate changed in Fieldglass
A recruiter raised the bill rate from £650 to £680/day; composerID’s check against the record flagged it.
⚠ composerID · reconciliation
4 Apr
Change approved
Procurement accepted the new rate; the Intent Record moved to v2.
👤 Lisa Park · Procurement Lead
intent_3kF9xQm2 Cross-reference
The same decision is on record in three systems, each holding the others’ numbers.
composerID
intent_3kF9xQm2
Master record · v2
⟷
SAP Fieldglass
REQ-40281 / WO-90114
CustomField_11: intent_3kF9xQm2
composerID
intent_3kF9xQm2
Master record · v2
⟷
SAP S/4HANA
PO-772891
Reference field: intent_3kF9xQm2
Reference numbers by system
Intent IDintent_3kF9xQm2
Fieldglass REQREQ-40281
Fieldglass WOWO-90114
S/4HANA POPO-772891
Compliance Filedf_8nWqL2v1
intent_3kF9xQm2 Financials
Every invoice on this engagement links back to the decision that authorised it.
Total spend to date
£78,880
16 weeks · £680/day · 4.6 days avg/wk
Budget remaining
£9,520
Original estimate: £88,400
Invoices raised
4
3 paid · 1 pending approval
Rate variance
+4.6%
£650 planned → £680 actual
Period
Amount
Source
Apr 1–30
£14,960
INV-8812
May 1–31
£15,640
INV-9103
Jun 1–30
£14,280
INV-9441
Jul 1–present
£34,000
Pending
Total
£78,880
Every pound here is booked against intent_3kF9xQm2. The original decision, the evidence, the rate change, and every invoice — one thread.
Search the Intent ID in any connected system and you reach the decision that created the object, and the evidence behind it.

The same intent, routed to different systems.

Most enterprises run different processes by region, business unit, category and channel. The Channel Map holds those routing rules as configuration, not code.

Channel Map — EU program
intent_3kF9xQm2 Config A
Channel Map resolves this intent to a single-step publish to the EU Fieldglass tenant.
work_typerole
channelcontingent
regionEU — United Kingdom
mapping_profilefg_eu_contingent_v3
target_systemSAP Fieldglass (EU)
object_typeJob Posting / Requisition
publish_steps1
Intent Record
intent_3kF9xQm2
→
Channel Map
fg_eu_contingent_v3
→
Destination
SAP Fieldglass (EU)
intent_3kF9xQm2 Config B
Same intent format. Different mapping profile sends it to the US VMS instead.
work_typerole
channelcontingent
regionUS — New York
mapping_profilebl_us_contingent_v2
target_systemBeeline (US)
object_typeWork Request
publish_steps1
Intent Record
intent_3kF9xQm2
→
Channel Map
bl_us_contingent_v2
→
Destination
Beeline (US)
The Intent Record is identical. Only the mapping profile changed — fg_eu_contingent_v3 → bl_us_contingent_v2. Each field is renamed to what Beeline expects.
intent_3kF9xQm2 Config C
Services intent triggers a multi-step chain — and the Channel Map holds that order.
work_typeservice
channelstatement_of_work
mapping_profilesow_multi_v1
publish_steps4
sequencingserial — each step must succeed before the next runs
Intent Record
intent_3kF9xQm2
→
1
Sourcing
Globality
→
2
CLM
Icertis
→
3
S2P
Coupa
→
4
VMS tracking
Fieldglass
A single intent goes to four destinations in order — sourcing, then contract, then purchase order, then VMS tracking. Each step must succeed before the next runs, and the intent_3kF9xQm2 reference runs through all four.

Every object arrives with its evidence attached.

The Compliance File is an evidence bundle that travels with the decision. When an auditor asks "why did we engage this supplier through this channel?" — the answer is attached to the object.

01 — Decide

Compliance File created

composerID assembles the evidence behind the decision as it is made; the contents are listed below.

02 — Publish

Linked and published

Compliance File URL written into the destination object's custom field or notes on publish. Where supported, the PDF is attached directly to the VMS object.

Always

The master copy stays with you

composerID keeps the master Compliance File itself, so the evidence survives a change of VMS vendor or tenant configuration.

What the Compliance File contains

Request summary and justifications
Classification rationale & confidence
Constraints & assumptions
Recommended channel + alternates
Required approvals & compliance
Links to supporting documents

Where decisions land.

composerID publishes into vendor management, source-to-pay, contract, ERP, HR and recruitment systems.

VMS

Vendor Management Systems

Requisitions, work orders, timesheets — SAP Fieldglass, Beeline, VNDLY, Workday VNDLY. The Intent ID rides every object. VMS coverage →

S2P

Source-to-Pay

Sourcing events, contracts, purchase orders — Coupa, SAP Ariba, GEP, JAGGAER, Ivalua. S2P coverage →

CLM

Contract Lifecycle Management

Agreements, envelopes, e-signatures — Icertis, Ironclad, DocuSign, Conga, Juro, Agiloft, LinkSquares and more; ContractPodAi and Malbek on the roadmap. CLM coverage →

ERP

Enterprise Resource Planning

Purchase requisitions, cost objects, vendor masters — SAP S/4HANA, Oracle, Dynamics 365, NetSuite. ERP coverage →

HRIS

HR Information Systems

Position records, headcount, onboarding triggers — Workday, SAP SuccessFactors and ADP; UKG, BambooHR and Dayforce on the roadmap. HRIS coverage →

ATS

Applicant Tracking Systems

Job openings, candidate pipelines, offer letters — Greenhouse and Lever; iCIMS, SmartRecruiters and Bullhorn on the roadmap. ATS coverage →

See how composerID publishes into your systems.

Read the docs → Explore platforms