Example: What NexArt Produces

1. The execution

A fintech company uses an AI agent to review refund requests. The agent reads the ticket, checks order history, and recommends a resolution.

This is a real business decision. Six months later, if someone asks why the refund was approved, what evidence exists?

2. What gets sealed

NexArt captures the input, output, model identifier, timestamp, and execution conditions into a single record. A unique fingerprint is computed from these fields.

If any value changes, the fingerprint changes. This sealed record is called a Certified Execution Record (CER).

3. The certificate hash

The fingerprint of this record:

This hash is deterministic. The same inputs, output, model, and timestamp will always produce the same hash. It cannot be reverse-engineered to recover the original data.

4. What verification checks

When someone verifies this record, three things are checked:

1. Hash match. The fingerprint is recomputed from the record fields. If it matches the stored hash, the record has not been altered.
2. Node receipt. If the record was submitted to an attestation node, the node's independent signature is checked. This confirms a third party saw and signed the record.
3. Timestamp consistency. The recorded time is compared against the node receipt time to confirm they are consistent.

5. What "verified" means

A verified record confirms one thing: the record has not been changed since it was created. The input, output, model, and timestamp are exactly what they were at execution time.

Verification proves execution integrity, not correctness. It does not confirm the refund recommendation was right. It confirms that this specific input produced this specific output, at this specific time, using this specific model.

This record can be verified independently using its certificate hash. Anyone with the hash can confirm the record is intact, without contacting NexArt or the system that created it.