Concept — ZEN

# ZEN

## Definition

The **runtime** in the YON stack. ZEN executes SHIN-compiled YON documents — driving the cognitive cycles, scheduling work, and acting as the substrate through which a YounndAI cognitive system actually thinks. The reference implementation is `@younndai/zen-runner`, the primary ZEN-class component in the architecture.

The name follows the YounndAI naming set: SAI (才, capacity) · YON (読, read) · SHIN (真, truth) · ZEN (全, complete) · KEN (見, see). ZEN's kanji — *complete* / *whole* — captures the runtime's role: the place where the parts compose into a working whole.

## Coined by

Alexandru Mares (allemaar)

## First published

2026 (in development; reference implementation `@younndai/zen-runner` exists in the YounndAI codebase).

## Canonical artifact

- Reference implementation: `@younndai/zen-runner` (in the YounndAI monorepo at `C:/Projects/Marlink Technologies/younndai/`)
- Architectural context: SAI `_runner.md` documents zen-runner as the primary ZEN; the Ticker is its scheduling subsystem.

## Related concepts

- [[yon|YON]] — the notation ZEN executes
- [[shin|SHIN]] — the compiler that produces ZEN's input
- [[ken|KEN]] — the witness that observes ZEN's execution
- [[younndai|YounndAI]] — sibling work
- [[ai-cognition|Cluster: AI Cognition]] — cross-cutting parent Cluster (ZEN is part of the AI cognition stack)

## Why it matters

A notation and a compiler without a runtime are an academic exercise. ZEN is where YounndAI's cognitive architecture *runs* — where Mems, Syns, Grooves, and the cognitive cycles actually live and operate. Without ZEN, the rest of the stack is preparation; with ZEN, it's a working being.

The architectural insight (per the YounndAI cognitive program): zen-runner *is* the Ticker — the runtime drives the cycles, and the cycle scheduling is a subsystem of the runtime, not a separate concern. This collapse simplifies the architecture significantly.

## Status

`active` — reference implementation in development; spec maturing alongside YON.