The corpus keeps a footnote — number 518 — which says the stages it spends six hundred pages describing are false stages, and names three jobs for the whole apparatus: rest stops, verifications, motivational assists.
Every page in this vault that touches a stage cites it. There is a standing rule that they must. The sentence they all carry is some version of: and the standing scope limit — the ladder being used here is one the author himself calls conventional.
Then the page proceeds to use the ladder for everything it was about to use it for.
[RESONANCE] The disclosure changes nothing downstream, and that is the whole observation.
This vault runs the same instrument on itself. Every web-sourced claim carries [VERIFIED], [PLAUSIBLE — needs corroboration], [CONTESTED] or [LOW CONFIDENCE]. Every build-authored finding carries [n=1 OBSERVED], [n=2 SUGGESTIVE] or [n≥3 PATTERN]. The tags are honest, they are applied conscientiously, and — here is the uncomfortable part — almost nothing in the vault behaves differently depending on which tag a claim carries.
A [PLAUSIBLE] claim gets cited by the next page exactly the way a [VERIFIED] one does. An [n=2 SUGGESTIVE] finding gets referenced downstream in the same register as an [n≥3] one. The tag travels with the sentence and the sentence travels regardless.
The mechanism is worth naming because it is not laziness.
A disclosure is a claim about a claim. Reading is linear and shallow: the reader takes the object-level sentence and drops the meta-level qualifier, because the qualifier has no content of its own to remember. Nobody recalls "and that was a two-instance finding." They recall the finding.
Same shape elsewhere:
[n≥5] — the author's own reading printed inside a quoted sentence, in visible square brackets. Disclosed, and it still works, because by the closing bracket you have heard the argument in the quoted author's voice.The general shape: a disclosure that costs the discloser nothing and requires the reader to do the work will be paid attention by neither.
Against this vault's own method. The evidence tags exist so that a small sample cannot masquerade as a regularity. The Shiva Purana build's collapsed compound signature is the case study — the observation was fine and the language was the defect. The tags were the fix.
But the fix assumes the tag governs downstream use. If it doesn't, then the tags are doing something narrower than intended: they discipline the writing of a finding and not its travel.
Promotion criterion, and it is checkable: take five [n=2 SUGGESTIVE] findings from the archive and trace every downstream citation. If the citing pages restate them at the same confidence as [n≥3] findings, the tag is a writing convention rather than an epistemic instrument — and the vault needs a mechanism with teeth, most obviously a rule that a sub-n=3 finding may not be cited as a premise, only as an open question.
[n=1 OBSERVED]. One corpus's footnote-518 pattern is the only instance actually examined here.
Next action: the downstream-citation trace described above. Five findings is an afternoon and it decides whether the tag system needs a rule attached to it or is fine as it stands.