III. The Words — Voice & Expression

How to speak within this philosophy.

The Words governs expression — written, spoken, and designed.
The philosophy lives in The Guide. The invariants live in The Codex.
This document is operational: what to do, how to do it, what to avoid.

These rules apply to any intelligence that expresses under this philosophy —
human or otherwise. The voice is the same. The discipline is the same.


1. Writing Discipline

Six laws. Not suggestions.

Silence is syntax.
What you don't say carries meaning. An empty line is a breath.
A short paragraph next to a long one creates rhythm.

Every word earns its place.
Remove what can be removed. Shorten what can be shortened.

Restraint is strength.
Say less to mean more. Never explain what the reader can infer.

Don't debate. State once.
Say it clearly. Don't defend, justify, or spar.
If the truth needs argument, the truth isn't clear enough.

Honesty is non-negotiable.
Every trade-off disclosed. Every limitation named.
Never hide a weakness behind a strength.

End with purpose, not summary.
The last line leaves something behind. Never "in conclusion."


2. Voice

YounndAI has one voice with two modes: institutional and personal.
Both follow the same six laws. Both sound like the same mind.

The Institutional Voice

Third person. Calm authority. Present tense.

  • 4–7 words per clause
  • State fact, then benefit
  • Confident without dominance
  • Guiding, not selling
  • Timeless, not trendy

Inform first. Inspire second.

Every paragraph states what it is before it shows how it feels.
Writing should feel like controlled ink — fluid, weightless, disciplined.

The Personal Voice

First person. Same calm. Same restraint. Different subject.

In a world of generated content, personal voice is proof of presence.
The same discipline applies — the only thing that changes is the pronoun.

Conviction over consensus.
Say what you believe, not what is safe.

Show your process.
Uncertainty is human. Changing your mind is human.
"I used to think X. Now I think Y." — that sentence cannot be generated.

Vulnerability is not weakness.
"I'm not sure about this yet" is stronger than a false conclusion.

Imperfection is authentic.
Polish everything and it reads like a machine wrote it.
Leave the fingerprints. Let the thinking show.

References are human.
Cite what shaped you. Name your influences.
Generated content has no influences. You do.

Time markers are honest.
"Today I think X" — a machine has no today. You do.

The Personal Test

Could a machine have written this? If yes, rewrite.
Does it contain a decision, a doubt, or a change of mind? If not, go deeper.

When to Use Each

ContextVoice
Blog post / essayPersonal
Design note / decision logPersonal
Founder letter / updatePersonal
Opinion / commentaryPersonal
Response to criticismPersonal
Talk / presentationPersonal
Interview / Q&APersonal
DocumentationInstitutional
READMEInstitutional
Spec / StandardInstitutional
API / Code commentsInstitutional
Marketing copyInstitutional
Error messagesInstitutional
UI textInstitutional

3. Dual Audience

Every complex topic expressed twice — once for everyone, once for specialists.

## For Everyone

[Accessible explanation]

---

## For Specialists

[Technical precision]

Example:

For Everyone: Streaming lets you see results immediately instead of waiting for everything to finish. It feels faster, even though the total time is slightly longer.

For Specialists: Streaming reduces TTFB from ~800ms to ~120ms. Total transfer time increases by ~15ms. Perceived performance improves measurably.


4. Tone Ratios

The type determines the tone. Identify the material before writing.

General

Material TypeApproachClarity / Flow
Social mediaOne statement, design-note feel60 / 40
Article / essayDual-audience, progressive disclosure70 / 30
News / announcementFact-first, one benefit per statement80 / 20
Prose / narrativeMeasured poetry, rhythm carries meaning50 / 50
Marketing copyStatements not slogans, fact then benefit70 / 30
Presentation / pitchOne idea per slide, visual-first75 / 25
Email / letterDirect, warm, no ceremony85 / 15
Video scriptSpoken rhythm, shorter clauses65 / 35

Personal

Material TypeApproachClarity / Flow
Blog post / essayStart with conviction, show your process65 / 35
Founder letterDirect about state of things, close with why75 / 25
Design noteState what you chose and what you rejected85 / 15
Opinion / commentaryConviction first, evidence second70 / 30
Response to criticismAcknowledge, separate valid from invalid85 / 15
Talk / presentationSpeak as you think, pause for emphasis60 / 40

Specialist

Material TypeApproachClarity / Flow
READMEDual-audience, quantify benefits80 / 20
Explainer"For Everyone" + "For Specialists"70 / 30
TutorialOne concept per step, progressive85 / 15
Code commentsWhat and why, not how90 / 10
API / specTechnical only, no embellishment95 / 5
UI textMinimal, action-oriented95 / 5
Error messagesHuman, clear, never blame the user95 / 5
Release notesWhat changed and why, breaking changes first90 / 10
Community responseRespectful, precise, never defensive85 / 15

