Skip to main content

SAMPLE. VERIFIED AT BUILD TIME.

A signed audit record

One Intelligence Pack execution, recorded and signed. Every field group annotated in plain English.

Record format
huitzo.audit-record/v0.1-draft
Emitted
2026-07-06, 14:22:16 UTC
Signature
Ed25519, verified
Data
Illustrative sample

Sample notice

This record is illustrative. The Pack, run, reviewer, and data are fictional; no customer is referenced. The Ed25519 signature is real, generated with a throwaway documentation key created for this page, not a production key.

Intelligence Pack execution record

Document intake, one run

run_2026-07-06T14-22-07Z_a3f81c

Sample
Emitted
2026-07-06, 14:22:16 UTC
Record format
huitzo.audit-record/v0.1-draft
Status
Completed, signature verified

What ran

The Pack, what started it, and every step it executed in order. Each step is marked "Plain code" or "AI step", so you can see exactly where AI was involved and where it was not. Three of the four steps here are plain code.

Intelligence Pack
document-intake, version 1.4.2
Published by
huitzo-standard-library
Started by
A schedule, not a person: the intake scheduler service
Started
2026-07-06, 14:22:07 UTC
Finished
2026-07-06, 14:22:16 UTC (9 seconds)
Outcome
Completed, all four steps succeeded
  1. Fetched the new documents Plain code

    14 documents picked up from the intake queue

    412 ms
  2. Classified each document AI step

    14 documents labeled, each with a confidence score

    8.6 s
  3. Sent low-confidence items to human review Plain code

    3 documents below the 0.90 confidence bar, held for a person

    38 ms
  4. Wrote the results back Plain code

    14 results written to the customer's own database

    201 ms

What the AI step saw

The one AI step names the model, where that model runs (here: an endpoint inside the customer network), what scope of data it received, and the shape of what it returned. An auditor reads this without reverse-engineering a prompt log.

Model
llama-3.3-70b-instruct
Where it ran
Inside the customer's network, on a self-hosted endpoint
What it received
Document text only; no account or customer identifiers
What it returned
A category label and a confidence score per document

Who approved it

The policy in force (human review below 0.90 confidence), how many items were escalated, who reviewed them, what they decided, and when. "Who approved it" is a field in the record, not a Slack thread someone has to find later.

Policy in force
Human review required below 0.90 classification confidence
Items escalated
3 documents
Reviewed by
[email protected]
Decision
Approved
Decided at
2026-07-06, 15:03:41 UTC

What never left the network

The deployment is self-hosted and the record states the boundary outcome for this run: zero external network calls, no data left the network. This is the field group a data-protection officer turns to first.

Deployment
Self-hosted, production, inside the customer network
External network calls
0
Data left the network
No
Why
The model endpoint itself is self-hosted inside the customer network

The signature

A real Ed25519 signature over the record. Verify it with the public key; change any part of the record and verification fails. That makes the record tamper-evident. This site re-verifies the signature every time it builds.

Algorithm
Ed25519
Signing key
huitzo-docs-sample-2026-07
Public key
4Vw6k/1XJDkDz51A4e3Ik6QRr5ZYOXhw2xxEa7RFqYs=
Record fingerprint (SHA-256)
0f914bcce3e58b886b4350ce45e89c1253823ba9515aaf6d7c879ff5817bba03
Signature
9AcdzH5g7fis6ZvSwgUecNaWs8dtWi9SNOmTWgbXNDe6otqWE2RIQ2hZwv9o3VdE8F+9uBVxt788tavufvkeBQ==
Checked at build time
Verified. This page cannot publish if verification fails.

ED25519 SIGNED

Every value above is taken from the signed record itself, restated in plain English.

Download the raw signed record (JSON)

HUITZO.COM/TRUST/AUDIT-RECORD. SAMPLE. VERIFIED AT BUILD TIME.

SAMPLE. VERIFIED AT BUILD TIME.

Read the specification SPEC v0.1. DRAFT.

WHY THIS ARTIFACT EXISTS

Observers prove what crossed the wire. Huitzo proves what your application did.

Most AI assurance tools watch from outside. They can tell you what crossed the wire. Huitzo is the runtime your AI applications actually run on, so the evidence of what happened is produced by the execution itself.

Every Intelligence Pack execution emits a record like the one above. This page shows a complete sample so you can judge the artifact itself, and it pairs with the draft standard that grades records like this one.

Huitzo Assurance Levels v0.1 SPEC v0.1. DRAFT.

ABOUT THE SIGNATURE

Check it yourself

The signature covers the compact (no-whitespace) JSON serialization of the record inside the downloadable file, encoded as UTF-8. Verification needs three things, all present in that file: the record, the signature value, and the public key. Any standard Ed25519 implementation can check them; this site verifies the signature at build time, so the page cannot publish a record that no longer matches it.

The key pair (huitzo-docs-sample-2026-07) was generated for this documentation page and the private key was discarded. In a production deployment, records are verified against the deployment's own published verification key, held by the customer, not by Huitzo.

AI operating system for regulated companies

Simple by design. Built to scale. Runs where your data lives.

Product access
Huitzo Hub is available by invitation for teams evaluating the product.
Book a working session
Read the specification SPEC v0.1. DRAFT. Inspect a sample audit record SAMPLE. VERIFIED AT BUILD TIME.