Documentation,organized by the work.
Navigate the public product, technology, developer, legal, and operational documentation without needing to know internal codenames or repository boundaries.
Find the boundary before the detail.
Documentation is grouped by reader intent: orientation, development, intelligence, products, and trust.
The fastest path to understanding Kri Zek, its terminology, and the connected product architecture.
05 documents / canonical public routes
Technology overview
Canonical index of the gaming intelligence stack, products, indices, models, engine, and IDE.
AI-native full-spectrum suite
The pillar game-development offering spanning intelligence, IDE, engine, validation, and delivery.
Developer program
Contribution tracks, access boundaries, consent expectations, and developer-program workflow.
Product roadmap
Evidence-grounded direction across current foundations, validation gates, active implementation, and future product paths.
Release notes
Product and website changes, public milestones, and current release direction.
Current first-party creation surfaces and the boundaries between the workbench, runtime, and gamer-aware intelligence.
05 documents / canonical public routes
Majestic Helios IDE
Windows-native Code OSS workbench, local context, Git, reviewable AI workflows, and engine bridge.
Majestic Engine
Windows-first proprietary C++20 engine, native editor, 2D production path, validation, and packaging.
Codename DRM
Beta game-protection technology integrated into the Majestic Engine build, sealing, licensing, and packaging workflow.
Full-spectrum workflow
Understand, design, author, run, validate, and deliver with project context preserved.
Developer access
Request preview access, integration review, technical discussion, or developer-relations support.
Terminology, calculation layers, model surfaces, APIs, and the consent boundary around player-derived evidence.
06 documents / canonical public routes
tGiX algorithm
Gameplay telemetry framework across eight cognitive-performance dimensions and granular measures.
The Gamer Index
Player-facing TGI interpretation, progression, and the relationship between the index and its algorithm.
Codename-TGX1
Gaming-focused small-language-model direction, current proxy boundaries, and planned variants.
Gamer Training Contributors
Consent-first PC Module contribution program, planned data boundary, review pipeline, and player controls.
Codename-TGX1 API
Scoped integration process, pricing model, permissioned inputs, and bounded outputs.
The Human Index
Private deterministic personal-trend indicator powered by the tHiX algorithm.
User-facing surfaces where the intelligence, development, health, and editorial systems become tangible.
06 documents / canonical public routes
Altered Brilliance
Gaming intelligence application for preparation, active play, reflection, GamePilot, TGI, and progression.
GamePilot
Conversational gaming copilot for mechanics, strategy, lore, current information, and approved player context.
Altered Brilliance Hub
Windows session context, device-aware telemetry, local pairing, and player-controlled performance review.
Arzenal Human Health
Local-first routines, supplements, focus, fasting, sleep, optional device-health context, and THI.
The Power of Gaming
Book and media documentation covering gaming, cognition, human potential, and game development.
The Brilliance
Consent-based weekly gaming intelligence newsletter and editorial format.
Public service boundaries, product-specific policies, availability, and system health.
05 documents / canonical public routes
Product legal directory
Dedicated privacy policies and terms for every active Kri Zek product and service.
Privacy policy
Altered Brilliance and Kri Zek data-processing, retention, security, and user-rights overview.
Terms of use
General consumer terms, intellectual property, AI disclaimers, wellness boundaries, and governing law.
System status
Live operational status and availability across public Kri Zek services.
Contact and support
Product support, privacy requests, developer relations, enterprise discussions, and general contact.
What this documentation does not expose.
This hub documents product purpose, public behavior, technical boundaries, availability, access paths, and user responsibilities. It does not publish private repositories, credentials, internal prompts, proprietary training data, security-sensitive implementation detail, or unreleased commercial terms.