Rows of monitoring displays showing live system data

Scope before claim

Inspect the demonstrations.

Each entry tells you whether it is an interactive artifact, a sanitized receipt shape, or a synthetic implementation pattern. None silently upgrades demonstration into certification.

Now check your own stack What a receipt looks like

Public demonstration

Interactive artifact

The Quantize Receipt

An external interactive artifact presents two timing treatments of one performance. Follow the link and inspect the artifact and its own receipt rather than treating this index as proof.

What to check

Play the take and flip the toggle — the notes never change, only the time does
The derivation rule is declared: grid, tempo, anchor, and measured onset shifts
Treat the artifact's own declared receipt as the authority for its provenance and delivery scope

Run the audit at play.npssounds.com

Live on this site

Receipt shape

The Receipt That Runs

A sanitized demonstration of the receipt object itself: claim, source class, observation and decision times, wire verification, renderer bounds. The grammar is public. The tuning stays private.

What to check

Read the receipt JSON and trace the claim to its verification path
Note what is absent: no raw sources, no thresholds, no private paths

Read the receipt demonstration

Synthetic pattern

Implementation guidance

Governed publishing pattern

A generalized implementation pattern showing publish-tier gates, link integrity, and agent coordination through declared boundaries. It makes no private production claim.

What to check

Read how publish tiers decide what qualifies for the wire
See the snapshot boundary between write agents and read agents

Read the synthetic implementation pattern

Your turn

Use the public tools to inspect your own surface.

The self-assessment is educational and the URL checker is diagnostic. Neither certifies an implementation; both make missing evidence explicit.

Run the compliance check