EEAT Mechanics

tofu, keto, Rhubarb: The Subchunk Refinement Signals

The codenames that stand for refinement signals at the most granular level — individual subsections of a page — and why they represent the weakest evidence in the matrix

By Thomas Wawra· Published · Version 1.0· Systems referenced: tofu / keto / Rhubarb / Subchunks

What are tofu, keto, and Rhubarb?

These codenames stand for refinement signals that fine-tune the quality estimate at a very granular level — individual subsections (subchunks) of a page. Their exact function is not fully documented in the available material, making them the weakest evidence in the entire matrix.

The names follow Google's food-based naming convention: tofu (soy), keto (dietary), Rhubarb (vegetable). This convention is used for internal systems that are not user-facing — the names are internal identifiers, not descriptive labels.

tofu, keto, and Rhubarb are fed by IS-Calibration (System 12). This means they are calibrated by human rater judgments — the same ground truth that calibrates chard and OriginalContentScore. The connection to IS-Calibration is the strongest evidence for these systems: they are part of the quality calibration chain, even if their specific function is unclear.

Claim-level evidence (3)
B
tofu, keto, Rhubarb refine quality at subchunk (subsection) level.
Source: Google API leak — system description · tofu / keto / Rhubarb / Subchunks
C
Exact function not fully documented — weakest evidence in the matrix.
Source: Evidence assessment — [B] weakest, [C] uncertain · tofu / keto / Rhubarb / Subchunks
B
Fed by IS-Calibration (S12) — part of the quality calibration chain.
Source: Google API leak — fedBy: [12] · tofu / keto / Rhubarb / Subchunks

Subchunk-level refinement

The concept of 'subchunks' is architecturally significant. A page is not evaluated as a single unit — it is divided into subsections, and each subsection is evaluated independently. A long article might have an introduction, three main sections, and a conclusion — each is a subchunk.

Subchunk-level evaluation means that a page with one excellent section and three mediocre sections will be scored differently than a page with four good sections. The subchunk scores aggregate into the page-level score, which feeds into NSR (System 7) for site-level aggregation.

The Subchunk-Deltas field measures the difference between subchunk scores. High variance between subchunks (one excellent, three poor) might signal a page that was partially generated or partially copied — the excellent subchunk was written by a human, the poor ones were generated.

Claim-level evidence (3)
B
Pages are divided into subchunks — each evaluated independently.
Source: Google API leak — subchunk architecture · tofu / keto / Rhubarb / Subchunks
B
Subchunk scores aggregate into page-level → NSR site-level.
Source: Google API leak — feedsInto: [7] · tofu / keto / Rhubarb / Subchunks
C
High Subchunk-Delta (variance between sections) may signal partial generation.
Source: Inference from delta field semantics · tofu / keto / Rhubarb / Subchunks · Subchunk-Deltas

tofu/keto in the ranking architecture

These signals are indirect for Expertise (Exp: indirect) and Trust (T: indirect). The indirect Expertise signal comes from the fact that subchunk-level refinement requires a model capable of understanding section-level quality — a more sophisticated evaluation than whole-page scoring.

The indirect Trust signal comes from the connection to IS-Calibration. If raters trust a page, the subchunk signals will reflect that trust at the section level. A section that raters rated as untrustworthy (e.g., containing unverified claims) will receive a lower subchunk score.

The weakest evidence code in the matrix is here. Unlike NavBoost ([A] DOJ, [P] patent), Panda ([P] patent, [A] DOJ), or chard ([B] leak, [O] QRG), the tofu/keto/Rhubarb signals have only [B] (existence of codenames) and [C] (function inference). No patent, no DOJ testimony, no official communication.

Claim-level evidence (3)
B
Indirect Expertise (Exp: indirect) — subchunk evaluation requires sophisticated model.
Source: Google API leak — dims: {Exp: indirekt} · tofu / keto / Rhubarb / Subchunks
B
Indirect Trust (T: indirect) — IS-Calibration ground truth flows to subchunk level.
Source: Google API leak — dims: {T: indirekt} · tofu / keto / Rhubarb / Subchunks
C
Weakest evidence in the matrix — only [B] codename + [C] inference.
Source: Evidence assessment · tofu / keto / Rhubarb / Subchunks

This Deep Dive is Schicht 2 content — interpreted and referenced, but always pointing back to Schicht 1 (the reference layer). Every claim is mapped to a source with an evidence code: [A] DOJ/sworn material, [B] leak field, [P] patent, [O] official Google communication, [C] interpretation.

© Thomas Wawra · Senior SEO Manager · wetter.com — a Funke Digital company