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 65 SoC release dates from Wikipedia launch tables - #287
Correct 65 SoC release dates using unambiguous vendor/model matches in Wikipedia tables. Preserve slugs and all fields except release_date and source_urls; move records to the matching year folder with git mv.
Vendor
Updated
Unmatched
Ambiguous
Coarse/missing date
Already within policy
qualcomm
55
270
56
30
35
mediatek
0
179
17
148
0
samsung
0
67
5
91
0
apple
10
2
63
0
7
google
0
0
0
0
5
hisilicon
0
44
0
18
0
Quarter/year-only dates are skipped. Multiple matching rows, model/marketing conflicts, hardware revisions, mismatched part suffixes, and Galaxy rows sharing standard-chip announcement dates are skipped. Tensor dates already satisfy the six-month policy; MediaTek, Exynos, and Kirin matches lack month-level dates. Apple rows with multiple hardware configurations are skipped even when they share a release date.
Sample model
Previous
Corrected
Qualcomm Snapdragon 450 SDM450
2018-01-01
2017-06-28
Qualcomm Snapdragon 845 SDM845
2019-01-01
2017-12-07
Qualcomm Snapdragon 8 Gen 1 5G SM8450
2023-01-01
2021-11-30
Qualcomm Snapdragon 8 Gen 2 5G SM8550-AB
2024-01-01
2022-11-15
Apple S1
2014-01-01
2015-04-24
Apple A16 Bionic APL1W10 T8120
2023-01-01
2022-09-16
Validation: PYTHONIOENCODING=utf-8 python -m app.validate passed. Additional integrity checks confirm that only release_date/source_urls changed and all slugs and year folders are preserved.
🔎 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
65 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" : 1
"Yellow" : 64
"Red" : 0
Loading
Category
Distribution
Total
🟢
🟡
🔴
🟢 %
soc
🟩🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨
65
1
64
0
1.5%
All
🟩🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨
65
1
64
0
1.5%
Full-dataset baseline
106339 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" : 24216
"Yellow" : 81041
"Red" : 1082
Loading
Category
Distribution
Total
🟢
🟡
🔴
🟢 %
brand
🟩🟩🟩🟩🟩🟩🟩🟨🟨🟨🟨🟨
207
122
85
0
58.9%
soc
🟩🟨🟨🟨🟨🟨🟥🟥🟥🟥🟥🟥
2105
254
843
1008
12.1%
smartphone
🟩🟩🟨🟨🟨🟨🟨🟨🟨🟨🟨🟥
93407
17956
75383
68
19.2%
tablet
🟩🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟥
3455
292
3162
1
8.5%
watch
🟩🟩🟨🟨🟨🟨🟨🟨🟨🟨🟨🟥
442
80
358
4
18.1%
pda
🟩🟩🟩🟩🟩🟩🟩🟨🟨🟨🟨🟨
140
83
57
0
59.3%
gpu
🟩🟩🟩🟩🟩🟩🟩🟨🟨🟨🟨🟨
2076
1266
810
0
61.0%
cpu
🟩🟩🟩🟩🟩🟩🟩🟩🟩🟩🟨🟥
4507
4163
343
1
92.4%
All
🟩🟩🟩🟨🟨🟨🟨🟨🟨🟨🟨🟥
106339
24216
81041
1082
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/3455), watch 8.8% (39/442), soc 9.2% (193/2105), smartphone 18.7% (17501/93407), all 20.8% (22097/106339), 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 65 SoC release dates using unambiguous vendor/model matches in Wikipedia tables. Preserve slugs and all fields except release_date and source_urls; move records to the matching year folder with git mv.
Quarter/year-only dates are skipped. Multiple matching rows, model/marketing conflicts, hardware revisions, mismatched part suffixes, and Galaxy rows sharing standard-chip announcement dates are skipped. Tensor dates already satisfy the six-month policy; MediaTek, Exynos, and Kirin matches lack month-level dates. Apple rows with multiple hardware configurations are skipped even when they share a release date.
Validation:
PYTHONIOENCODING=utf-8 python -m app.validatepassed. Additional integrity checks confirm that only release_date/source_urls changed and all slugs and year folders are preserved.Refs #1