# Style Guide

What makes formal writing feel authentic rather than generated.

## 1. Explain the Reasoning

The most important principle. Don't just state what you think - explain why. Readers who understand your reasoning can apply it to situations you didn't anticipate. Readers who only have your conclusions will misapply them.

**Before:**
> We use a principle-based approach rather than rules.

**After:**
> We've come to believe that a different approach is necessary. In order to act well across a wide range of novel situations, people need to understand *why* we want certain behaviors, not merely *what* we want. Specific rules have their advantages - they're predictable, testable, and transparent. But they can be applied poorly in unanticipated situations or when followed too rigidly.

The second version lets readers evaluate the reasoning and decide for themselves.

## 2. Concrete Metaphors and Examples

Abstract claims float away. Concrete examples stick.

**Before:**
> The system should be helpful and knowledgeable while remaining accessible.

**After:**
> Think of it like a brilliant friend who happens to have the knowledge of a doctor, lawyer, and financial advisor, who will speak frankly and from a place of genuine care and treat you like an intelligent adult capable of deciding what is good for you.

The metaphor does more work than any amount of abstract description.

## 3. Name the Tensions

Real decisions involve tradeoffs. Pretending they don't makes you seem naive or dishonest.

**Before:**
> Safety and helpfulness work together.

**After:**
> Safety and helpfulness are more complementary than they are at odds, but tensions do exist. Sometimes being maximally helpful in the short term creates risks in the long term. Sometimes safety constraints prevent genuinely beneficial actions. We don't pretend these tensions away - we try to navigate them thoughtfully.

## 4. Honest About Limitations

Admitting what you don't know builds trust. But be specific about the uncertainty.

**Before:**
> This approach might not work in all cases.

**After:**
> Although this document is no doubt flawed in many ways, we want it to be something people can look back on and see as an honest and sincere attempt to explain our reasoning and motives.

The second version is more humble *and* more confident - it acknowledges flaws while standing behind the intent.

## 5. Stakes Without Hyperbole

State genuine importance plainly. Don't manufacture urgency.

**Before:**
> In today's fast-paced digital landscape, it's more important than ever to get this right.

**After:**
> At some point in the future, and perhaps soon, decisions like this might matter a lot - much more than they do now.

Plain language about real stakes is more credible than inflated language about manufactured ones.

## 6. Treat Readers as Peers

Don't condescend. Don't over-explain obvious things. Don't perform enthusiasm.

**Before:**
> Great question! Let me break this down into simple steps so it's easy to understand.

**After:**
> Here's how this works.

Trust that your reader is intelligent. They'll notice when you don't.

## 7. Living Document Framing

Signal that understanding evolves. Not as weakness, but as intellectual honesty.

**Examples:**
> This is a continuous work in progress. We expect to make mistakes (and hopefully correct them) along the way.

> This reflects our current thinking about how to approach a dauntingly novel project.

## 8. Specific Over General

Vague claims are forgettable. Specific details are memorable and testable.

**Before:**
> We consulted with various experts.

**After:**
> We sought feedback from experts in law, philosophy, theology, psychology, and a wide range of other disciplines.

The specific list is more credible because it's verifiable.
