{ lossPolicy, signal, context }Integrations
Connect one operation model.
Map frameworks, queues, storage, and host-product review to the same registered operation rather than maintaining provider-specific document semantics.
managed jobPOST /v1/docx/diff
Authorization: Bearer $RUNSTAMP_API_KEY
Idempotency-Key: $YOUR_IDEMPOTENCY_KEY
{ "input": [base, candidate] }
→ { ok, value, losses, diagnostics, receipt }Invocation contract
Integrations should translate transport and identity—not redefine document behavior.
{ ok, value, losses, diagnostics, receipt }Runtime sequence
Discover, invoke, resolve.
The calling surface changes; the operation name and result semantics do not.
- 01
Receive host context
Resolve tenant, artifact, operation, and execution surface from the host product.
host - 02
Invoke the registry contract
Translate transport-specific data into the registered operation input.
adapter - 03
Project the result
Return explicit artifact, error, losses, diagnostics, and evidence to the host.
result
Availability
Claims follow the registry.
Integration availability follows the underlying operation and delivery surface; directory presence is not a hosted-availability claim.
Inspect current capability evidence