Zhihe GrowthVersion content and interpretation together
Question text, labels, relevance definitions, filters, source revisions and scoring rules all affect results. A dataset release needs file hashes and an explanation of additions, removals, corrections and changed definitions.
Do not overwrite labels under the same version and leave old reports impossible to reproduce. Maintain an internal audit of withdrawn or expired records while respecting disclosure limits. Reproducibility is not permission to preserve client secrets in a public archive.
Distinguish four material classes
| Class | Required check | Publication approach |
|---|---|---|
| Authored synthetic data | Could it be mistaken for client facts? | Label its origin and license |
| Client submissions | Project scope and authorized use | Exclude from public packages by default |
| Public third-party pages | Attribution, copyright and validity | Do not assume full redistribution rights |
| Human labels | Standards, reviewer privacy and permissions | Publish only permitted fields |
Browser accessibility does not establish a right to redistribute an entire page. Permission to name a brand does not authorize contracts, credentials, personal details or complete private conversations. Record permitted fields and purposes separately.
Executed allowlist behavior
The fixture contains identifiers, a claim, license, expiry and a fictional example.invalid email. public_record outputs only four approved fields, requiring public status, no withdrawal, CC0-1.0 and an unexpired date. Withdrawn and expired variants return null.
The deliberately narrow rule accepts the teaching fixture's license; it is not a general licensing engine. Other licenses need explicit policies rather than relabeling everything CC0. Removing the email demonstrates an allowlist, not automatic detection of personal information inside free text.
Propagate withdrawal and validity changes
A fact reused across pages and languages needs downstream tracking. Determine whether a withdrawal concerns new use, public attachments, existing claims or all three. Preserve responsibility and version records, then verify pages and caches.
Expiry does not always make a historical report false, but an expired qualification cannot be presented as currently valid. Separate historical archives from current assertions. The example rejects expired records conservatively; real policies require explicit business and authorization rules.
Inspect archives separately from logs
Package only an explicit allowlist. Exclude workspace secrets, environment files, model caches, databases and SSH material. Retain model revisions and parameters without download tokens. Minimize logs before writing rather than relying solely on later secret searches.
A ZIP needs a manifest, data card and reproduction instructions. Being readable or matching a hash does not prove permission to publish; technical integrity and authorization are separate gates.
Zhihe Growth's data boundary
Authorized brand names and confirmed figures may appear in public cases, but client records should not leak into teaching experiments. This package uses synthetic products, questions, permissions and inquiry records, plus blank templates. SuperPDR and ELEREIN historical cases remain separate.
This distinction protects clients and identifies what derives from executed code versus service history. Cooperation, implementation and commercial outcomes need different evidence. A future real-data benchmark needs its own license and annotation review rather than inheriting this synthetic package's claims.
Pre-export review example
| Item | Default | Evidence to change it | Review focus |
|---|---|---|---|
| Synthetic specifications | Public | Authorship and license | Not client models |
| Client contacts | Exclude | Specific permitted purpose | Minimal fields and retention |
| Contract | Exclude | Explicit disclosure right | No recursive inclusion |
| Model revision | Record | Actual execution | No access token |
| Reviewer name | Private ID | Approved public identity | Preserve auditability |
| Full third-party article | No assumed redistribution | License or permission | Link versus copied text |
| Withdrawn record | Stop export | New explicit authorization | Existing copies |
Internal readability does not authorize public release. Export permissions depend on purpose, not database read access. Mixed-permission files need reviewed extracts or exclusion. Record when permission was checked; later withdrawal or scope changes require regeneration and downstream review.
Materials and reference
Deleting a server copy cannot guarantee removal of copies already downloaded elsewhere. Minimize and review before release, and describe withdrawal limits honestly rather than promising to recover every internet copy.
Download the synthetic records and allowlist check. W3C PROV supports provenance modeling. Read the public teaching benchmark and fact provenance guide. This engineering guidance does not replace specific permission or legal advice.