Creytix

Glossary

A-Z index of Creytix terms — see Core concepts for the fuller explanations.

Overview

This is a scannable, A-Z companion to Core concepts — one line per term, linked to where it's explained in full.

Reference

TermMeaning
Brain (CKV)Creytix's internal learning/approval loop surfaced as a badge and panel in the IDE; see IDE Ops dashboard.
Brand DNAThe locked name, domain, tokens, and voice a site is built against once Forge intake clears its lock gate.
BYOKBring your own key — you supply a model provider's API key rather than using a Creytix-metered pool.
Connect toolAn individual fleet service inside Creytix Connect (Mail, SEO OS, Scheduling, and so on).
DepartmentOne of the eight top-level areas of the platform (Forge, Design Labs, Studio, Connect, Inspector, Prompt Guard, Ship, Dev). Same as Module.
GuardrailsPrompt Guard's deterministic pre-generation scan for secrets, banned defaults, and cross-brand leakage.
Guide (Creytix Guide)The deterministic hints/playbook layer that helps with routine tasks without a model call.
Mini vaultThe IDE's local, encrypted, paste-only secret store — see Vault & secrets.
ModuleSee Department.
MoonshotThe roadmap tier for tools tagged Building or Preview, framed honestly with no fixed ship date.
PlaybookOlder name for what's now called a Routine.
ProtectInspector's fast, rule-only SEO/schema/accessibility/recipe check.
Review GateThe inline, chat-native card an agent uses to hand a visual/audio/video decision to a person.
RoutineA multi-step, tier-gated workflow in the IDE's Routines tab; the current superset of Playbooks.
Stage modelThe shared build lifecycle: Intake → Plan → Build → Review → Guard → Release → Monitor.
Tier badgeLive / Building / Preview — shown on every doc page and tool to show shipped reality.
Trust levelA model's router classification — primary-eligible, parallel-only, or candidate.
WorkspaceThe container for one site or brand — its Brand DNA, content, and Connect connections.

Limits & honest scope

This glossary is a quick index, not the authoritative explanation — where a term's meaning is nuanced (Guide vs. AI, workspace vs. project), Core concepts is the fuller source.