01The project's parts
One author, one inquiry, and the four parts of the work.
Grammar of Meaning
The inquiry — an open, bottom-up study of how humans make meaning, across religion, philosophy, and psychology. Also the name of the published essays. Field notes on how meaning gets made.
Tamara Sanderson
The byline — the author. Byline → inquiry → object: Tamara Sanderson is who · Grammar of Meaning is what she studies · the Garden is what she's building.
The Library
The world's traditions, gathered and read — the corpus and the coding underneath everything. The "engine" face of the project: where the observations and patterns actually come from.
The Essays
The published writing — one pattern at a time, on Substack (grammarofmeaning.org). The project thinking out loud, in public.
The Garden
What's being built: the interactive "digital pilgrimage" — the traditions seen as a place you walk rather than a database you query, where the rhymes light up around you. Soil below, flowers around, a constellation overhead. The destination, on a decade-scale horizon.
The Method
The open method behind the work — the bottom-up reading, the multi-model reliability check, the bias made visible, the lineage it belongs to.
02How meaning is read
The core ideas the whole project turns on.
Meaning-making
The premise: meaning isn't a thing you find or possess — it's made, a verb, in the meeting between a person and the world. So we study what traditions do, not only what they believe.
A move
The underlying gesture beneath a tradition's answer — what it does with suffering, attention, the self, or time, rather than the doctrine it states. The unit the project looks for.
A rhyme
The same move surfacing in a different voice across traditions — a structural echo. Not sameness, not borrowing: a recognizable echo (devotion to the sacred in a Buddhist sutra, a Christian epistle, a Sufi poem).
An analogy
What a rhyme gives you to carry: the same gesture held up across traditions, portable into your own life. The Islamic God is not the Christian God — but devotion to the sacred is a move you can carry across both.
Convergence / divergence
Convergence is where traditions rhyme; divergence is where each goes its own way. The divergence is where a tradition's specific wisdom lives — most of what any tradition says is its own, and that's the point. Both are shown.
Portable
Whether an observation can travel — something you could carry with you across traditions without converting. The project's question is a testable one about what's portable, not a claim that "all religions say the same thing."
Perennialism
The view that every tradition secretly says the same thing. Not what this project claims — it would erase the real differences.
Particularism
The view that every tradition is an island, with nothing carryable between them. Also not what this project claims. The work lives between the two: difference first, and rhyme where it genuinely recurs.
Tradition
A way of making meaning that the project reads in its own terms — a religion, a philosophy, or a school of psychology. 540+ are included in the corpus.
Family
A broad grouping of related traditions — e.g. Abrahamic, Dharmic, East Asian, Philosophical, Psychological, Indigenous & traditional, Ancient, Modern Spiritual, Secular. The corpus spans nine.
Sub-tradition
A finer branch within a tradition — Sufi Islam, Zen Buddhism, Advaita Vedanta. The level at which the corpus actually tags a source.
The seed
A human situation you start from — suffering, exile, the constructed self, the dread of the future. The garden gathers how each tradition answers that. (In the essays, a "seed" is the starting idea for one piece.)
03The method
How the reading is kept honest.
Bottom-up
The discipline that keeps the answer from being smuggled into the question: each tradition is read in its own vocabulary first, before any comparison. A pattern only counts if it emerges from the traditions — not from an AI's priors or the Western canon.
First-cycle coding
Labelling a passage in the tradition's own words first — a Buddhist passage in Buddhist terms, a Christian one in Christian terms — with no outside categories imported at this stage.
The reliability panel
Used when coding the corpus: the substitute for a room full of human coders a solo researcher can't afford: each judgment is put to a panel of independent AI model-cohorts, and their agreement is scored. Disagreement isn't smoothed over — it flags a shaky call.
The three chairs
The three roles the panel reads from: the insider (a member of the tradition — does this honour how it understands itself?), the outsider (a comparativist — what does it look like from outside?), and the practitioner (someone who does the practice — what does it ask of a life?).
Bias, made visible
The corpus skews toward traditions with long text-production and digitization histories. Rather than hide that behind "principled selection," the skew is documented and tracked. A bias you can see is one you can correct for; a bias you pruned away is one you've only hidden.
The lineage
The category the project belongs to — open-methodology comparative inquiry, where the corpus, coding, and tooling are all published so others can extend, audit, or contest the work. The forebears: Stewart Brand (access to tools), Diderot (encyclopedic ambition), Christopher Alexander (patterns across contexts), Donella Meadows (archetypes across domains), Vaclav Smil (vast empirical breadth — but method published, not withheld).
Q1 / Q2
The two questions the work holds at once. Q1 — what does each tradition, on its own terms, observe? Q2 — which of those observations converge across traditions, and what do the cross-tradition patterns tell us?
The commons
Why build it: a rebuilt commons for meaning-making — a shared record of how humans have made meaning, for a moment when the inherited commons has thinned. Not wellness, not one tradition: a commons.
04The machinery
The working parts a reader meets on the engine and essay pages.
The engine
The acquisition machine that fills the Library: it brings a new idea in — checks whether it's already held, searches many archives at once, pulls each source in with a full trail, splits it into passages, and codes it. What it brings in then fuels the next search — so it's an engine, not a one-way pipe.
Acquire → chunk → code
The engine's core arc: acquire the sources, chunk them into quotable passages, code each passage in its own vocabulary.
Passage
The smallest unit you could quote and stand behind — the unit of analysis. A book or recording is just a container; container-counts aren't depth.
Chunking
Splitting a whole text into passages, because a whole book is too big to compare.
L0–L4
The shallow hierarchy a text is split into. L0 — a shared canonical root (a scripture many traditions read). L1–L3 — organizational scaffolding (book → chapter → section). L4 — the quotable passage itself, the actual "atom" of analysis.
Coding
Describing a passage in its own tradition's words first, by the three-chair reliability panel — before any outside category is applied.
Coded corpus
The body of passages read and labelled in each tradition's own vocabulary — the layer meant to feed the garden. The corpus spans 545 traditions, but the coding itself is just beginning: coding is the project's current frontier.
Endpoints / archives
The many source collections the engine searches in parallel — a tradition's home-region scholarship alongside the big Western indexes, queried for what they contain, never for whose region they "belong to." 4,700+ catalogued so far.
The shopping cart
The running list of what to acquire next. Coding a new idea surfaces new terms and citations, which refill the cart, which drives the next search.
CRADLE · PRISM · FOUNDRY
The engine's internal stages, named on the engine page's "for the curious" notes. CRADLE — the acquisition pipeline (classify a request → route it → resolve it to real sources → dedupe → ingest). PRISM — tags every archive on routing axes (region, language, era, peer-review…) so the engine knows where to look. FOUNDRY — builds the individual harvesters that pull from each archive.
The essay engine
How a public essay gets made: the engine harvests and drafts from the corpus, but the human makes the essay. The engine gathers and drafts; the human makes the essay.
The voice guide
The writing guide that holds the essays' repertoire of forms — how the essays should sound.
The forms / repertoire
The structural shapes an essay can take (the Thurman flex, the Watts flex, Black-preaching principles — a small, deliberate repertoire, not a long catalogue). Choosing the form — not just the words — is a human judgment call, and the cure for the default "self-help" march.
The review panel
A simulated nine-person panel that reviews each essay adversarially — to refute it — plus the honesty rails that flag legend as legend and keep a move from being flattened across traditions.
Revision
Where the essay is actually made: not one tidy step but dozens of line-level passes (≈ 22 for the Rabiʿa essay). By a wide margin the most time-consuming part of the build.
Footnotes / verify-first
Pinning every claim to a named source before it ships — the difference between looking sourced and being sourced. Illustrative quotes are checked against the named source before publication; nothing is presented as a locked citation until it is one.
Flowers · soil · constellations
The garden's images. Flowers are the traditions; soil is the conditions that grew them (the where, when, and how-the-world-was); the constellation overhead is the convergences — the rhymes. A flower is one tradition's bloom; a constellation is a cross-tradition pattern.
Pilgrimage
The shape of the experience: not a search bar but a walk — you arrive, pick a seed, watch the rhymes light up, go deep or wide, and end in a practice you can carry out the gate.