V. The Terminology — Names, Pronunciation & Stack
What things are called and how they are said.
The Terminology is the canonical reference for naming within YounndAI.
Pronunciation, capitalization, and stack names are defined here and nowhere else.
This document supports The Guide (principles) and The Codex (invariants).
When in doubt about what to call something, start here.
1. The Brand
| Term | IPA | Phonetic | Meaning |
|---|---|---|---|
| YounndAI | /juːn.daɪ/ | yoon-dye | You and AI, unified |
Capitalization
The only correct form is YounndAI. Capital Y, lowercase ounnda, capital AI.
Never use: "Younndai", "younndAI", "YounnDAI", "YOUNNDAI", "Younnd AI", "Younnd.AI", "YoUNNdAi"
Usage
- Always written as one word, no spaces, no dots.
- In code identifiers:
younndai(lowercase) orYounndAI(PascalCase). - In URLs:
younndai(lowercase). - In sentences: "YounndAI is a philosophy of structure."
2. The YON Stack
Four tiers. Each has a name, a pronunciation, and a defined function.
| Tier | Name | IPA | Phonetic | Full Name | Function |
|---|---|---|---|---|---|
| 1 | YON | /jɒn/ | yon | YounndAI Object Notation | Data notation & format |
| 2 | SHIN | /ʃɪn/ | shin | Semantic Hub for Intelligent Notation | Compiler & transformer |
| 3 | ZEN | /zɛn/ | zen | Zero-trust Execution Node | Secure runtime |
| 4 | KEN | /kɛn/ | ken | Knowledge Evidence Nexus | Observability platform |
Capitalization
All stack names are written in ALL CAPS in prose: YON, SHIN, ZEN, KEN.
In code identifiers: lowercase (yon, shin, zen, ken).
In package names: @younndai/yon-parser, @younndai/shin-compiler.
Never use: "Yon", "Shin" (title case in prose). Always all caps or all lowercase.
Stack References
When referring to the full stack: YounndAI YON Stack or simply the stack.
When referring to tiers together: "YON → SHIN → ZEN → KEN" (arrow notation for flow).
3. Technical Vocabulary
Terms used across documentation, code, and communication.
Canonical Terms
| Use | Never Use | Why |
|---|---|---|
| record | row, entry | YON uses records, not database rows |
| field | attribute, property | Consistent with notation terminology |
| block | chunk, segment | Defined unit in YON |
| tag | directive, command | YON tags are declarative, not imperative |
| parse | deserialize | YON is parsed, not deserialized |
| format | serialize (unless specific) | YON is formatted, not serialized |
| token efficiency | compression | YON optimizes tokens, not bytes |
| profile | mode (for document metadata) | Profiles govern document behavior |
| scenario | template (for YON generation) | Scenarios define generation context |
Phonetic Aids
For presentations, podcasts, or spoken content:
| Term | Say |
|---|---|
| YounndAI | "yoon-dye" |
| YON | "yon" (rhymes with "dawn") |
| SHIN | "shin" (as in the bone) |
| ZEN | "zen" (as in Buddhism) |
| KEN | "ken" (as in "beyond my ken") |
| .yon | "dot yon" |
| .ai.md | "dot A-I dot M-D" |
| @DOC | "at-doc" |
| @SEC | "at-sec" |
4. Naming Conventions
Products & Projects
| Category | Convention | Examples |
|---|---|---|
| Brand | YounndAI — one word, specific caps | YounndAI |
| Stack tiers | ALL CAPS mononyms | YON, SHIN, ZEN, KEN |
| Packages | @younndai/ + kebab-case | @younndai/yon-parser |
| Files | kebab-case | yon-spec-standard.md |
| Components | PascalCase with layer prefix | Nol.Button, Kin.Dialog |
| Tokens | --nol- prefix, kebab-case | --nol-surface-1, --nol-accent |
New Names
When naming something new under YounndAI:
- Short. One or two syllables preferred.
- Monosyllabic for tiers. YON, SHIN, ZEN, KEN — follow the pattern.
- Meaningful. The name should hint at function.
- Pronounceable. If it can't be said aloud naturally, rename it.
- Unique within the ecosystem. No collisions with existing stack names.
Brands
When quoting a company's name, use their capitalization. "GitHub," not "GITHUB." "PostgreSQL," not "Postgresql." Respect names and trademarks the way you want yours respected.
5. Version & Document References
Version Format
- Specifications:
v2.0,v1.5(lowercase v, major.minor) - Documents: "Version 1.0" (spelled out in prose)
- Code:
2.0.0(semver, no prefix)
Document Chain
| # | Document | Short Reference |
|---|---|---|
| I | The Guide | "The Guide" or "§I" |
| II | The Codex | "The Codex" or "§II" |
| III | The Words | "The Words" or "§III" |
| IV | The Sight | "The Sight" or "§IV" |
| V | The Terminology | "The Terminology" or "§V" |
When cross-referencing: "see The Guide (§I)" or "as defined in The Codex."
Section References
Sections are referenced by document number and section number: §III.8 = The Words, section 8.
Subsections by position: §IV.2.3 = The Sight, section 2, third subsection.
These IDs are stable. Renumbering a section is an amendment.
Names carry weight. Say them correctly.
Version 1.0 · February 2026
Author: Alexandru Mareș · allemaar.com
The YounndAI philosophy and The Terminology are the personal and intellectual work of Alexandru Mareș.