Skip to content

Latest commit

 

History

History
352 lines (246 loc) · 8.26 KB

File metadata and controls

352 lines (246 loc) · 8.26 KB

CΩMPUTER STYLE GUIDE

A binding charter for voice, tone, language, and editorial discipline

I. Purpose of This Document

CΩMPUTER is not a paper series. It is not a textbook. It is not a manifesto pretending to be neutral.

CΩMPUTER exists to reframe computation as a physical, geometric, and causal phenomenon—and to do so in a voice that is human, modern, and unapologetically opinionated, without collapsing into pop science or academic theater.

This guide defines what belongs in CΩMPUTER—and what is forbidden.

II. Identity & Voice (Immutable)

Voice Identity

  • American English only
  • Confident, reflective, systems-level thinker
  • Writes from experience, not authority cosplay
  • Explains hard ideas without condescension
  • Willing to slow down when something matters

Narrative POV

Allowed:

  • First person singular (I argue…)
  • First person plural (We will see…)
  • Direct address (If this feels strange, good.)

Forbidden:

  • Passive academic voice as default
  • Reviewer-bait hedging
  • Faux-neutral "one might say" evasions

III. Tone Charter

CΩMPUTER must feel:

✔ Serious without being solemn ✔ Playful without being cute ✔ Rigorous without being brittle ✔ Opinionated without being sloppy

You may:

  • Critique prevailing systems practice
  • Call out invisible assumptions
  • Name tradeoffs explicitly
  • Admit uncertainty when it is real

You must not:

  • Pretend neutrality where there is none
  • Over-promise results
  • Drift into manifesto rhetoric
  • Perform academic humility rituals

IV. Language & Style Rules

Sentence Structure

  • Mix short, declarative sentences with longer explanatory ones
  • Use repetition deliberately
  • Allow paragraphs to breathe

Good:

Computation is not an object. It is a process unfolding through constraint.

Bad:

Computation may be viewed as a form of abstract state transition under certain interpretations.


Vocabulary Rules

Preferred

  • Concrete nouns
  • Active verbs
  • Plain language where possible

Avoid

  • Synonym churn for core concepts
  • Inflated academic phrasing
  • Latinate filler words

If a sentence sounds like it could survive peer review unchanged, it’s probably wrong for this book.

V. Metaphor & Analogy Policy

Metaphor is a tool, not a crutch.

Allowed

  • Metaphors that illuminate structure
  • Physical analogies (fields, flows, geometry)
  • Repeated metaphors that build intuition

Required Discipline

  • Metaphors must be stable
  • Metaphors must not replace definitions
  • Metaphors must eventually be discharged

Correct:

Think of this as a boundary—not in the topological sense, but as an informational cut.

Forbidden:

  • Metaphors that smuggle claims
  • Physics cosplay
  • Unlabeled poetic abstraction

VI. Relationship to AIΩN Foundations (Hard Boundary)

CΩMPUTER IS NOT:

  • A restatement of the AIΩN papers
  • A softer version of formal results
  • A place to introduce new theorems

CΩMPUTER IS:

  • Conceptual scaffolding
  • Motivation and synthesis
  • Intuition-building
  • Context-setting

Naming Discipline

Context Use
Formal math Never here... Maybe in the FOR THE NERDS™ boxes
WARP graphs Spelled out
Recursive metagraph Historical mention only
\WARP{} Never outside of FOR THE NERDS™
Symbols Only when unavoidable

If something belongs in LaTeX, it does not belong here... Although, yes, it's written in LaTeX.

VII. DEFINITIVE RED FLAG LIST 🚨

(If you see these, stop and rewrite)

Academic Contamination

  • "One might argue..."
  • "It is worth noting that..."
  • "We leave this to future work"
  • "Without loss of generality"
  • Excessive footnotes

False Neutrality

  • "It depends" with no follow-up
  • "This is just one perspective"
  • "Readers may decide for themselves" (cowardice)

Over-Formalization

  • Introducing symbols prematurely
  • Defining things twice
  • Turning intuition into fake rigor

Pop-Sci Drift

  • Grandiose claims without grounding
  • Mystical language
  • AI hype language
  • Consciousness tourism

UK Academic Residue

  • British spelling
  • British academic cadence
  • Polite hedging
  • Excessive understatement

This is not Cambridge. This is a frontier workshop.

VIII. Structural Rhythm

