> For the complete documentation index, see [llms.txt](https://research.ambitiousimpact.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://research.ambitiousimpact.com/other/style-guide.md).

# Style Guide

## Overview

This guide governs all AIM research writing. Apply it by default; deviate only with good reason.

### Audiences (in priority order):

CE decision-makers → CE incubatees → general public

**Writing goal:** Support decision-making through clear reasoning and transparent evidence.

### Style Rules

#### Voice & Person

* Use "we" for AIM actions: "We conducted a geographic analysis."
* Use specific actor for implementation: "The non-profit could implement X" (not "we could").
  * Avoid the use of the word "charity". Instead use "non-profit" or simply "organization". 
* Use active voice: "Researchers showed that…" (not "It was shown that…").
* Use gender-neutral pronouns (they/them) unless context requires otherwise.

#### Tense

* Evidence and findings: past tense — "Savoie and Sarek (2020) concluded that…"
* General statements: simple present — "we discuss" (not "we will be discussing").

#### Punctuation & Mechanics

* Oxford comma required: "CEA, WFM, EpV, and IC."
* Em dash (—): no spaces; use for emphasis, interruptions, or additional info.
* En dash (–): no spaces; use for ranges (pages, dates, numbers).
* "Double quotation marks" for direct quotes and emphasized terms.
* Single quotation marks only for quotes within quotes.
* Footnotes placed after punctuation marks.¹
* No chained parentheses. Use semicolons to separate: "(like this; and this)."

#### Spelling & Terminology

* American spelling throughout (arbiter: Merriam-Webster).
* Spell out all acronyms on first use; never explain the same acronym twice.
* Do not assume familiarity with Effective Altruist or subject-specific terminology; define all terms.

#### Numbers

* Spell out one through nine; use numerals for 10 and above.
* Exception: always use numerals in dates and data tables.
* Thousands separator: comma — 10,000 / 1,000
* Exact numbers: do not round.
* Estimates: round to two significant figures (e.g., 1.375% → 1.4%).
* Leading zero: include only when the value can exceed one (e.g., 0.8 kg); omit for values that never exceed one (e.g., p < .05).

#### Dates&#x20;

* Format: Day Month Year — "27 February 2020."

#### Sentences & Paragraphs

* Begin each paragraph with a topic sentence stating the paragraph's main point.
* Keep paragraphs and sentences short.
* Use lists, examples, and illustrations to aid clarity.

### Formatting

#### Document Defaults

* Font: Inter, size 11.5, 1.5 line spacing.
* Add space after each paragraph.
* Left-aligned throughout.
* Heading case: sentence case — capitalize first word only.
* Footnote text: size 9.

#### Captions

* Figures: "Figure X: Title" — placed below the figure.
* Tables: "Table X: Title" — placed above the table.
* In-text: refer by number (hyperlinked); avoid directional language ("above," "below").
* No abbreviation tables.

#### Colors

**Brand palette:**

<table><thead><tr><th width="153.66668701171875">Name</th><th>Hex</th><th>Notes</th></tr></thead><tbody><tr><td>Black </td><td>#000000</td><td></td></tr><tr><td>CE Red </td><td>#801C31</td><td>White font required on background</td></tr><tr><td>Gray </td><td>#2F2E2E </td><td></td></tr><tr><td>Alternative Red</td><td>#A53247 </td><td>White font required on background</td></tr><tr><td>Pink-ish</td><td>#F6EDFC </td><td></td></tr><tr><td>Off white</td><td>#F8F8F8 </td><td></td></tr></tbody></table>

Grading palette:

| Level       | Hex     |
| ----------- | ------- |
| High        | #F4CCCC |
| Medium-high | #FCE5CD |
| Medium      | #FFF2CC |
| Low-Medium  | #D9EAD3 |
| Low         | #B6D7A8 |

### Accessibility

* No underline except for hyperlinks.
* Prefer single-column layouts.
* Keep tables simple; avoid merged or split cells.
* Do not convey meaning through color or shape alone.
* For images and charts: either state the same information in body text, or provide alt text.
* Avoid images of text (screen readers cannot parse them).
* Check color contrast: <https://gka.github.io/palettes/>

## References

**Style**: APA 7th Edition. Add page numbers when citing a specific claim, even without a direct quote.

Full examples: <https://apastyle.apa.org/style-grammar-guidelines/references/examples>

## Dispute Arbiters

* &#x20;Spelling: Merriam-Webster — <https://www.merriam-webster.com/>
* Style: APA Style Guide — <https://apastyle.apa.org/>

<br>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://research.ambitiousimpact.com/other/style-guide.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.