Style guide

The archive should read like one voice: plain, specific, and honest about risk.

Voice

• Write for someone in their first week. Explain every term the first time, or link it to the glossary.
• Be specific. "Six wallets bought 31% in the launch block" beats "lots of insiders bought".
• Short sentences. One idea per sentence.
• No hype. No "to the moon", no price predictions, no "this will 100x".
• Say what you do not know. If a number changes often, say so and tell people where to check.

Structure

• Start with one or two sentences that say what the reader will learn.
• Use ## headings for sections. Keep sections short.
• Use lists for steps and checklists, tables for comparisons.
• End with what to do next or what to learn.

Formatting

Write in Markdown. These extras are available:

<Callout title="Check the current numbers">
Fees change. Check the source before you rely on a figure.
</Callout>

<Callout type="warn" title="Careful">
Use for anything that can lose someone money.
</Callout>

<PenNote>A short handwritten note in the margin.</PenNote>

Numbers and names

• Market caps as $40K, $1.2M. Percents as 31%.
• Contract addresses and wallets in full, in code formatting.
• Product names as the product writes them: pump.fun, PumpSwap, Axiom, DexScreener.