Documentation

This documentation describes the Context Layer runtime and its execution model. Context Layer sits between applications and LLM providers, governing how executions are admitted, processed, and verified.

Architecture mental model

Application
│
▼
Context Layer
│
▼
LLM Provider

Application
Defines what should execute.

Context Layer
Governs how execution occurs.

LLM Provider
Generates the model output.

Get started

Provision execution authority and integrate the runtime wrapper.

• Installation. Integrate Context Layer into your application runtime.
• Execution Modes. Flow Mode and Pulse Mode overview.

Core concepts

• Structural Gap. Traditional application-to-model architectures lack a runtime execution boundary.
• Execution Authority. Context Layer enforces consistent execution behavior.
• System Boundary. Operational boundary between applications, the Context Layer runtime, and model providers.

Runtime

These pages describe runtime behavior and guarantees.

• Runtime Contract. Enforcement guarantees provided by the runtime.
• Session-Level Enforcement. Accumulated constraint rules evaluated across Flow workflow steps.
• Context Block. Structured runtime context assembled before every model invocation.
• Architecture. System topology and developer interaction model.

Reference

These pages describe API behavior and system configuration.

• API Reference. Complete runtime API specification.
• Execution Receipts. Per-step execution artifacts and evidence.
• BYOK. Provider credential management and model configuration.
• Definitions. Canonical terminology used throughout the documentation.
• Version Roadmap. Version history and planned runtime evolution.