Skip to content

Convex-Dev/convex / .claude/skills/cad-reference

cad-reference

Verified

Index of the Convex Architecture Documents (CADs), the normative specifications for Convex. Use to find which CAD governs a subsystem before changing protocol, encoding, consensus or economic behaviour.

Convex Architecture Documents

CADs are the normative specifications for Convex. Where the code and a CAD disagree, that is a bug in one of them — not a licence to pick either. Before changing behaviour in a specified area, read the governing CAD and say which one you relied on.

Read them at https://docs.convex.world/docs/cad/<slug> — the slug is the CAD directory name without its numeric prefix, e.g. CAD003 is https://docs.convex.world/docs/cad/encoding.

If the design repository is checked out alongside this one, the sources are in design/docs/cad/<nnn>_<slug>/index.md. Do not assume it is present.

Core Protocol

CADSlugCovers
000principlesDesign principles behind every other decision
001archOverall architecture
002valuesCVM values
003encodingCAD3 encoding format — see the cad3-encoding skill
004accountsAccounts, addresses, controllers
005cvmexCVM execution model
033cvmtypesCVM type system

Resources and Economics

CADSlugCovers
006memoryMemory accounting and allowances — see the memory skill
007juiceJuice accounting and pricing — see the juice skill
020tokenomicsCoin supply, distribution, denominations
016peerstakePeer staking

Language and Compilation

CADSlugCovers
008compilerCompiler
009expandersExpanders and macros
011errorsError handling and error codes
012numericsNumeric semantics
013metadataMetadata
026lispConvex Lisp
032readerCVX reader syntax

Transactions and Consensus

CADSlugCovers
010transactionsTransaction format and lifecycle
051cposConvergent Proof of Stake — consensus levels, belief merge
050network_upgradeNetwork upgrades and protocol versions — see the protocol-versions skill
015peercommsPeer communication protocol
017peeropsPeer operations
018schedulerScheduled execution
021observabilityObservability
027logEvent logging

Storage and Lattice

CADSlugCovers
047etchEtch storage format — see the etch skill
048storesLattice store abstraction — roots, persistence status
049etch_gcEtch garbage collection and migration — see the etch skill
024data_latticeAbstract value, validation and merge semantics
035cursorsAtomic storage, projections and fork reconciliation
036lattice_nodeNetwork delivery and replication of hosted state
037kv_databaseKV database
039convex_sqlConvex SQL — see the convex-db skill
040lattice_queueLattice queue
028dlfsData Lattice File System
044jsonJSON on the lattice
045lattice_appsComponents: domain operations, policy, routing and publication boundaries
053lattice_regionsShared region names and references to their semantic definitions
046cell_explorerCell explorer

Assets, Identity and Trust

CADSlugCovers
019assetsAsset model
029fungibleFungible token standard — see the token skill
031nft_metadataNFT metadata
030torusTorus DEX
022trustmonTrust monitors — the authorisation model; see the trust skill
014cnsConvex Name System — see the cns skill
034curated_registryCurated registry
023keystoreKeystore
025walletHD wallets
038lattice_authSigned ownership, authorisation and authoring rules
043didDecentralised identity

CAD024 and CAD038 define semantics independently of implementation classes. Components are the normal application implementation mechanism under CAD045; they may delegate to reusable lattice definitions and use CAD035 cursors for storage. A lattice expression does not prescribe a component superclass or require a monolithic root lattice object. CAD036 supplies replication, while CAD053 registers the shared region namespace.

For a DID used as a lattice owner or signed application subject, read CAD043, CAD038 and CAD004 together. Use CAD043 for DID method syntax and resolution, CAD038 for merge-boundary signer authorisation, and CAD004 for account keys, rotation and controllers. Check the authorisation boundary of each independently mergeable signed value; do not assume that a signature around a mutable aggregate remains valid after a structural merge. For a recursive merge beneath SignedLattice, identify which authorised owner context can re-sign a synthesised result and how a non-owner relay behaves when it cannot. Raise any cross-CAD mismatch rather than copying an example silently.

Integration

CADSlugCovers
041mcpModel Context Protocol
042x402x402 protocol

CAD 0000cads is the index and describes the CAD process itself.

slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack."Stars: 196kUpdated Claude CodeCodexVerifiedInstall
ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read.Stars: 192kUpdated Claude CodeCodexVerifiedInstall
ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report.Stars: 192kUpdated Claude CodeCodexVerifiedInstall
ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt.Stars: 192kUpdated Claude CodeCodexVerifiedInstall