Verification and TechEngineBot (workstream)

[Seungpyo1007]

Purpose

Workstream tracker for verification and TechEngineBot, under the roadmap #97. PRs in this area link here with Closes #<this>.

Scope

• app/verify (offline scoring, signals, hosts, crossref, network verify, promotion ledger)
• integrity_check.py (structural checks for all categories; benchmark sanity for CPU/GPU)
• TechEngineBot PR comments: techapi-pr-validation-comment, techapi-verify-comment, /verify, dump check
• verify-network, verify-status, coverage-report workflows

Status (2026-09-27)

• Every category is scored since feat: analyze all dataset categories and actual PR diffs #95. Categories without domain rules (laptop, monitor, software, website) get structural checks only and can't be green.
• Verified: 11.5% of records, 16.3% of models, across TechAPI.

Open items

• Source qualifying T1/T2 citations for the remaining yellow laptop/monitor records: current Tier 0 laptop 107 green / 1,888 yellow / 0 red and monitor 0 green / 882 yellow / 0 red (feat(verify): add laptop and monitor domain scoring #102). Of the yellow records, laptop 0/1,888 and monitor 0/882 have a qualifying source_url; all 2,770 need sourcing (no pipeline gap found).
• Domain scoring rules (RICH_FIELDS and signals) for laptop and monitor.
• 18 pre-existing CPU anomalies from the full integrity scan.
• Next promotion pass (verify-network) after the release of #292 data.

[Seungpyo1007]

Reopened: this tracker was auto-closed by the Closes #98 keyword in #101's commit message. Tracker issues stay open. #101 (laptop/monitor Tier 0 normalization) is done: laptop 0/1,995/0 and monitor 0/882/0 (green/yellow/red), up from 1,888 and 882 red.

[Seungpyo1007]

Live laptop/monitor audit against TechAPI develop bf4a0597381cdf208c1fdeceedc1559f2b770bb7 using TechEngine main 303890871897f50bf214ca4943fb569b9073ddd6 and the same app.verify score / status tooling used for #102. The old "red in Tier 0" checklist text is stale after #101/#102.

Category	Green	Yellow	Red	Yellow with T1/T2 source_url	Yellow without T1/T2 source_url
laptop	107	1,888	0	0	1,888
monitor	0	882	0	0	882

This is a data gap: all 2,770 yellow records need qualifying citations. Among yellow laptops, 965 cite only https://huggingface.co/datasets/Ammok/laptop_price_prediction (unclassified host) and 923 cite only https://github.com/abhinavflac/laptops-specs-dataset (T3); all 882 monitors cite only https://www.kaggle.com/datasets/durjoychandrapaul/amazon-products-sales-monitor-dataset (T3). These are existing dataset citations, not model-specific authoritative sources.

verify-network scores every category without a category filter; check-urls and promote also default to every category, including laptop and monitor. promote recomputes offline.score_record for each unverified record and accepts live classified T1/T2 citations. None of these paths excludes laptops or monitors, and the green band still correctly requires a T1/T2 source. No sources were invented or reclassified, no data files or code were changed, and no code PR is warranted for this outcome.

Before/after bands are unchanged: laptop 107/1,888/0; monitor 0/882/0 (green/yellow/red). Validation: full pytest suite 499 passed in 258.79s against live TechAPI develop data; mypy app and ruff check app tests pass.