Skip to main content
Use these patterns when an integration needs linked proofs, version history, or tag-based lookup. Proof ID in API responses is qHash.

Typed reference: reference.type: "qhash"

The ownership-basic check accepts a reference object with type: "qhash" and id set to another proof’s ID. That creates a typed link from one proof to another.
Reference payloads for the same target commonly hash from qhash:{targetId} in the signed content. Confirm current behavior in the ownership-basic capability reference and live API responses. Do not invent proof IDs.

Version chain: supersedes:<qHash> tag

When you update a memory or instruction proof, NEUS can tag the new proof with supersedes:<previousQHash>. Newer proofs point back to older ones.
Use neus_proofs_get to walk the chain and read history.

Tag prefixes for discovery

Tag prefixes help you filter related proofs. Common prefixes include subject facets (topic:, domain:) and review state (quality:draft / quality:approved). Query tagged proofs with neus_proofs_get. To attach an agent profile to a project, see Connect agent context.

Large content

Inline proof content has a size limit (about 50,000 characters). For larger artifacts, store the canonical file elsewhere and attach a short proof that references it (reference URL or content hash), or split content across multiple proofs only when your integration explicitly supports that pattern.

Next

Proofs

How proofs work on NEUS.

Guard an agent action

Check permissions before a tool runs.

Proofs read

Query proofs by tag and scope.

ownership-basic

Check inputs for content and references.
Last modified on August 13, 2026