You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Fix 117 MediaTek, Exynos and Kirin SoC release dates - #289
Correct 117 SoC release dates with unambiguous matches on the supplied Wikipedia vendor pages. Preserve every field except release_date and source_urls, preserve slugs, and move changed-year records using git mv.
Vendor
Month/day table dates
Explicit prose dates
Quarter-start corrections
Total
Skipped
mediatek
0
0
79
79
265
samsung
0
5
30
35
128
hisilicon
0
3
0
3
59
Month/day-precise table changes: none qualified.
Explicit prose changes (8): Exynos 4212 ×2 (2011-09-29), Exynos 5250 ×2 (2011-11-30), Exynos 2200 ×1 (January 2022 represented as 2022-01-01), Kirin 9000S ×1 (2023-08-29), Kirin 9030 and 9030 Pro ×1 each (2025-11-25). These are chip announcement/introduction dates explicitly named in page prose; citation retrieval/publication dates are excluded.
Quarter-sourced changes (109): only existing YYYY-01-01 placeholders whose year differs from the table year qualify. The stored date is the first day of the stated quarter, a normalization convention rather than a claimed exact launch day. Same-year quarter-only entries and nonplaceholder dates remain untouched.
Skip examples: MT6572 appears in multiple rows; ambiguous shared MT part numbers and combined Exynos 2400/2400e variants are excluded. Dimensity 1100/1200 have conflicting table/prose dates. Kirin models without explicit dates (including Kirin 960/970) remain untouched; cited article dates are not treated as chip launch dates.
Validation: PYTHONIOENCODING=utf-8 python -m app.validate passed. Integrity checks passed for all 117 records: only release_date/source_urls changed, slugs preserved, exact change scope verified, and all 114 year-changing records moved to matching year folders.
🔎 Data verification — Tier 0 (offline existence/trust)
Scored by app.verify; posted by TechEngineBot. Informational only — the structural gate (app.validate) is separate and authoritative for merge.
Changed records in this PR
186 record(s) scored.
%%{init: {"theme":"base","themeVariables":{"pie1":"#3fb950","pie2":"#d29922","pie3":"#f85149","pieStrokeWidth":"0px","pieOpacity":"1"}}}%%
pie showData
title Verification bands — all records
"Green" : 45
"Yellow" : 141
"Red" : 0
Loading
Category
Distribution
Total
🟢
🟡
🔴
🟢 %
soc
🟩🟩🟩🟨🟨🟨🟨🟨🟨🟨🟨🟨
182
45
137
0
24.7%
tablet
🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨
4
0
4
0
0.0%
All
🟩🟩🟩🟨🟨🟨🟨🟨🟨🟨🟨🟨
186
45
141
0
24.2%
Full-dataset baseline
106343 record(s) scored.
%%{init: {"theme":"base","themeVariables":{"pie1":"#3fb950","pie2":"#d29922","pie3":"#f85149","pieStrokeWidth":"0px","pieOpacity":"1"}}}%%
pie showData
title Verification bands — all records
"Green" : 24281
"Yellow" : 81007
"Red" : 1055
Loading
Category
Distribution
Total
🟢
🟡
🔴
🟢 %
brand
🟩🟩🟩🟩🟩🟩🟩🟨🟨🟨🟨🟨
207
122
85
0
58.9%
soc
🟩🟩🟨🟨🟨🟨🟨🟥🟥🟥🟥🟥
2105
282
827
996
13.4%
smartphone
🟩🟩🟨🟨🟨🟨🟨🟨🟨🟨🟨🟥
93407
17990
75363
54
19.3%
tablet
🟩🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟥
3459
292
3166
1
8.4%
watch
🟩🟩🟨🟨🟨🟨🟨🟨🟨🟨🟨🟥
442
83
356
3
18.8%
pda
🟩🟩🟩🟩🟩🟩🟩🟨🟨🟨🟨🟨
140
83
57
0
59.3%
gpu
🟩🟩🟩🟩🟩🟩🟩🟨🟨🟨🟨🟨
2076
1266
810
0
61.0%
cpu
🟩🟩🟩🟩🟩🟩🟩🟩🟩🟩🟨🟥
4507
4163
343
1
92.4%
All
🟩🟩🟩🟨🟨🟨🟨🟨🟨🟨🟨🟥
106343
24281
81007
1055
22.8%
Hard violations (forced red):
Count
Check
1
!boost_ge_base
green = authoritative source + complete + consistent · yellow = plausible, needs confirmation · red = sparse/weak source or a hard contradiction. Promotion to verified runs in the scheduled verify-network workflow.
Tracked verified coverage is below 50% for tablet 7.9% (273/3459), watch 8.8% (39/442), soc 9.2% (193/2105), smartphone 18.7% (17501/93407), all 20.8% (22097/106343), gpu 49.4% (1026/2076).
Tracked coverage excludes records missing the verified field; see the Missing verified column for those records.
This does not fail validation. Keep imported records verified: false until manual audit, but treat this as follow-up verification work before relying on the affected categories as curated data.
Validation notes
The integrity gate blocks only hard anomalies introduced by this PR relative to its merge base.
Full advisory outlier listings are suppressed on successful runs because they are dataset-wide and mostly stable between PRs.
Failure runs still include a detailed log excerpt for debugging.
Key output:
## app.validate
## integrity_check.py (PR head compared with PR base)
loaded CPU=4507 GPU=2076
Integrity section
Flagged lines
structural
18
CPU name/tier consistency (desktop mainstream only)
0
CPU single>multi (cinebench/geekbench — should be multi>=single)
0
CPU era-vs-score outliers
8
CPU cross-source ratio outliers (possible wrong-variant)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
bugSomething isn't workingdataDataset changesenhancementNew feature or request
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Correct 117 SoC release dates with unambiguous matches on the supplied Wikipedia vendor pages. Preserve every field except
release_dateandsource_urls, preserve slugs, and move changed-year records usinggit mv.Month/day-precise table changes: none qualified.
Explicit prose changes (8): Exynos 4212 ×2 (2011-09-29), Exynos 5250 ×2 (2011-11-30), Exynos 2200 ×1 (January 2022 represented as 2022-01-01), Kirin 9000S ×1 (2023-08-29), Kirin 9030 and 9030 Pro ×1 each (2025-11-25). These are chip announcement/introduction dates explicitly named in page prose; citation retrieval/publication dates are excluded.
Quarter-sourced changes (109): only existing
YYYY-01-01placeholders whose year differs from the table year qualify. The stored date is the first day of the stated quarter, a normalization convention rather than a claimed exact launch day. Same-year quarter-only entries and nonplaceholder dates remain untouched.Skips by vendor:
Skip examples: MT6572 appears in multiple rows; ambiguous shared MT part numbers and combined Exynos 2400/2400e variants are excluded. Dimensity 1100/1200 have conflicting table/prose dates. Kirin models without explicit dates (including Kirin 960/970) remain untouched; cited article dates are not treated as chip launch dates.
Sources: MediaTek, Exynos, HiSilicon.
Validation:
PYTHONIOENCODING=utf-8 python -m app.validatepassed. Integrity checks passed for all 117 records: only release_date/source_urls changed, slugs preserved, exact change scope verified, and all 114 year-changing records moved to matching year folders.Closes #1