This document codifies the quality bar for the PaulMaxwell.dev wiki. Read before writing any content. Use the self-review checklist before declaring a page done.

The non-negotiables

Reference voice, never edification. The wiki is an encyclopedia. Third-person, descriptive, scholarly. Never address the reader ("For anyone working on X", "if you're leaving religion...", "this is useful for your career"). Never label content with what it does for the reader ("Hook", "Takeaway", "What this means for you"). Never use second person.

Section headings are descriptive, not on-the-nose. Use "Introduction", "Founding moment", "Core doctrines", "Reception", "Internal debates". Never use "Hook", "Why it matters", "The big idea". The headings should be what an academic reference would call them, not what a marketer would call them.

No reader-addressing tags anywhere. Strip "For Career:", "For Deconversion:", "For Philosophy:", "For practitioners:", "For anyone working on X". These break the reference voice instantly.

Prose discipline

Ban filler modifiers. Strike all instances of these unless they carry real information:

• substantial / substantially (the worst offender — it almost never adds meaning)
• significant / significantly (usually filler)
• very, really, quite, rather, somewhat
• clearly, obviously, of course, naturally
• in many ways, in some sense, in a way

If removing the word changes nothing about the meaning, the word should not be there. Substantially developed means developed. Significant influence means influence. A substantial body of work means a body of work (or, if there's actually a quantitative claim, name the size: over forty volumes, a thirty-year corpus).

Prefer concrete to abstract. Instead of substantially shaped subsequent philosophy, write shaped the Vienna Circle and the early analytic tradition. Instead of substantial influence, write influenced Kant, Hegel, and the German Idealists. Specificity is what makes a reference page useful and what makes it rank in search.

Use verbs, not noun phrases. Produced the development of → developed. Made a contribution to → contributed to. Engaged in critique of → criticized. Every nominalization is an opportunity to shorten.

Avoid hedging that contributes nothing. Can be seen as, might be considered, in some sense, to some extent. If the claim needs hedging because it's contested, hedge with substance: The standard reading treats X as Y; resolute readings (Diamond, Conant) argue instead that... If it doesn't need hedging, just make the claim.

Don't repeat the title in the opening sentence. Start with the substantive claim, not with X is the figure who... repeated for every page.

No throat-clearing. It is important to note that, one might say that, it should be observed that — cut all of it.

Structural requirements

Pillar concepts: 2,000–3,500 words. Required sections: Introduction (or The problem it answers), Core claim/doctrines, History in one paragraph, body sections specific to the concept, Common confusions, Live debates, Contemporary engagement, Further reading.

Satellite concepts: 1,200–1,800 words. Required sections: Definition, Problem/origin, Core thesis, body sections, Common confusions, Contemporary engagement, Further reading.

Traditions: 3,000–4,500 words. Required sections: Introduction, Founding moment, Core doctrines, Major figures, Major texts, Internal tensions and rival schools, Legacy, Internal debates within the tradition, Texts and transmission.

Figures: 2,500–3,500 words. Required sections: Introduction, Life, The problem he/she worked on, Contributions (with subsections), Key works, Influences and influenced, Reception, Continuing engagement, Further reading.

Publications: 1,800–2,500 words for secondary, 2,500–3,500 for canonical. Required sections: Introduction, Composition and publication, Central doctrines (with subsections), Reception, Place in the wiki, Further reading.

Every page ends with Further reading — 4–7 internal wiki links to related Pillar concepts, key figures, founding publications, and the parent Tradition. Each link annotated with one phrase explaining the relation.

Every page ends with a one-line italic summary under the closing horizontal rule.

Scholarship requirements

Name living scholars, name critical editions, name journals. Every page should anchor the contemporary engagement in actual people doing the work now — not just "contemporary scholarship" in the abstract but Robert Pippin on Hegel, Cheryl Misak on Peirce, Dan Zahavi on Husserl. Name the standard editions (Leonine Aquinas, Pléiade Sartre, Husserliana). Name the journals (Mind, Hegel Bulletin, Husserl Studies).

Dates are non-negotiable. Every figure has birth/death years; every publication has a year; every founding moment has a year. Around the eighteenth century is not acceptable.

Internal debates are required for pillar pages. Any tradition or pillar concept worth writing about has live scholarly disputes. Name them, name the disputants, identify what's at stake.

No invented quotes, no fabricated attributions. If a figure didn't say it in this form, don't put it in quotes. If a doctrine isn't theirs, don't attribute it. Wittgenstein didn't precisely formulate Ockham's razor; say so.

SEO requirements

Crosslinks everywhere. First mention of any wiki entity (Figure, Concept, Publication, Tradition) gets a link. Subsequent mentions in the same page don't need to repeat the link.

Slug discipline. Lowercase, hyphenated, no leading articles, no diacritics. Critique of Pure Reason → critique-of-pure-reason. Søren Kierkegaard → kierkegaard (figures use last name only unless ambiguous).

Hook field (database property) is the SEO meta description. First sentence under 160 characters. Specific, substantive, no marketing language. This is the snippet Google shows.

Summary field is a one-line thesis. What the thing is and why it matters in one sentence.

Self-review checklist

Before declaring any page done, walk this list:

1. Substantial check. Search the page for substantial and substantially. For each occurrence, ask: does removing this word change the meaning? If no, remove it. If yes, often a more precise word exists.
2. Filler check. Same for significant, significantly, very, really, clearly, obviously, in many ways.
3. Reader-addressing check. Any second-person (you, your)? Any "For X:" headings or sentences? Any if you're working on X? Strip all of it.
4. Specificity check. Are claims about influence grounded in named people? Are dates present? Are critical editions named?
5. Scholarship check. Does the contemporary engagement section name at least three living scholars and at least one journal?
6. Crosslink check. Does the first mention of every wiki entity have a link? Are all referenced traditions, figures, concepts, publications real (no broken links)?
7. Length check. Does the page meet the word-count band for its tier?
8. Voice check. Read the opening paragraph aloud. Does it sound like Britannica, the Stanford Encyclopedia of Philosophy, or a Cambridge Companion? If it sounds like marketing copy, rewrite.
9. Further reading check. Are there 4–7 internal links at the end, each annotated?
10. Closing italic check. Is there a one-line italic summary under the final rule?

What the user actually said (verbatim, for reference)

• "the wiki should be for the purpose of reference not edification"
• "it's important not to call it a 'hook' in the text itself as this is on the nose and tells the reader we are 'hooking' them"
• "the quality is clearly dipping here from a length / academic rigor perspective"
• "i want this to be SEO GOLD"
• "ensure quality doesnt drop"
• "make sure we are standing on solid ground here before we move forward"
• "create quality standard based on critiques you think i would make"

The through-line: encyclopedic, scholarly, specific, no marketing voice, no filler.

Quality bar for the PaulMaxwell.dev wiki. Read before writing. Walk the checklist before declaring done.

101-level foundational requirement

Added 2026-05-31.

Every page is written for a reader picking up cold. The model: a curious, intelligent reader with no prior philosophical training stumbles into the page from a search result and should be able to follow it. They may not know what substance means, who Aristotle was, what a priori signifies, or why the cogito is famous. The page does not assume they do.

The rule has four operational consequences:

First, define before you use. Any technical term that is not common English-vocabulary gets either a defining clause on first appearance or a wiki link to its own page (which itself follows the 101-level rule). Never write Aquinas advances a hylomorphic account without either (a) parenthetical gloss (every material thing as a composite of matter and form) or (b) a wiki link to [Hylomorphism]. Both is best.

Second, link prerequisite dependencies explicitly. If the page genuinely requires the reader to have absorbed another concept to follow the argument, link to that concept on first appearance and write the sentence around the assumption that the reader has not read it. The page should be coherent if the link is followed or if it is skipped.

Third, the opening paragraph is the standalone snippet. It must define the page's subject in plain language before any technical move. A reader who reads only the first paragraph should come away with the right basic idea. This serves both the casual reader and AI answer engines (which truncate aggressively).

Fourth, no over-assumption of canonical familiarity. Do not write as everyone knows, Kant's transcendental turn changed everything or the obvious response to Plato's theory of Forms. Nothing is obvious to a 101 reader. State what Kant's turn was; state what the response is and why it is plausible.

The bar is: Wikipedia's accessibility, the Stanford Encyclopedia's rigor, with stronger SEO than either.

AEO, GEO, and LLM-ingestion requirements

Added 2026-05-31.

The wiki is built to compete for placement in answer engines (ChatGPT, Perplexity, Claude, Gemini, Google AI Overviews) as well as in classical search. These engines extract content differently than humans read it. The following requirements optimize for both audiences simultaneously.

Lead with the definition in the first sentence. Not the second. Not after a contextual setup. The first sentence of every page is the answer to what is X? phrased as a complete proposition. This is the snippet that gets pulled.

The first paragraph is a self-contained micro-article. A reader (or model) that reads only the first paragraph should walk away with: the definition, the discipline it belongs to, the figure most associated with it, the rough period, and why it matters. Roughly 80–140 words. No throat-clearing.

Use plain, predictable section headings. Introduction, History, Core claim, Common confusions, Live debates, Contemporary engagement, Further reading. AI parsers reward the predictable; avoid clever or oblique titles.

Cite primary sources in-line with named work and year. In Republic 514a, Plato describes the cave. Aristotle distinguishes act and potency in Metaphysics Θ (Theta). This is how answer engines determine the page is grounded; it is also what makes the page citable.

State the page's thesis in one sentence inside the first 100 words. Models reward early thesis statements; readers do too. "This entry argues that X is best understood as Y, against the more common Z reading" is the kind of move.nnUse lists when three or more comparable items appear. Numbered or bulleted; never run them as a comma-separated prose sentence at length. Both ingestion models and screen-readers parse lists more reliably.nnAnchor with proper nouns, not pronouns. Where ambiguity is possible, repeat the name (Augustine not he) so a model extracting the sentence in isolation still knows the subject. Slight stylistic redundancy is cheap; lost extraction is expensive.nnNo emojis, no decorative characters, no centered text. These confuse parsers and don't survive plain-text extraction.nnHeadings in canonical order. Per-page heading order should match the tier's template in the Operations Manual. AI models trained on similar reference corpora (Wikipedia, SEP) extract more reliably when the structure matches.nnEvery page must be self-coherent without JavaScript. super.so renders the Notion DOM server-side, but avoid features that don't render in static HTML (synced blocks, embeds, toggles for critical content).nnThe llms.txt source page must be updated every time a new Tradition, canonical Publication, or Pillar Concept moves to Published. The source page lives at 🤖 llms.txt (source) under the wiki hub.nn---nnQuality bar updated 2026-05-31 to include 101-level foundational requirement and AEO/GEO/LLM-ingestion section. Read both before writing or editing.