VIORANT TRUST

# Give every AI artifact a verifiable identity.

Viorant Trust fingerprints, signs, and verifies AI artifacts composed in a [.vio system definition](/vio), so a workflow can check identity, integrity, version, provenance, and recorded approval before [Helix prepares a supported deployment](/helix).

[Download the Hub](/download)[Talk to sales](/contact#c-sales)

MCP · API · OFFLINE VERIFICATION · REGISTRY

Viorant Trust command signing, fingerprinting, registering, and verifying an AI asset

THE SIGNING CEREMONY From consent to enforceable deployment policy

## ONE CEREMONY. A COMPLETE CHAIN OF EVIDENCE.

01

### Capture intent

Record signer identity, affirmative consent, IP address, user agent, and timestamp in a secure signing ceremony.

02

### Canonicalize

Normalize the asset and compute a deterministic fingerprint with a configurable hash algorithm.

03

### Sign and timestamp

Apply primary and optional counter-signatures, then request an RFC 3161 trusted timestamp.

04

### Register evidence

Store the asset hash, fingerprints, timestamp token, certificate references, and ceremony evidence atomically.

05

### Verify before use

Evaluate every available proof layer and block deployment when the asset cannot be verified.

VERIFICATION ENGINE Four independent proof layers

## VERIFY THE ASSET. NOT THE CLAIM.

Verification starts with the proof embedded in the asset, then falls back to increasingly durable records. A missing transport layer does not erase the authoritative signing record.

- 01

### In-band signature

Decode the hidden signature and validate it cryptographically when the embedded proof survives transit.

- 02

### Visible manifest

Parse asset metadata, license terms, certificate identifiers, and compare the canonical content hash.

- 03

### Registry record

Look up the authoritative server record and validate its trusted timestamp and ceremony evidence.

- 04

### Ledger anchor

Confirm the optional Merkle proof against an immutable public blockchain anchor.

DURABLE PROVENANCE Evidence that survives transport and tooling

## THREE RECORDS. ONE VERIFIABLE HISTORY.

### Portable proof

A visible JSON manifest travels with the asset. A compact hidden signature can support offline verification after common copy operations.

### Authoritative fallback

A durable sidecar and relational database preserve the complete record when editors or platforms strip in-band formatting.

### Immutable anchor

Optional Merkle-tree anchoring places proof of the registered record on a public blockchain ledger without placing the asset itself on-chain.

CRYPTOGRAPHIC EVOLUTION

## CRYPTOGRAPHY CAN CHANGE. THE TRUST MODEL HOLDS.

The trust model is designed so cryptographic algorithms can evolve. Current algorithms, proof layers, and verification interfaces are documented per release.

CONFIGURABLE HASHING PRIMARY + COUNTER-SIGNATURE RFC 3161 TIMESTAMP MERKLE ANCHORING

EVIDENCE CAPTURED

- Signer identity and affirmative consent

- IP address, user agent, and timestamp

- Canonical asset hash and signature fingerprints

- Certificate identifiers and license terms

- RFC 3161 trusted-timestamp token

- Primary signature and optional counter-signature

Designed to support evidence requirements across US ESIGN, EU eIDAS, and Taiwan ESA/PDPA workflows. Applicability depends on implementation and jurisdiction.

MCP AND API Trust services inside the tools you already run

## CALL TRUST FROM THE WORKFLOW.

Connect developer tools, CI pipelines, registries, and deployment systems through MCP or API. Signing and verification stay machine-readable and can become a required gate before release.

[Documentation](https://docs.viorant.ai)[Talk to sales](/contact#c-sales)

TRUST REQUEST JSON

{

"asset": "production-agent.vio",

"channel": "mcp | api",

"policy": "algorithm-evolution",

"timestamp": "rfc3161",

"ledger_anchor": "optional",

"deployment_gate": "required"

}

FAQ Signing, verification, and integration

What can Viorant Trust sign? +

Viorant Trust is designed for any AI asset, including prompts, models, skill libraries, memory definitions, agents, policies, and .vio bundle descriptors.

What makes the fingerprint canonical? +

The asset is normalized into a stable representation before a configurable hash algorithm computes its fingerprint. The same valid content therefore produces the same verification input.

Is blockchain required? +

No. The relational registry record and durable sidecar provide authoritative verification. Public blockchain anchoring is an optional additional proof layer.

Can an asset be verified offline? +

Yes, when the embedded signature or durable sidecar is available. Server-record and optional ledger checks add independent online verification layers.

How do systems connect to Viorant Trust? +

Signing and verification workflows are accessible through MCP or API so developer tools, CI pipelines, and deployment gates can call them directly.

Can the cryptography evolve? +

The evidence model is designed to allow cryptographic algorithms to evolve. Current algorithms and interfaces must be verified in release documentation.

## KNOW WHAT CHANGED. PROVE WHAT SHIPPED.

Bring verifiable provenance into every AI asset lifecycle.

[Download the Hub](/download)[Talk to sales](/contact#c-sales)