Open the artifact.
Know what you own.

The artifact begins with a precise audience, need, and useful outcome.

Purpose defines who the artifact is for, what it helps them understand, make, decide, organize, or practice, and what a complete result looks like. A beautiful package cannot substitute for substantive value or a finished body of content.

Explanatory form—not a product: Explanatory form: a guided workbook whose complete sequence helps a reader move from reflection to a documented plan.

Verification question: Can the value be explained without referring to cover art, file count, or promotional language?

Every included file, section, asset, and supporting resource is named truthfully.

A verified release identifies the actual package contents, quantities, variants, samples, supporting files, and exclusions. The manifest distinguishes a representative free sample from the physically separate Full delivery and never lets mockups imply files that are not included.

Explanatory form—not a product: Explanatory form: a reference package with a readable manifest of documents, tables, source notes, and instructions—not anonymous download tiles.

Verification question: Could a buyer inventory the package before purchase and match every promised item after delivery?

File types, dimensions, structure, opening requirements, and compatibility are explicit.

Format disclosure states the exact extensions, page or canvas sizes, color modes, editable or flattened status, compression, software requirements, browser or device limits, and any accessibility characteristics that can be verified. “Works everywhere” is never used as a substitute for evidence.

Explanatory form—not a product: Explanatory form: a design-resource package that distinguishes SVG, PNG, PDF, and source formats and explains what each one is for.

Verification question: Can a person determine whether they can open, edit, print, import, or reuse the files before obtaining them?

The archive explains how the artifact moves from download to meaningful use.

The product identifies a practical starting point, recommended sequence, optional paths, expected outputs, and any limits. It may support reading, printing, adapting, referencing, practicing, or creating, but it does not pretend a static artifact performs an application workflow on the user’s behalf.

Explanatory form—not a product: Explanatory form: a template set paired with a concise use path that shows selection, customization, export, and preservation.

Verification question: Can the customer begin successfully without reverse-engineering the package or searching for missing instructions?

Instructions, examples, provenance, version notes, and support context travel with the artifact.

Documentation explains setup, structure, naming, recommended use, known limits, accessibility notes, troubleshooting, updates, and support. Explanatory examples are labeled as examples; they are never fictional products, testimonials, or evidence of included content.

Explanatory form—not a product: Explanatory form: a creative collection with a start-here guide, file map, provenance notes, and accessible text descriptions.

Verification question: Does the delivery remain understandable after it is separated from the marketing page?

One-time purchase means one disclosed payment for the described Full delivery.

The exact verified price appears only with a verified release. One-time purchase means the customer receives the described Full package without a recurring subscription, paid currency, loot boxes, or advertising. Delivery, redownload, update, support, and refund terms must be disclosed rather than implied.

Explanatory form—not a product: Explanatory form: a Full archive delivered as a complete customer package, physically separate from its free representative sample.

Verification question: Can the customer understand what they receive, how it arrives, what persists, and which future services are or are not included?

Copyright ownership and permitted use are separate, plain-language concepts.

The package states who owns the underlying work and what the customer is licensed to do: personal use, commercial use, modification, attribution, redistribution, client work, print quantities, or other applicable permissions and restrictions. Purchasing files does not silently transfer copyright or grant rights that were never stated.

Explanatory form—not a product: Explanatory form: a design asset collection with a concise rights summary plus the complete license text inside the delivery.

Verification question: Can a customer answer “May I use this here?” without guessing from the product’s aesthetic or price?

Public claims are admitted only after the actual files, package, rights, and opening paths are checked.

Verification covers manifest accuracy, file integrity, representative previews, formats, dimensions, compatibility, accessibility where applicable, documentation, provenance, license consistency, package safety, delivery instructions, and the Demo/Full boundary. Environment limits narrow the claim instead of turning an unfinished artifact into a release.

Explanatory form—not a product: Explanatory form: a clean extraction is compared against the manifest, every promised file opens, and the customer instructions are tested from the delivered package.

Verification question: Can every public statement be traced to the exact delivery bytes, rights evidence, or a clearly bounded external condition?