Zhihe GrowthTraceable evidence is not automatically true, but missing provenance makes correction difficult. On a bilingual website, one incorrect specification may spread across long articles, FAQs, structured data and English pages. Source management must include those derivations.
Separate sources, activities and responsibility
W3C PROV provides concepts for entities, activities and agents. A manual version can be a source entity; extraction or translation can be an activity; an editorial role can carry responsibility. Applying these concepts does not require claiming an implemented graph database.
| Element | Synthetic example | Question answered |
|---|---|---|
| Source entity | D1, AX-220 manual v1 | Which material supports the fact? |
| Derived entity | voltage_v=220 | What was extracted? |
| Activity | Extract and normalize a unit field | What transformation occurred? |
| Responsibility record | Editorial review reference | Who reviewed the transformation? |
| Output location | Chinese, English and JSON-LD fields | What must be checked after a correction? |
Do not invent reviewer names to populate a field. The lab is author-created and author-reviewed, not independently audited. Real projects can retain internal responsibility records while disclosing only authorized information.
Hashes and retrieval dates are insufficient
A content hash can detect a changed file, not whether the change is correct. Retrieval time says when material was obtained, not when its facts became effective. Downloading an old manual again should not make its specifications appear newly updated.
One URL can serve replacement files, and one file can contain several product versions. Retain source identity, version, retrieval time, applicable entity and a location within the material. High-risk facts need original evidence and review rather than only a generated summary.
Constraints address a different problem
SHACL expresses constraints over RDF graphs. JSON records can use JSON Schema. Neither is a search-engine endorsement. Choose tools for the actual data representation instead of adopting a knowledge-graph label before defining the problem.
This package implements JSON records and a JSON Schema. It does not implement a SHACL engine. A false number with the right type can still pass, so compare approved values with sources separately. Describe implemented checks rather than listing standards as if they were all deployed capabilities.
Handle a changed fact through its dependencies
Suppose AX-220's approved source becomes v2 while the English page still refers to v1. Flag dependencies for review, then inspect what changed. A layout correction should not automatically alter specifications. A changed usage restriction requires review of product text, excerpts, FAQs and translated explanations.
source D1@v1 -> fact F-supply -> zh paragraph
-> en paragraph
-> structured field
new version -> review dependencies -> approve or withdraw
This illustrates a recommended relationship model. It does not claim that the current website automatically withdraws all dependent content. The downloadable bilingual checker detects differences in specified fields; a full production dependency graph requires additional implementation.
Inspect reproducibility and failure records
The dataset includes evidence IDs, versions and four annotated claims. The output records input hashes and validation results; code and dependencies are in the bundle. Hashes identify the synthetic inputs used, not the truth of customer data.
Distinguish an inaccessible link, an obsolete version, a source that does not support a claim and withdrawn disclosure permission. They require different actions: restore access, update the fact, revise the conclusion or withdraw publication. None should automatically be diagnosed as insufficient website authority.
Test provenance with a withdrawal exercise
Mark D1 as awaiting review, list its direct facts, then locate every affected paragraph, table, short answer and English counterpart. Knowing that “many pages used the manual” is insufficient. A small project can maintain this relationship in a table; a graph database is not a prerequisite.
Record the trigger, affected facts, public locations, temporary action and verification. A broken link does not necessarily invalidate a fact if an authorized original is retained, though public evidence access still needs repair. Conversely, a reachable new source that contradicts the old fact requires correction. Accessibility and validity are different checks.
Keep old versions for internal audit, not as unlabeled current specifications. Historical cases need an explicit time scope. A new manual does not justify refreshing every article's date: change the outputs affected by real facts. The downloadable hash identifies an experiment input, not an implemented dependency-query or withdrawal system. A controlled version change that leads to concrete, verified output corrections is the appropriate acceptance exercise.
Why Zhihe Growth needs this layer
For Chinese exporters maintaining multiple language versions, copied facts can lose their update relationships. Zhihe Growth can demonstrate professional practice through accessible evidence, explicit versions and correction paths. Cooperation history and patent application records should not become unsupported performance guarantees.
Continue with SSOT validation, entity identity, citation support and the editorial policy. Provenance serves explainable, correctable facts, not merely a larger number of links.