Glossary
The vocabulary shared across Clay’s product, platform, and specs. Terms are organized by domain so each section maps to the page that owns the concept.Product primitives
Intention
A first-class signal describing what a person is trying to become and the constraints, timing,
and readiness around it. See Intentions.
Personality
A first-class signal describing how a person works and how they come across. See
Personalities.
Opportunity
Any person, team, project, job, event, community, collaborator, or partner experience that Clay
can route toward. See Opportunities.
Fit signal
A translated, consent-aware summary of why an opportunity may be relevant to an intention,
personality context, or constraint. See Consent.
Fit brief
The translated, consent-gated summary Clay produces from an intention, personality signals, and
constraints that a user can share with an opportunity source. See User experience
flows.
Translated signal
A user-approved plain-language summary of a private reflection that Clay is allowed to share
externally instead of the raw input. Raw reflections stay inside Clay.
Memory and companion
Curious pet
Clay’s emotional mascot behavior state: present, curious, slightly persistent, and always trying
to understand the user better. The pet is a behavior metaphor, not a permission to fake
dependency. See Curious pet memory.
Personal knowledge
A user-owned, optionally shareable Clay reflection organized as an MDX page with provenance,
confidence, and explicit shareability. See Curious pet memory.
Companion experience
The proactive voice and nudge model that turns personality fit into useful action. See
Companion experience.
Consent gate
The UI pattern that controls what is shareable, to whom, and under which translated signals.
Nothing leaves Clay until the user explicitly approves the shareable version. See
Consent.
Visual system and mascot
Mascot
Clay the emotional interface: a small plasticine figure with anatomy, expressions, and
animations that communicate system state without replacing consent controls or written next
steps. See Mascot.
Plasticine
Clay’s visual metaphor for moldable personal context: tactile around fit reasoning, crisp around
decisions, consent, and action. See Design language.
Theme pack
A reusable mood layer (Acid Lime, Editorial Purple+Orange, Dark Plum) that changes atmosphere,
mascot palette, and motion pacing while layout, information architecture, and consent rules stay
constant. See Themes.
Momentum button
The acid-lime call to action used only when a concrete next step is genuinely available. When
nothing actionable exists, the surface stays calm and the button is not shown.
3D and motion pipeline
Rive
The runtime for designer-authored, state-machine-driven 2D animations shipped as
.riv files
across web and mobile. See 3D generation and Rive
pipeline.Three.js
The WebGL renderer used for real-time 3D scenes in Clay’s web surfaces.
React Three Fiber
The React renderer for Three.js that lets Clay compose 3D scenes with declarative components.
Meshy
Clay’s primary image- and text-to-3D generation service for plasticine assets.
Fal
The generative model routing service Clay uses as a premium fallback for one-off hero assets
when Meshy quality is not enough.
Tripo
A text- and image-to-3D generation service kept as a deferred backup for stylized models,
multi-view flows, smart low-poly, or auto-rigging experiments.
GLB/glTF
The 3D asset container formats Clay optimizes generated models into for web and mobile runtime.
Platform and tooling
Worker
Clay’s backend runs as a Cloudflare Worker. Bindings and runtime config live in
apps/backend/wrangler.toml. See Backend overview.Mastra
The intended AI agent runtime for Clay’s backend. Mastra becomes part of the live stack once
code lands under
apps/backend/src/mastra; until then it is part of the intended design and
should be documented as implemented only after that path exists. See
Architecture.Hyperdrive
The intended Cloudflare database connection boundary for Clay’s backend. Application code should
never hold raw database URLs. Hyperdrive becomes live once a Hyperdrive binding is added to the
Worker configuration; until then it is part of the intended design and should be documented as
implemented only after the binding exists. See Environment and
bindings.
@clay/client
The Fern-generated TypeScript SDK every Clay app uses to call the API. See Client
package.
Specs site
The Mintlify site under
apps/specs. It is exported to a static bundle and deployed to the
clay-specs Cloudflare Pages project.Expo UI
The
@expo/ui package used by Clay mobile for native iOS form controls inside hosted native
subtrees. See Mobile capture flow.Cloudflare Pages
Static-site hosting on Cloudflare. Clay’s landing and specs sites deploy to separate Pages
projects (
clay-landing, clay-specs). See Deploy.Cloudflare Worker
The serverless compute runtime that hosts the Clay backend. See Backend
overview.
R2
Cloudflare’s S3-compatible object storage, used for generated 3D assets and large media. Listed
as an intended binding in Environment and bindings.
Decisions and operations
Architecture decision record (ADR)
A short, immutable Markdown record under
docs/decisions/ that captures a single architecture
decision, its rationale, and its consequences. See Decisions.Personal knowledges vault
The user-owned MDX knowledge vault Clay maintains per user. Each knowledge has frontmatter with
confidence, sensitivity, shareability, and provenance. See Curious pet
memory.