Zhihe GrowthTrack facts separately from pages
A fact may appear on many pages; one page may depend on many facts. Use stable fact and page identifiers, with references to exact fact versions. File timestamps alone can miss copied dependencies and misclassify styling changes as factual revisions.
A translation needs a translated-from source version, not simply a “translated” checkbox. It may remain fluent after its source changes while becoming incorrect. Mark it for review instead of carrying forward approval from an older version.
A minimal executable readiness condition
The teaching function requires source version equality and an approval flag. Version two translated from version two and approved passes; version two translated from version one fails. This demonstrates a version gate, not reviewer authentication or semantic validation.
{
"fact_id": "demo-capacity",
"version": 2,
"en_source_version": 1,
"approved": true,
"expected_ready": false
}
Previous approval does not cover changed content. A production workflow also requires authorization, persistent records and audit history; a Boolean field is not a complete approval system.
Classify changes by their consequences
| Change | Review | Avoid |
|---|---|---|
| 500 mL becomes 750 mL | Text, tables, Schema, translations | Updating one occurrence only |
| New restriction | Negation and recommendation scope | Retaining unconditional wording |
| Expired certificate | Status, validity, dependent pages | Assuming continued validity |
| Brand terminology | Entity and aliases | Renaming the legal entity |
| CSS spacing | Visual regression | Restamping all publication dates |
A short edit can have a large semantic impact. Adding “not” can matter more than rewriting a background paragraph, so character-difference size is not an adequate review criterion.
Build an auditable synchronization process
Register the source change, identify affected pages, prepare translation differences, check protected fields, review meaning, approve the current version, package it and verify public output. Record input versions and artifact hashes at each step. Failure should leave the workflow in an explicit state; saved is not published.
Review dependent FAQs and evidence summaries without copying whole technical articles into short answers. Preserve concise conclusions and meaningful links. Withdrawal of a fact needs a downstream withdrawal or correction plan, not just deletion of its source file.
Coordinate publication according to risk
Corrections involving safety, certification or purchasing limitations should prevent stale translations from continuing to mislead. Coordinate bilingual release or deliberately mark or remove affected content while it is repaired. Do not indiscriminately noindex an entire language section.
Stylistic improvements can be staged with clear status. Preserve original publication dates and use genuine modification dates. Sitemap lastmod values should not change across every page merely because a build ran.
Zhihe Growth's public fact controls
Zhihe Growth's brand, legal entity, case figures and patent-application status belong in protected records. SuperPDR 17% and ELEREIN 15% retain their approved historical-case meanings. Permission to identify a partner does not establish an unconfirmed cooperation scope.
The example is not an installed WordPress synchronization plugin. It provides executable rules for the workflow model and publication checks. Real integration needs separately tested permissions, storage, conflicts and rollback.
Synchronization exercise: one corrected specification
Suppose a new source corrects AX220 from 20 L to 18 L. This hypothetical does not change the package's frozen 20 L fixture. Create a new fact version, then inspect dependencies.
| Asset | Review | Approval condition |
|---|---|---|
| Chinese text | Value, unit, model | New evidence checked |
| English table | Correct row and 18 L | Bound to new source |
| Short FAQ | Old 20 L conclusion | Updated concise answer |
| Schema | Property and body | No stale field |
| Historical or current use | Explicit version role | |
| Experiment report | Frozen old dataset | Do not rewrite history |
Do not replace every historical “20” with “18.” Preserve old experiment inputs while correcting current commercial claims. Confusing those purposes damages both accuracy and reproducibility.
Materials and references
Download the version and approval fixtures. W3C PROV provides a framework for provenance and responsibility; Google's localization guidance addresses page relationships. Synchronization maintains facts, not guaranteed crawling or citations.