Reference

The Reference section provides canonical technical definitions and specifications for the KEK ecosystem.

These documents define the formats, terminology, and data structures used throughout KEK. They are intended for developers, quantitative users, integrators, and anyone requiring precise, implementation-level detail.

Reference material is treated as a single source of truth for how KEK objects are represented, validated, versioned, and interpreted across products and systems.

What this section covers

This section includes:

Standardized terminology used across KEK
Formal strategy specifications used in generation, validation, and optional execution workflows
Data model definitions and schemas for strategy state, metrics, and validation artifacts
Version history and system changes through a maintained changelog

How to use the Reference section

Reference pages are designed to answer questions like:

"What does this field mean?"
"What is the schema for this object?"
"What lifecycle states exist and what transitions are valid?"
"What changed between versions?"

If you want conceptual explanations and end-to-end workflow understanding, start with How KEK Works and System Architecture, then return here for exact definitions.

Reference documents

Glossary

Authoritative definitions of terms used throughout KEK documentation and interfaces.

The glossary establishes consistent meaning across:

KEK Terminal interfaces
Strategy specifications
Validation and monitoring outputs
APIs and integration surfaces

Use this when: you want canonical meaning for a term before implementing or interpreting a strategy workflow.

View Glossary →

Strategy specification

The formal specification for KEK strategies.

Defines:

Strategy structure and object hierarchy
Required vs optional fields
Parameter formatting and typing rules
Validation requirements and lifecycle expectations

This document serves as the source of truth for generation, validation, monitoring, and optional execution eligibility.

Use this when: you want to generate, validate, parse, or store strategies correctly.

View Strategy Specification →

Data models

Schema definitions for core KEK data structures.

Includes:

Strategy state (identity, version, lifecycle stage)
Performance metrics and evaluation outputs
Validation artifacts (backtests, paper trading telemetry)
Monitoring and drift signals
Execution metadata (authorization context, downstream references)

These models are used by internal systems, analytics layers, and external integrations.

Use this when: you need exact payload formats, schema expectations, or integration compatibility.

View Data Models →

Changelog

A chronological record of notable changes to the KEK system.

Includes:

Feature additions
Behavioral changes
Deprecations
Documentation updates

KEK changelogs are intended to be curated and chronologically ordered, consistent with best practices for communicating "what changed and why it matters."

Versioning may follow semantic principles so consumers can understand compatibility impact across releases.

Use this when: you need to track compatibility, identify behavior changes, or validate that your implementation matches the current spec.

View Changelog →

Usage note

The Reference section is intended to be read alongside System Architecture and How It Works:

How It Works explains the lifecycle and validation discipline
Architecture explains boundaries and system composition
Reference defines the exact objects and terms the system uses

Reference defines what the system is, not why it exists or how to use it step-by-step.