Reading System

✍️Capture quotes

One sourced sentence at a time, not highlights

Copy quotes verbatim as you read, but split them one note per idea and tag each with author and page so you can cite later. Don't bulk-highlight — highlights are passive and you never revisit them. The discipline: right under each quote, write one line in your own words on why it matters. Months later, that single line is what makes the quote findable again.

🧵Connect themes

Link, don't file — let notes collide

Instead of filing notes into folders, link them by theme so unrelated books start talking to each other. When a new quote echoes an old one, connect them and name the link. Real insight happens here — in the friction where two sources from different fields collide. Keep one index note per theme (a Map of Content) so the web of links never loses its way.

🪄Turn into claims

A debatable sentence, not a summary

A note isn't done until its title is a complete, debatable claim — 'X causes Y', not 'thoughts on X'. This forces you to take the position the source only hinted at. The test: could a smart reader disagree? If not, it's a summary, not a claim. Every claim gets sharpened by two children — the evidence that holds it up and the strongest objection against it.

Evidence

Concrete cases, numbers, quotes that hold it up

List the strongest support for the claim — concrete data, named examples, the quotes you captured in step one. Rank them by force, not by count, and lead with the single most undeniable piece. Weak evidence dilutes strong evidence, so cut anything you'd be embarrassed to defend. Every piece must trace back to a sourced note, never to memory.

Counterpoint

Steelman the strongest objection first

Write the best version of the argument against you — steelman it, don't strawman it. A claim that survives its toughest objection is publishable; one that dodges it reads as propaganda. Either meet the counterpoint head-on, or narrow your claim until it's true. Naming the objection first also pre-empts the comment that would otherwise sink the post.

🗂️Build outline

Sequence by argument, not chronology

Arrange your claim-notes into a spine: claim → evidence → counterpoint → resolution. Order by logical force, not by the sequence you read the books in. Write each outline line as a full sentence and the draft is half-written before you touch prose. If a section has no claim-note to anchor it, it's filler — delete it.

Sections

One section, one claim — split the rest

Each section carries exactly one claim and the evidence that earns it; the moment it needs an 'and also', split it. A reader should follow your whole argument from the section headers alone. Aim for three to five sections — more than that usually means two essays fighting inside one. Open each section with its claim, not with throat-clearing.

📰Publish note

Ship over polish — feedback is the next input

Publish the note before it feels finished; the system improves through readers' replies, not through private polishing. Publishing forces a clarity that note-taking alone never does — an audience catches the hand-waving you can't see. Treat each published note as a unit you can later link, quote, and build on. The point of the pipeline isn't the essay; it's compounding a body of public, reusable thinking.

Gallery post

One shareable map of the whole argument

The shareable artifact: the finished map exported as a single visual you can post anywhere. It compresses the whole argument — claim, evidence, counterpoint — into something you can skim in ten seconds. This is the distribution layer; a good map travels further than a long essay and pulls readers back to the full note. It also becomes a reusable template for your next reading project.