Sixty-six of the hundred and five documents in the Hanumanic Strategy corpus are built the same way: a roster of items, and every item filled out against the same set of labelled fields.1
⚑ Not an argument developed across paragraphs. A table, printed as prose. ⭐ And once you see it, the corpus's two documented defects stop looking like lapses of care and start looking like properties of particular columns — which makes them predictable, and makes the whole corpus readable at a glance.
Counted mechanically, not impressionistically.1 A document qualifies if any single labelled field is repeated three or more times inside it — the signature of a schema being filled rather than a point being made.
⚑ Sixty-six of a hundred and five. Nearly two-thirds.
The most-used labels across the whole corpus, with occurrence counts: Mantra 66 · Consciousness Signature 60 · Applications 60 · Purpose 41 · Application 36 · Duration 30 · Integration 28 · Nyāsa 25 · Hanumanic Principle 24 · Best for 20 · Core Insight 17 · Modern Application 16 · Why It's High Value 15 · Advanced Technique 15.1
⭐ The word Practice: alone appears as a labelled field in thirty-two separate documents.
⚠ Some of that is one roster inflating a count — a single directory of masters supplies all sixty Consciousness Signature entries. ⚑ But Purpose, Application, Duration and Practice are spread across eight to thirty-two documents each, which is a habit rather than an artefact.
⚑⚑ This is a fact about how the corpus was made and it explains more than any observation about its content.
A document is drafted by choosing a roster — eight powers, sixty masters, twenty visualisations, fifteen tools, eighteen tiers, five paradigms — then choosing three to five fields, then filling the grid. ⭐ The intellectual work happens twice: once when the roster is chosen and once when the schema is chosen. After that the document writes itself.
⚠ Which is why the corpus can produce twenty iterations of a construct without running out of things to say, and why its lists come in suspiciously regular lengths.2 A grid does not get tired and it does not admit that a cell has nothing in it.
⚑ The method has real virtues and they should be stated before the criticism. ⭐ Fixed fields make a roster searchable, comparable and extensible; they force the author to say the same kinds of thing about every item, which is exactly what a reader needs and what discursive treatment rarely delivers. The corpus's most useful artefacts are all grids.
⭐⭐ Now the finding that makes the observation worth having: the trustworthiness of this corpus varies by column, and it varies the same way in every document.
The procedural fields hold up. Duration, Repetitions, Practice, Implementation, Nyāsa, Best for — counts, minute markers, step sequences, placements, indications. ⚑ Where this build has checked these against the documents they came from, they are specific, internally consistent and usually recoverable in full.3
⚑⚑ The reason is structural rather than moral. ⭐ A procedural field can only be filled by someone who has decided what to do. There is no way to write fifteen to twenty minutes without committing to a design, and a design can be wrong in ways the author would notice.
⚠ These columns are also where this build's pages get almost all of their content, which is worth saying plainly: the corpus is a good source read column-wise, and this is the column to read.
⛔ The fields headed Traditional Basis, Ancient Definition, Traditional Foundation, Traditional Technology and Archetypal Framework are where the corpus's documented quotation problem lives.4
⚑ This build has established that sentences presented in quotation marks and attributed to the source volume routinely cannot be located in it. ⭐ What the field structure adds is where to expect it. ⚠ The failure is not distributed evenly through the prose; it concentrates in the column whose job is to supply an ancient warrant for a modern practice.
⚑⚑ And again the reason is structural. A schema with a Traditional Basis row demands a traditional basis for every item, including the items that do not have one. ⚠ The author does not decide to fabricate; the grid has an empty cell and the cell must be filled.
⭐ Which yields a reading rule with real teeth: in this corpus, treat any traditional-warrant field as unverified by default, and every procedural field beside it as probably sound. The two can sit in the same entry, three lines apart, at completely different levels of reliability.
⛔ The same holds, harder, for the fields headed Measurable Outcome, Neurological Impact, Evidence of Effectiveness and Why It's High Value.
A tier framework promises a "reduced time-to-insight… by 30% within first month." A toolkit attaches a neurological consequence to each of eight practices — prefrontal strengthening, reduced amygdala reactivity, desensitised fear response. A value proposition promises revenue multiples.5 🚩 None carries a source, a baseline or a method.
⚑⚑ The pattern is not that the author exaggerates when excited. It is that a column headed Measurable Outcome cannot be left blank, and the honest entry — unknown — is not a permitted value in a grid designed to demonstrate a system's worth.
⭐ This is a strictly finer instrument than the build's existing register rule. ⚑ That rule says reliability tracks the register a document is written in and can be predicted from its title.6 This says reliability tracks the field, which means a single document can be trusted and distrusted at once, row by row. ⚠ Offered as an extension of the register rule and consistent with it, not as a replacement.
⭐⭐ And here the pattern reverses, which is the strongest evidence that it is a pattern about fields rather than about the author.
Nine documents carry a Potential Drawbacks or equivalent field.1 ⚑ This build has already established that these blocks are unexpectedly good — specific, self-damaging, naming real failure modes nobody asked the author to name, including one graded contraindication set whose indicators are all observable.7
⚑⚑ So the same compositional habit that manufactures fabricated outcomes also manufactures unusual candour, and the difference is what the field asks for. ⭐ *A drawbacks field asks how could this fail?, and that question can be answered honestly by someone who does not know the answer to does this work?* An outcome field asks for a result, and a result cannot be invented honestly at all.
⭐ Which gives the general rule, and it is the page's real content: a mandatory field is safe when it can be filled truthfully by someone who lacks the evidence, and dangerous when it cannot.
⚑ The last question is why a corpus with this author's evident capability composes almost entirely in grids.
⭐ Because a grid is the only form that survives twenty iterations. ⚠ An argument developed across paragraphs cannot be extended without being revised; a roster can always take another row, and a schema can always take another roster. ⚑⚑ The fixed-field entry is the compositional unit that makes an indefinitely iterating corpus possible, and the corpus iterates indefinitely.
⚠ The cost is that the corpus has very few arguments in it. ⭐ Its findings are almost all comparisons across a grid — this master gets a higher dose than that one, this tier sells at a higher price — and comparisons are not the same as reasons. ⚑ The build's own strongest findings from this material have consistently come from reading a grid's shape rather than its contents, because the shape is where the author's thinking is.
Choose the schema deliberately, and know that you are choosing the document. ⭐ Whatever fields you pick will be filled for every item, including the items that have nothing to put there.
Never include a field that cannot be honestly left empty. ⛔ If your grid has a Measurable Outcome row and no measurements, the row will be filled anyway. Cut it or rename it to something answerable — What Would Count as Working is a field an honest author can complete.
Do include a drawbacks field. ⚑ It is answerable without evidence, it produces the most candid material in this corpus, and it costs a paragraph.
Read grids by column, not by document. ⚠ A single entry can carry a trustworthy duration and a fabricated warrant three lines apart. Reliability is a property of the field, not of the author's mood that day.
And write at least one thing that is not a grid. ⚑ A schema will let you produce indefinitely without ever making a claim that could be wrong. That is comfortable, and it is why the corpus contains twenty iterations and few arguments.
Source. The whole extension folder, 105 documents, examined mechanically at the phase-10b sweep 2026-08-19.1 personal-notes. [EXTENSION].
Method, stated so the count can be reproduced or refuted. *Each document was scanned for labelled fields of the form Capitalised Phrase:, and a document was counted if any single label recurred three or more times within it.* Result: 66 of 105. ⚠ The threshold of three is a judgement; at two the count would be higher and at five lower. ⚑ The occurrence figures for individual labels are raw counts across the whole folder and are not de-duplicated by document.
⚠ The column-reliability claim is an inference over this build's existing findings, not a new audit. The attribution failures, the manufactured numbers and the quality of the drawback blocks were each established separately and are recorded in the source stub.457 What this page adds is that all three sort by field, and that claim has not been tested against a held-out sample.
⛔ The test that would settle it, and it is cheap: take the documents this build has not yet drawn pages from, predict from the field labels alone which rows will verify and which will not, then check. ⚑ A prediction made before reading the cell contents is the only version of this claim worth keeping.
Open question. ⚠ Is the grid habit the author's, or the medium's? Several of these documents read as generated in dialogue with an assistant, and structured output is what that medium produces by default — which would make the compositional signature a fact about how the corpus was written rather than about how its author thinks.
Second open question. ⚑ Do the corpus's few non-grid documents behave differently? The commentary-based solopreneur document, the best-cited thing in the folder, is one of them.8 If the non-grid documents are systematically better sourced, the relationship between form and rigour is stronger than this page claims.
⚑ The author's honesty and his fabrication come out of the same habit, and no amount of care would separate them.
⭐ This is the tension worth stating carefully, because it is easy to read as an accusation and is not one. ⚑⚑ Nothing in the corpus suggests an author trying to deceive anyone. What it suggests is an author who builds grids, and a grid extracts a value for every cell whether or not one exists. ⚠ The Potential Drawbacks column and the Measurable Outcome column are filled by the same person on the same afternoon with the same intent, and one comes out admirably and the other comes out invented.
⭐ The convergence is that the author is at his best where the field forces a decision rather than a claim. ⚑ Durations, sequences, placements, dosages, indications, drawbacks — all fields that ask what did you decide? *Warrants and outcomes ask what is true?, and he does not have that information for most of what he is describing.*
⚠ He never separates the two kinds of field, and the corpus prints them in the same table with the same authority. ⚑⚑ A reader with no external knowledge cannot tell which rows are design and which are assertion — and the corpus's whole ambition is a book, which is to say a reader with no external knowledge.
The Anti-Whitewashing Framework and Its One Exemption. ⚑ The same author, the same compositional method, and the opposite result — a roster of historical figures where every entry carries a mandatory Failures line: Marcus Aurelius given Commodus and the persecutions, Saladin given the failure to expel the Crusaders, Lincoln given habeas corpus.
⚑⚑ The pairing supplies the mechanism this page needs and could not get from the corpus's failures alone. ⭐ That roster is trustworthy because of its schema, not despite it. A mandatory Failures column forces a truthful entry from an author who would otherwise have written a hagiography — the grid did the work that the author's enthusiasm would have undone.
⚠ So the fixed-field method is not a defect to be designed out. ⭐ It is a lever, and its direction is set entirely by whether a given field can be honestly completed by someone who does not have the answer. ⚑ Failures can. Measurable Outcome cannot. Same author, same corpus, same fortnight — and the difference in reliability is a property of two column headings.
The Experiments That Pre-Register Failure. ⚑ The corpus's own repair, arrived at from another direction: state what would count as failure before running the test.
⭐ Read as a field-design rule, that is exactly the fix for the outcome column. ⚑⚑ Replace Measurable Outcome with what result would falsify this, and the cell becomes answerable by an author with no evidence — because a falsification condition is a decision, and decisions are the class of thing this author fills in reliably. ⚠ The corpus has the repair in one document and the defect in a dozen, and never connects them.
⚑ A compositional habit that predicts a source's reliability, column by column.
🧭 The first open boundary: this instrument is not about this corpus. ⚠ Any structured source — a practitioner manual, a curriculum, a product catalogue, a set of case studies — sorts the same way, and the question which of these columns could be filled honestly by someone who did not know? can be asked of all of them. ⭐ The vault holds several fixed-field corpora already, and none has been read this way.
🧭 The second, and it points at the medium: if the grid habit comes from composing in dialogue with an assistant, then a great deal of contemporary practitioner writing has the same signature and the same predictable failure column. ⚑⚑ That would make the reading rule far more valuable than a fact about one author's corpus — and it is checkable against any document set whose provenance is known.
🧭 The third is the sharpest and it cuts at the build. ⭐ If the corpus's thinking lives in its shapes rather than its contents — which roster, which fields, in what order — then a research base that extracts contents is capturing the wrong layer. ⚠ This build's best pages have all been about shapes, and none of them says so. 🧭 Nobody has asked whether the right unit of extraction from a grid-composed source is the entry at all, or the schema.