The in-browser check of the retraction showcase (https://organetic.ai/showcase/retraction/) What this folder holds yuce-verify.mjs the independent checker of YuCe journals (yuce-verify 0.2.1, levels J0 to J3), one ES module of 94 KB with no dependency and no network request; it hashes with the browser's own crypto (crypto.subtle). The file is exactly the one the development session delivered after its review. It is not rebuilt and not edited: its SHA-256 below is part of the trust. Licence: Apache-2.0 (https://www.apache.org/licenses/LICENSE-2.0), stated here and on the page, not inside the file. Open source: https://github.com/OrganeticSphere/yuce/tree/71b2acf5b3135afc25551dab8ebb4d7865f24ac2/verifier (Apache-2.0); its built file verifier/yuce-verify/dist/yuce-verify.mjs has the same SHA-256 as the file here. check.js the script of the page: it reads the journal and the documents, calls the checker and shows its answer. docs.json the names of the six documents. docs/ the six documents the journal quotes from: five CC BY papers as plain text (each file keeps its header with the source and the licence) and the record file of the retracted paper (bibliographic facts only). The journal itself is beside the view: /live/retraction-run1/run.wal (SHA-256 a47fefc22d2cfc2a0f0778a87b49785d5edfd303b510e2946a5441f3868374e0). The files, by their SHA-256 (check-site compares every file of this folder with these lines) yuce-verify.mjs 27d07ff676a82c3c338db315965e12cf3520416ab0fb9dc7025e198d3c44d285 docs.json c901183d26a999e8854daf2c9bd1152736af6dedace33f130431cb600c86fbe8 docs/PMC13226197.txt ab4f2013f126545f0b946e7b96c7df5e0cffe8c7341c4841e96c2d5d4cf12d84 docs/PMC13314867.txt 083f6e5abe47970ff7705226382285eaca03983e6ddb8b585792fabfeb7b227c docs/PMC13388837.txt c14a42b1ad5672eed7e2010b677ee73f909bbfdc54db6c735fcc66d140ef0083 docs/PMC13449012.txt 220a11dcb3a93b02cb36e5e6a850bdc62ac4887b25fe3081e875b929b9add93b docs/PMC13647323.txt ef7b9c6755b5631cf2ad2cbc2f6082fb2a54934af23544282566c755143967b8 docs/retracted-metaanalysis-wang-fan-2025.txt cd148c2af35a730f41ba7fee3324ee349ae94245918f79ff2afc6a3c7233510b (the six documents are the files the run read: their SHA-256 are the ones in the run's own report) What the check does and does not do It checks that the journal is consistent with itself: well-formed frames, an unbroken chain of hashes, its checkpoints, and, with the documents, that every quote is found byte for byte in its document. Without a hash or a signed checkpoint kept elsewhere it says "authenticity not established"; the SHA-256 of the journal published on the page is that kind of hash for this file. It does not recompute what fell after the withdrawal and does not check signatures (its answer says: "Not verified: withdrawal cascade, signatures"). A quote replaced by another phrase of the same document is not seen by this check. Nothing leaves the browser: the journal and the documents are read in the page and hashed there.