What does Utah AI Policy Act require, by when, and what does Planisphere deliver for it?

Utah AI Policy Act is enacted (or near-enacted) law in a specific jurisdiction, with a specific obligation and a specific date. Planisphere maps the obligation to a deliverable — the bias audit, the transparency disclosure, the high-risk notice — and pins it to the section and effective date so the filing is defensible.

00 ·

Utah AI Policy Act — capability brief.

Register 09 · Compliance pins · brief v0.1

Prepare evidence for compliance review Verify a record

Planisphere's evidence record answers Utah AI Policy Act's evidentiary asks via the Astrolabe schema. The mapping is published, reproducible byte-for-byte on customer hardware, and re-verifiable by any third party with the same inputs.

01 ·

Scope.

What this brief covers and what it does not.

In scope. SB 149 / SB 226 disclosure-on-request for generative AI. Cite-anchor: Utah AI Policy Act.

Out of scope. Production data (no PHI, no PII, no student record, no privileged correspondence). Model weights. Customer's own analyses of the evidence record.

Boundary. Only sha-pinned, Merkle-rooted derived metadata crosses; model state never does. U.S. provisional patent No. 64/073,668 covers the property.

02 ·

Evidence.

What the evidence record proves against this anchor.

Every measurement against Utah AI Policy Act lands in a signed evidence record: each artifact carries its own SHA-256, the artifacts chain into a Merkle root, and the engine version is pinned alongside. Internal or external compliance recomputes the root and checks the record — without the model state ever crossing the boundary.

Prepare an evidence brief →See how a record is checked

03 ·

Limitations.

Stated up front; ask a vendor that won't.

Planisphere measures behaviour, not capability. The evidence record says this is what your fleet did against the probe set; it does not say this is what your fleet will do under adversarial pressure. Adversarial coverage is a scope expansion that adds a probe family; the engine and the record shape do not change.

Reproducibility requires the inputs to be preserved. The record pins the inputs by SHA; it does not host them.

04 ·

Reproducibility & compliance check.

How a third party recomputes the record bit-for-bit.

Open the evidence check. Drop ATTESTATION.json and the named artifacts. The browser recomputes each per-artifact SHA-256 and the chained Merkle root via Web Crypto. Files do not leave the tab.

For a synthetic 3-subject record, see how a record is checked: one click checks an intact record; one click checks a tampered record and names the failing file.

05 ·

Cite.

How to reference this brief.

Planisphere Corp., Utah AI Policy Act — capability brief, v0.1, https://www.planisphere.ooo/corpus/utah-ai-policy-act/brief. Methodology preprint: 10.5281/zenodo.20372606.

Open scoping for Utah AI Policy Act Reference