Documentation
Concepts and operator guides
Creytix docs live in the fleet workspace repo — this page summarizes core concepts and links to SSOT markdown for deeper setup.
Core concepts
Creytix is a planning-first AI platform umbrella: Forge (intake), Studio (production), Design Labs (system), Inspector (QA), Prompt Guard (safety), and Releases (shipping). Projects are the central object; modules are views into the same work.
Stage model
Every project progresses through Intake → Plan → Build → Review → Guard → Release → Monitor. Stage chips appear across Protect results, project tabs, and release checklists so operators scan status consistently.
Operator vs marketing surfaces
creytix.com explains the platform publicly. Authenticated /app on creytix-front is the product shell stub; full operator tools run on Creytix ECP (localhost:3010 in dev) until native /app modules ship.
Inspector pre-ship
Run npm run forge:platform:ci -- --slug=expedia-parts --url=http://guest.localhost:3000 --json from the workspace root. See docs/fleet/INSPECTOR_OPERATOR_RUNBOOK.md for daily Protect flow.
Fleet workspace
Open Expedia-Solutions.code-workspace at the fleet root — not a single site repo. Rules, HF staging, and Inspector projects live in expedia-solutions SSOT.
Repository docs (SSOT)
- Sitemap & wireframe spec ↗
- Website process ↗
- Brand architecture ↗
- Inspector runbook ↗
- Route registry JSON ↗
Fleet operators: open /app after sign-in · run npm run ecp:dev for full Creytix console.
Onboarding
Evaluating Creytix for your fleet?
Tell us your team shape and sites — we will route a focused demo around your use case.