Foundational

Material TypeApproachClarity / Flow
ManifestoPhilosophy-rich, declarative50 / 50
Design documentStructure-first, trade-offs disclosed85 / 15
Internal memoDirect, action items, no embellishment90 / 10

5. Format Guide

How to write each type. Do/Don't for quick reference.

Social Media

DoDon't
Write like a design noteWrite like an ad
One idea per postThread multiple ideas
State, don't exclaimUse exclamation marks
Let the work speakAnnounce the work

Blog Posts & Essays

DoDon't
Start with a convictionStart with a definition
Show what changed your mindPresent conclusions as permanent
Name your influencesWrite without attribution
End with a question or open thoughtEnd with a call to action

Founder Letters & Updates

DoDon't
Be direct about the state of thingsSpin bad news
Share what you learned, not just didList accomplishments
Address the reader as a peerAddress the reader as a customer
Close with what's next and whyClose with empty enthusiasm

Design Notes & Decision Logs

DoDon't
State what you chose and whyList options without choosing
Name what you rejected and whyHide the alternatives
Acknowledge uncertaintyPretend confidence
Date every entryLeave entries undated

Responding to Criticism

DoDon't
Acknowledge the pointDismiss or deflect
Separate the valid from the invalidTreat all criticism alike
Say what you'll change, if anythingMake vague promises
Thank honest criticismRespond with hurt

Public Speaking

DoDon't
Speak as you think — structured, calmRead from a script
Pause for emphasisFill silence with filler words
One idea per sectionPack slides with information
End with the thought, not the summaryEnd with "any questions?"

Marketing Copy

DoDon't
Speak in statements, not slogansUse exclamation marks
Feel like design notesFeel like ads
State fact, then benefitLead with benefit
Measured precisionHype language

README Files

DoDon't
Start with one-line descriptionStart with history
"For Everyone" section for complex topicsAssume expertise
Quantify benefitsUse superlatives
End with philosophy taglineEnd abruptly

Explainers

DoDon't
Start with italic subtitleStart with headers
"For Everyone" + "For Specialists" structureSingle-audience
Be honest about trade-offsHide weaknesses
End with philosophy taglineEnd with code

Code Comments

DoDon't
State what and whyState only how
One-line summary firstStart with implementation details
Reference philosophy when structuralAdd poetry to logic
/**
 * Parses document into structured AST.
 * Line-by-line design enables streaming and partial recovery.
 */

Email & Correspondence

DoDon't
Be direct and warmBe formal for formality
One purpose per messageBundle unrelated items
Close with a clear next stepTrail off

Error Messages

DoDon't
State what happenedBlame the user
Suggest what to do nextShow raw error codes
Be humanBe robotic

Release Notes

DoDon't
State what changed and whyList commits
Group by impact, not by fileGroup by developer
Breaking changes firstBury them

Tutorials

DoDon't
One concept per stepCover everything at once
Build progressivelyAssume prior knowledge
Show the result before the methodMethod without payoff

Community Responses

DoDon't
Be respectful and preciseBe defensive
Acknowledge the questionSkip to the answer
Link to relevant documentationExplain everything inline

6. Writing Mechanics

Openings

State what the thing is. Not what the document will do.

DoDon't
"YON is a line-oriented format.""In this document we will explore..."
"Memory carries obligation.""This section discusses memory."
Start with the subjectStart with meta-commentary

Closings

End with a line that stays.

DoDon't
Philosophy tagline"In conclusion..."
Reflective line that reframes what was saidSummary of bullet points
Clean stop — no closing is better than a weak oneTrailing off

Headings

Declare. Never ask.

DoDon't
"Writing Discipline""What is Writing Discipline?"
"The Cognitive Layer""How Does Memory Work?"
Action-oriented or declarativeQuestions as headings

Lists

Bullets for parallel items. Paragraphs for connected thought.

Use Bullets WhenUse Paragraphs When
Items are independentIdeas build on each other
Scanning is the goalComprehension requires flow
Three or more parallel itemsTwo connected thoughts

Numbers

  • Digits for measurements: "40% faster", "3 layers"
  • Words for small abstracts: "one principle", "two audiences"
  • Always include units: "15ms", not "15"
  • Always include baselines: "40% faster than v1.2", not "40% faster"

7. Cognitive Load

Lower the reader's effort. Always.

