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
| Context | Voice |
|---|---|
| Blog post / essay | Personal |
| Design note / decision log | Personal |
| Founder letter / update | Personal |
| Opinion / commentary | Personal |
| Response to criticism | Personal |
| Talk / presentation | Personal |
| Interview / Q&A | Personal |
| Documentation | Institutional |
| README | Institutional |
| Spec / Standard | Institutional |
| API / Code comments | Institutional |
| Marketing copy | Institutional |
| Error messages | Institutional |
| UI text | Institutional |
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 Type | Approach | Clarity / Flow |
|---|---|---|
| Social media | One statement, design-note feel | 60 / 40 |
| Article / essay | Dual-audience, progressive disclosure | 70 / 30 |
| News / announcement | Fact-first, one benefit per statement | 80 / 20 |
| Prose / narrative | Measured poetry, rhythm carries meaning | 50 / 50 |
| Marketing copy | Statements not slogans, fact then benefit | 70 / 30 |
| Presentation / pitch | One idea per slide, visual-first | 75 / 25 |
| Email / letter | Direct, warm, no ceremony | 85 / 15 |
| Video script | Spoken rhythm, shorter clauses | 65 / 35 |
Personal
| Material Type | Approach | Clarity / Flow |
|---|---|---|
| Blog post / essay | Start with conviction, show your process | 65 / 35 |
| Founder letter | Direct about state of things, close with why | 75 / 25 |
| Design note | State what you chose and what you rejected | 85 / 15 |
| Opinion / commentary | Conviction first, evidence second | 70 / 30 |
| Response to criticism | Acknowledge, separate valid from invalid | 85 / 15 |
| Talk / presentation | Speak as you think, pause for emphasis | 60 / 40 |
Specialist
| Material Type | Approach | Clarity / Flow |
|---|---|---|
| README | Dual-audience, quantify benefits | 80 / 20 |
| Explainer | "For Everyone" + "For Specialists" | 70 / 30 |
| Tutorial | One concept per step, progressive | 85 / 15 |
| Code comments | What and why, not how | 90 / 10 |
| API / spec | Technical only, no embellishment | 95 / 5 |
| UI text | Minimal, action-oriented | 95 / 5 |
| Error messages | Human, clear, never blame the user | 95 / 5 |
| Release notes | What changed and why, breaking changes first | 90 / 10 |
| Community response | Respectful, precise, never defensive | 85 / 15 |
Foundational
| Material Type | Approach | Clarity / Flow |
|---|---|---|
| Manifesto | Philosophy-rich, declarative | 50 / 50 |
| Design document | Structure-first, trade-offs disclosed | 85 / 15 |
| Internal memo | Direct, action items, no embellishment | 90 / 10 |
5. Format Guide
How to write each type. Do/Don't for quick reference.
Social Media
| Do | Don't |
|---|---|
| Write like a design note | Write like an ad |
| One idea per post | Thread multiple ideas |
| State, don't exclaim | Use exclamation marks |
| Let the work speak | Announce the work |
Blog Posts & Essays
| Do | Don't |
|---|---|
| Start with a conviction | Start with a definition |
| Show what changed your mind | Present conclusions as permanent |
| Name your influences | Write without attribution |
| End with a question or open thought | End with a call to action |
Founder Letters & Updates
| Do | Don't |
|---|---|
| Be direct about the state of things | Spin bad news |
| Share what you learned, not just did | List accomplishments |
| Address the reader as a peer | Address the reader as a customer |
| Close with what's next and why | Close with empty enthusiasm |
Design Notes & Decision Logs
| Do | Don't |
|---|---|
| State what you chose and why | List options without choosing |
| Name what you rejected and why | Hide the alternatives |
| Acknowledge uncertainty | Pretend confidence |
| Date every entry | Leave entries undated |
Responding to Criticism
| Do | Don't |
|---|---|
| Acknowledge the point | Dismiss or deflect |
| Separate the valid from the invalid | Treat all criticism alike |
| Say what you'll change, if anything | Make vague promises |
| Thank honest criticism | Respond with hurt |
Public Speaking
| Do | Don't |
|---|---|
| Speak as you think — structured, calm | Read from a script |
| Pause for emphasis | Fill silence with filler words |
| One idea per section | Pack slides with information |
| End with the thought, not the summary | End with "any questions?" |
Marketing Copy
| Do | Don't |
|---|---|
| Speak in statements, not slogans | Use exclamation marks |
| Feel like design notes | Feel like ads |
| State fact, then benefit | Lead with benefit |
| Measured precision | Hype language |
README Files
| Do | Don't |
|---|---|
| Start with one-line description | Start with history |
| "For Everyone" section for complex topics | Assume expertise |
| Quantify benefits | Use superlatives |
| End with philosophy tagline | End abruptly |
Explainers
| Do | Don't |
|---|---|
| Start with italic subtitle | Start with headers |
| "For Everyone" + "For Specialists" structure | Single-audience |
| Be honest about trade-offs | Hide weaknesses |
| End with philosophy tagline | End with code |
Code Comments
| Do | Don't |
|---|---|
| State what and why | State only how |
| One-line summary first | Start with implementation details |
| Reference philosophy when structural | Add poetry to logic |
/**
* Parses document into structured AST.
* Line-by-line design enables streaming and partial recovery.
*/
Email & Correspondence
| Do | Don't |
|---|---|
| Be direct and warm | Be formal for formality |
| One purpose per message | Bundle unrelated items |
| Close with a clear next step | Trail off |
Error Messages
| Do | Don't |
|---|---|
| State what happened | Blame the user |
| Suggest what to do next | Show raw error codes |
| Be human | Be robotic |
Release Notes
| Do | Don't |
|---|---|
| State what changed and why | List commits |
| Group by impact, not by file | Group by developer |
| Breaking changes first | Bury them |
Tutorials
| Do | Don't |
|---|---|
| One concept per step | Cover everything at once |
| Build progressively | Assume prior knowledge |
| Show the result before the method | Method without payoff |
Community Responses
| Do | Don't |
|---|---|
| Be respectful and precise | Be defensive |
| Acknowledge the question | Skip to the answer |
| Link to relevant documentation | Explain everything inline |
6. Writing Mechanics
Openings
State what the thing is. Not what the document will do.
| Do | Don't |
|---|---|
| "YON is a line-oriented format." | "In this document we will explore..." |
| "Memory carries obligation." | "This section discusses memory." |
| Start with the subject | Start with meta-commentary |
Closings
End with a line that stays.
| Do | Don't |
|---|---|
| Philosophy tagline | "In conclusion..." |
| Reflective line that reframes what was said | Summary of bullet points |
| Clean stop — no closing is better than a weak one | Trailing off |
Headings
Declare. Never ask.
| Do | Don't |
|---|---|
| "Writing Discipline" | "What is Writing Discipline?" |
| "The Cognitive Layer" | "How Does Memory Work?" |
| Action-oriented or declarative | Questions as headings |
Lists
Bullets for parallel items. Paragraphs for connected thought.
| Use Bullets When | Use Paragraphs When |
|---|---|
| Items are independent | Ideas build on each other |
| Scanning is the goal | Comprehension requires flow |
| Three or more parallel items | Two 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.
| Principle | Application |
|---|---|
| Short sentences | One idea per sentence. Break long thoughts. |
| Familiar words first | Common terms before jargon. |
| Structure before content | Headers, bullets, tables for scanning. |
| Quantify, don't qualify | "42% fewer" not "much fewer" |
| Baseline comparisons | State what you're comparing against |
| Visual hierarchy | Important information first |
| Progressive disclosure | Simple 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
| Check | Question |
|---|---|
| Material Type | Did I identify what I'm writing? |
| Discipline | Does every word earn its place? |
| Voice | Is it the right voice — institutional or personal? |
| Dual-Audience | Does this serve both specialists and general readers? |
| Cognitive Load | Can this be read once and understood? |
| Terminology | Did I use controlled vocabulary? |
| Tone Ratio | Is the clarity/flow ratio appropriate? |
| Honesty | Did I disclose trade-offs? |
| Accessibility | Does every sentence land on first hearing? |
| Closing | Does it end with purpose? |
| Silence | Did I leave room to breathe? |
11. Quick Reference
Six Laws
- Silence is syntax
- Every word earns its place
- Restraint is strength
- Never argue — declare
- Honesty is non-negotiable
- 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ș.