The resource library

Useful things. Within easy reach.

Checklists, fictional reference payloads, and plain-language definitions for your next digital asset design review.

Your working reference

Inspect the pattern.
Ask better questions.

The API playbook makes a few important distinctions visible: identity versus label, raw quantity versus display value, receipt versus processing, and missing data versus zero.

Open the API playbook

Build a review around the question

Choose the tokenization checklist when program rules and token observations are being combined. Use the wallet checklist when a prompt changes a user's authority or asks for a consequential signature. Use the data-quality checklist when a page displays balances, valuations, activity, or a total assembled from several sources.

Each checklist is a proposed review process rather than a certification. Record the evidence that supports each answer and assign an owner to unresolved items. Printing a checklist can help a team work through the questions together, but completing the list does not guarantee security, compliance, or investment suitability.

Follow the primary reference

The Field Notes guides each link to a directly relevant primary source. For a protocol question, start with the protocol specification. For provider delivery behavior, read that provider's own contract. For product terminology, preserve the scope of the investor reference. A common term can describe different things in different systems.

The glossary offers concise definitions and links back to the relevant guide. The editorial policy explains how examples and proposed patterns are separated from documented behavior.

Read without another account

All checklists, reference files, articles, category collections, and glossary entries are public. Downloading an example does not create an account, subscribe you to email, or connect a wallet. Use the RSS feed to read the substantive material in a feed reader.