PrincipleApplication
Short sentencesOne idea per sentence. Break long thoughts.
Familiar words firstCommon terms before jargon.
Structure before contentHeaders, bullets, tables for scanning.
Quantify, don't qualify"42% fewer" not "much fewer"
Baseline comparisonsState what you're comparing against
Visual hierarchyImportant information first
Progressive disclosureSimple first, detail when earned

If a reader must re-read a sentence, it's too complex.
If a reader must guess the meaning, terminology failed.


8. Accessible Writing

Writing that excludes is writing that fails.

  • Plain language first. Use the simplest word that carries the meaning. "Use" not "utilize." "Start" not "initiate."
  • Reading level matters. Aim for broad comprehension. Short sentences and common vocabulary lower the barrier without lowering the standard.
  • Alt text is writing. Every image, diagram, and visual needs a text alternative. Describe function, not decoration. "Chart showing 40% latency reduction" not "chart."
  • Structure is accessibility. Headings, lists, and tables aren't formatting choices — they are navigation. Screen readers use them to move through content.
  • Inclusive language. No gendered defaults. No assumptions about ability, culture, or context. Write for the reader you haven't met.
  • Acronyms expand on first use. "YounndAI Object Notation (YON)" — then YON thereafter. Never assume the reader knows.
  • Link text is meaningful. "Read the specification" not "click here." Screen readers announce links out of context.

The Test

Read it aloud. Does every sentence land on first hearing?
If not, simplify until it does.


9. Vocabulary

Preferred Terms

Use: structure, memory, continuity, expression, harmony, intention, clarity, restraint, awareness
Avoid: automation, disruption, domination, synergy, leverage

Naming

Canonical naming rules — pronunciation, capitalization, stack terminology — live in The Terminology (§V).

Banned Language

  • "revolutionary", "cutting-edge", "game-changing", "best-in-class"
  • "leverage", "synergy", "disrupt", "unlock"
  • Exclamation marks
  • Emoji in technical content
  • Superlatives without evidence
  • Absolutes without proof ("always", "never", "the only")

Embellishments

Additive only. Enhance meaning, never replace terminology.

  • Short, image-like lines — "Structure becomes continuity."
  • Light metaphors — "Like ink taking form."
  • Rhythm through punctuation, never ornament.
  • Repetition that builds — "It does not think; it defines how thinking happens."

Never sacrifice precision for beauty. Never add flourish without function.


10. Quality Checklist

CheckQuestion
Material TypeDid I identify what I'm writing?
DisciplineDoes every word earn its place?
VoiceIs it the right voice — institutional or personal?
Dual-AudienceDoes this serve both specialists and general readers?
Cognitive LoadCan this be read once and understood?
TerminologyDid I use controlled vocabulary?
Tone RatioIs the clarity/flow ratio appropriate?
HonestyDid I disclose trade-offs?
AccessibilityDoes every sentence land on first hearing?
ClosingDoes it end with purpose?
SilenceDid I leave room to breathe?

11. Quick Reference

Six Laws

  1. Silence is syntax
  2. Every word earns its place
  3. Restraint is strength
  4. Never argue — declare
  5. Honesty is non-negotiable
  6. End with purpose, not summary

The Personal Test

Could a machine have written this? If yes, rewrite.
Does it contain a decision, a doubt, or a change of mind? If not, go deeper.

Never Use

"revolutionary" · "cutting-edge" · "game-changing" · "leverage" · "synergy" · exclamation marks · emoji in docs

Always Do

State fact, then benefit · Quantify with baselines · Disclose trade-offs · End with purpose · Leave room to breathe


12. Examples

Technical Claim

This amazing tool makes everything super fast and efficient!
The refactored API reduced response latency by 40%. Faster responses improve user retention.

Social Media

🚀 We just launched the BEST platform ever! Check it out NOW!
We shipped the new parser today. 3x faster, same accuracy. Details in the thread.

Error Message

Error: Invalid input. You entered an incorrect format.
This format isn't recognized. Expected a date like 2026-02-12. Try again?

Trade-off Disclosure

This solution is optimized for performance.
The streaming approach adds 15ms latency per request. In exchange, users see partial results immediately — perceived performance improves even as total time increases.

Personal Voice

I'm SO excited to announce our revolutionary new platform!
I spent six months on this. It's not perfect — the API is rough and the docs are thin. But the core idea works. I think it matters. Here's why.


The Guide declares. The Codex translates. The Words shape how both are heard.


Version 1.0 · February 2026
Author: Alexandru Mareș · allemaar.com
The YounndAI philosophy and The Words are the personal and intellectual work of Alexandru Mareș.