Versioned operation
Inputs, outputs, options, losses, and errors stay behind one inspectable contract.
Core operations
One contract for difficult documents.
Generate, transform, extract, compare, redact, and package native business files without recalibrating a different engine for every job.
79 stable operationsDOCXdocx.diffstable
DOCXdocx.validatestable
PPTXpptx.renderstable
XLSXxlsx.parsestable
How this surface works
Libraries expose functions. Runstamp exposes a production boundary.
Target preflight
The destination profile and validators run before an artifact enters delivery.
Bound evidence
Artifact identity, rules, execution, and decisions resolve from one durable receipt.
Operational sequence
State advances only with evidence.
Every step has an observable input, result, and release consequence.
- 01
Describe the operation
Discover a typed capability and its exact availability before execution.
registry - 02
Execute against native bytes
The selected engine runs with bounded resources and explicit loss policy.
operation - 03
Return result and receipt
Your application receives the artifact, diagnostics, loss ledger, and proof.
result
Availability
Claims follow the registry.
Operation availability is disclosed per registry item. Hosted access remains capability-gated.
Inspect current capability evidence