Versioned operation
Inputs, outputs, options, losses, and errors stay behind one inspectable contract.
Runstamp platform
The document operations layer.
Compose native-file operations, target validation, named review, and durable evidence behind one contract for SDKs, API, MCP, and embedded UI.
artifact / exact version- 01OperateNative input
- 02ValidateTarget profile
- 03ReviewNamed decision
- 04DeliverArtifact + receipt
How this surface works
The operation, artifact, decision, and receipt remain one system.
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
Receive a native artifact
Keep source identity and the requested operation explicit at the first boundary.
input - 02
Operate under one contract
Run the registered engine with typed options, budgets, cancellation, and loss policy.
result - 03
Validate and review
Hold the exact artifact when its target or policy requires a material decision.
gate - 04
Deliver with evidence
Return the released bytes with diagnostics, losses, and the bound receipt.
release
Availability
Claims follow the registry.
Each operation and delivery surface declares its own capability state in the public registry.
Inspect current capability evidence