- Total
- source value
- Endpoint
- declared identifier
Validation and receipts
Validate for the real destination.
Pin the target contract, run official or equivalent validators, reject known-bad controls, and retain the exact proof beside the artifact.
profile pinnedHow this surface works
A file that opens is not necessarily a file the receiver accepts.
Versioned operation
Inputs, outputs, options, losses, and errors stay behind one inspectable contract.
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
Pin the target
Select the destination, rule set, and exact profile version.
profile@version - 02
Preflight and correct
Surface the failing field, declared loss, or human exception before delivery.
fail closed - 03
Issue acceptance evidence
Bind accepted bytes to validators, known-bad controls, and run identity.
receipt
Availability
Claims follow the registry.
Acceptance profiles are under development. Current validator evidence is disclosed operation by operation.
Inspect current capability evidence