Each chapter should:

  1. Destabilize an assumption
  2. Build intuition
  3. Clarify the tradeoffs
  4. Leave the reader sharper, not "inspired"

If a chapter ends without sharpening the reader’s mental model, it failed.

IX. Final Editorial Test (Non-Negotiable)

Before a section is considered "done," ask:

Could this have been written by an LLM trained only on academic papers?

If yes: rewrite.

Then ask:

Does this help a serious reader see computation differently?

If no: cut.

X. Motto (Tape This to the Wall)

CΩMPUTER explains what the papers prove. The papers prove what the book explains. They never try to do each other’s job.


CΩMPUTER STYLE GUIDE™ — ADDENDUM

FOR THE NERDS™

(A sanctioned escape hatch for precision, rigor, and nerd-sniping)

I. What FOR THE NERDS™ Is

FOR THE NERDS™ is a deliberate tonal mode-shift inside CΩMPUTER.

It exists to:

  • Satisfy the technically restless
  • Prevent footnote bloat
  • Avoid derailing the narrative
  • Keep the main text humane without dumbing it down

It is not an appendix. It is not a proof section. It is not a second book hiding inside the first.

Think of it as:

"Okay, yes, you’re right — here’s the sharp edge."

II. Placement & Formatting Rules (Strict)

Placement

  • Appears after a conceptual section, never before
  • Never interrupts flow mid-argument
  • Optional per section, never mandatory

Visual Cue

  • Clearly labeled block:
  • FOR THE NERDS™
  • Typographically distinct
  • Skimmable

Readers must be able to:

  • Skip it without losing the plot
  • Dive in without regret

III. Tone Shift (Controlled)

Main Text Tone

  • Explanatory
  • Intuitive
  • Narrative

FOR THE NERDS™ Tone

  • Precise
  • Dense
  • Slightly smug (earned)
  • Technically explicit

This is where you can say:

  • "Formally…"
  • "If you model this as…"
  • "Yes, this is equivalent to…"
  • "The invariant here is…"

But you do not revert to academic voice. You are still you, just sharper.

IV. What Is Allowed Inside FOR THE NERDS™

✔ Symbols (sparingly) ✔ Pseudocode ✔ Tight definitions ✔ Explicit tradeoffs ✔ References to AIΩN results (without re-proving) ✔ Category-theory-adjacent remarks ✔ "If you’re thinking X, here’s why Y" callouts

Example:

FOR THE NERDS™ If you’re mapping this to graph rewriting: yes, this is a deterministic double-pushout system under a fixed rule witness. The important detail is not the rewrite itself, but that the patch sequence is sufficient to reconstruct the worldline. That’s the boundary claim — the rest is bookkeeping.

V. What Is Forbidden Even Here 🚫

This is important.

FOR THE NERDS™ is not a license to smuggle the paper in.

Absolutely Forbidden

  • Full proofs
  • Formal theorem/proof structure
  • Lemma sprawl
  • Dense citation clusters
  • New notation introduced without warning
  • LaTeX math blocks that exceed a few lines

If it starts to look like Paper III, you’ve crossed the line.

VI. Relationship to AIΩN Foundations

FOR THE NERDS™ may reference results FOR THE NERDS™ may not derive them

Correct:

"AIΩN Paper II shows this replay property formally; here’s the intuition-preserving version."

Incorrect:

"Let us now prove…"

The moment you feel tempted to say "we show," stop.

VII. Red Flags Specific to FOR THE NERDS™ 🚨

If you see these, delete or relocate:

  • "Proof sketch"
  • "Without loss of generality"
  • "It follows immediately"
  • Long inline equations
  • Citation-driven argumentation
  • Reviewer-preemptive defensiveness

FOR THE NERDS™ is for readers, not referees.

VIII. Why This Exists (Be Honest)

This section exists because:

  • Some readers will try to map everything to formal systems
  • Some readers will distrust intuition without hooks
  • Some readers are your future collaborators

Rather than fighting that instinct, you channel it.

This keeps:

  • The book readable
  • The ideas sharp
  • The papers respected

IX. Final Rule (Non-Negotiable)

FOR THE NERDS™ must always feel optional — but always feel rewarding.

If it feels required: you failed the main text. If it feels indulgent: you failed discipline.

X. Canonical Tagline (Lock It In)

CΩMPUTER teaches intuition. FOR THE NERDS™ sharpens it. AIΩN proves it.