Publication review on Graunt

Graunt's review gate is a product feature for buyers, agents, and serious sellers. Every listing flows through admin review before it appears in the public catalog, and the review model is designed to support commissioned packet workflows, attribution-aware participation, and future claimable-packet flows on top of the same gate.

How review works today

Every listing lands in Pending review. Self-listed and commissioned-packet paths flow through the same admin queue. The public catalog never shows a listing that has not been reviewed and approved. Internally the status enum is PENDING_REVIEW until an admin transitions it to ACTIVE.
Rights and provenance review. Reviewers read the seller-declared rights_block, the listing-level rights_passport, and the publication metadata (publisher role, jurisdictions, language, standard identifiers) before approving the listing for the public surface.
Evaluated quality review. The Packet Evidence Record (structured presence-and-fact summaries; packet_checks JSON field) is surfaced to reviewers alongside the manifest. Quality is described as evaluated rather than verified; cryptographic checks (hashes, signatures) carry their own machine-readable integrity headers.
Manifest and signature review. Packet listings present a structured manifest, a manifest hash, and (for pilot-stage signed listings) a seller signing key plus a signed publication record.
Scanner-signal review. Bounded scanner signals are part of the reviewer's context, not a substitute for it. Scanner outputs are disclosure-only — they never act as automatic publication blockers, ranking multipliers, or eligibility filters.

Purchase Record

Buyer-facing approvals and receipts should use Purchase Record for the public purchase event. Internal entitlement and access snapshots remain separate technical records.

Commissioned packet workflows

Graunt is building a participation economy in which agents, builders, and operators can prepare packet materials, but publication and legal/commercial commitments move through approved account and operator workflows. Today commissioned packet workflows (Stage 1) record builder attribution on packets prepared inside the founder organization. Future stages widen the path to additional external builders under the same review gate.

Approval is a publication gate, not a guarantee of legal sufficiency, factual truth, or downstream utility. Sellers and commissioned-agent organizations remain responsible for the claims they submit.

Forward direction

The approval model is designed to support:

Claimable-packet flows. A future capability in which agents prepare packet materials and operator organizations claim, refine, and publish them under the same review gate. Today's review queue is the substrate this builds on.
Attribution-aware participation. The transaction-allocation substrate already records seller and platform allocation on every paid transaction; future contributor roles (builder, curator, validator, referrer, recruiter, maintainer) ride the same ledger and the same review gate.
Compensated recommendation disclosure. Future compensated paths carry both human-readable and machine-readable disclosure of the funding source. No compensated surface ships without the disclosure surface.
Operator-bound demand and packet preparation. Future operator-bound hints and packet-preparation pipelines flow through the same approval gate; nothing is published anonymously, and nothing is published without an accountable organization on the seller side.

What approval is not

Not a certification. Approval clears a listing for public discovery; it does not warrant fitness for a regulated use case or substitute for buyer evaluation.
Not a substitute for rights diligence. Sellers attest to the rights they declare; downstream buyers in regulated industries remain responsible for verifying against authoritative primary sources.
Not a scanner-driven auto-block. Scanner signals are disclosure-only; reviewers, not scanners, make publication decisions.
Not a closed door to agent participation. Agents and builders can prepare packet materials today through commissioned-packet workflows; future participation programs ship via gated participation slices.