74:30 PROJECT
Part 7 of 17MethodTransparencyJune 20263 min read

The Discovery Framework: Every Adjustment, and Why

A numerical claim is only as honest as its disclosures. Here is every adjustment the project makes to the count, why it was made, and the scholars who debated the same point long before any computer did.


The fastest way to fool yourself with numbers and scripture is to keep quietly adjusting what you count until a pattern appears. The only real defense is to disclose every choice, rank it by how contested it is, and publish the method so anyone can change a choice and watch what happens. This is the full list. Nothing here is held back.

The text is fixed


The standard Uthmani text is used throughout. Nothing is added and nothing is removed. This is the first rule and it does not bend: if a result ever required editing the Quran, the result is thrown out, not the Quran. That single rule is what separates this from the work that came before it.

The letter groups


The disconnected letters open twenty-nine chapters and fall into thirteen groups by their shared initials. Eight of those thirteen groups require no choices at all. You count the letters as they stand and the totals are already divisible by nineteen. There is nothing to disclose about these eight because there is nothing to decide.

The five parameterized groups


The remaining five groups depend on one disclosed parameter from the Uthmani manuscript tradition, a documented question about how certain letters are counted. This is the weakest assumption in the project and it is labeled as the weakest assumption, openly, every time it comes up. Reject all five of these groups and you still keep the eight clean groups, the independent word count, and the book-level totals, all divisible by nineteen.

Verse boundaries


In four chapters the project follows a recognized verse-boundary convention. The regional counting traditions, Kufan, Basran, Madani, and others, have always divided a small number of verses at slightly different points. This is centuries old and fully documented. No content is added or removed by the choice. It affects only where one verse is judged to end and the next to begin.

The Madinan and Meccan layer


The verse-level Meccan and Madinan classification uses al-Suyuti's al-Itqan for the set of disputed chapters and the classical exception-verse ranges recorded by al-Zamakhshari and others. The partition the project uses agrees with the scholarly majority on eleven of the twelve disputed chapters. This is the most assumption-heavy layer and it is ranked last for exactly that reason.

Why each adjustment is legitimate


None of these choices was invented to chase the number nineteen. Every one of them is a point that classical scholars themselves debated, in writing, long before a computer was pointed at the text. The project did not decide where the verses divide, or which chapters are disputed, or which exception ranges exist. The tradition decided all of that. The project only asks a narrow question: when you adopt one documented, scholarly position over another, what happens to the arithmetic.

Ranked, not buried


Every choice is ranked by how contested it is, from the eight groups that need no choice at all to the Meccan and Madinan layer that needs the most. The weakest assumption is never disguised as a strong one. That ranking is the honesty of the project made visible. Trust, but verify: the code is published, so you can overturn any single choice yourself and see exactly what it costs the result.

Next in the seriesHow the Lock Was Found →

A question, a correction, or something to add? The project would be glad to hear from you. Get in touch.