# AURIC authenticated results data

This folder contains published AURIC MAX SUITE result payloads for independent verification.

## Files

| File | Description |
|------|-------------|
| `auric-latest-results.json` | Multi-run history with compression, speed, reproducibility hash, and environment signature per run |
| `auric-max-suite-results.json` | Full authenticated MAX SUITE report (phases, assertions, seals) |
| `site-contact.json` | Site contact configuration |

Download from [Test Results](../test-results.html) or fetch directly from `/assets/data/`.

## How to authenticate the AURIC reproducibility hash

1. Verify the reproducibility hash matches the published value.
   - Read the `reproducibility_hash` field from the JSON (format: AURIC-RH-XXXXXXXX).
   - Compare it byte-for-byte with the published hash for that run.
   - Any mismatch indicates modified data, a different environment, or a non-AURIC runtime.
2. Recompute the hash from the normalized payload.
   - Take the `normalized_payload` field from the JSON.
   - Run it through a standard SHA-256 hashing function.
   - Convert the result to uppercase hex.
   - Confirm it matches the `reproducibility_hash` value.
   - If it does not match, the payload was altered or not produced by AURIC.
3. Validate the environment signature.
   - Read the `environment_signature` field (e.g., DELL-ENV-4421-BIOS-OK).
   - Confirm it matches the published environment signature for that run.
   - If the signature differs, the run is not considered an authenticated AURIC execution.