Bulk v1 — Remaining Human Semantic Review
Final outstanding formalization queue after deterministic reconciliation and materialization.
Status
- Formal revisions persisted: 1,683 / 1,702
- Outstanding revisions: 19
- Evidence blockers: 0
- New bulk review decisions: 0
- Production eligible claims remain: 39
The 19 rows below are intentionally not auto-revalidated. Each requires a semantic or ontology decision that cannot be proven from wikilink drift alone.
1. ICMS / CMX ontology and rebrand — 14
The source describes the platform historically as ICMS / Inference Context Memory Storage and later under CMX branding. The existing Inference Context Memory Storage canonical node remains meaningful, while there is no safe automatic rule establishing whether CMX is merely an alias, a renamed canonical identity, or a successor/new node.
| Legacy ID | Source line | Human decision |
|---|---|---|
| NIEK2-0291 | 365 | Decide ICMS canonical + CMX alias vs CMX successor/new canonical vs explicit rebrand relation. |
| NIEK2-0292 | 365 | Same ontology decision. |
| NIEK2-0303 | 377 | Resolve ICMS/CMX identity before changing the frame target. |
| NIEK2-0319 | 391 | Resolve ICMS/CMX identity before removing the historical target. |
| VR2-0221 | 321 | Decide the canonical identity and rebrand relationship. |
| VR2-0222 | 321 | Decide whether ICMS remains, CMX replaces it, or both are represented. |
| VR2-0231 | 325 | Resolve ICMS/CMX ontology before formalization. |
| VR2-0232 | 325 | Resolve alias vs successor/new canonical vs rebrand relation. |
| VR2-0234 | 327 | Resolve which canonical node represents the platform after rebranding. |
| VR2-0243 | 331 | Resolve platform identity before formalizing provider ecosystem relation. |
| VR2-0244 | 331 | Same provider-ecosystem ontology decision. |
| VR2-0245 | 331 | Same provider-ecosystem ontology decision. |
| VR2-0246 | 331 | Same provider-ecosystem ontology decision. |
| VR2-0247 | 331 | Same provider-ecosystem ontology decision. |
2. Ambiguous bare Vera reference — 4
These rows previously targeted NVIDIA Vera CPU, but the current source no longer retains an explicit Vera CPU surface form. Bare Vera is not sufficiently specific for a fail-closed automatic mapping.
| Legacy ID | Source line | Human decision |
|---|---|---|
| VR2-0119 | 149 | Confirm whether bare Vera means the canonical NVIDIA Vera CPU. |
| VR2-0199 | 295 | Confirm whether the implicit Vera reference is specifically NVIDIA Vera CPU. |
| VR2-0200 | 295 | Same identity check. |
| VR2-0201 | 295 | Same identity check. |
3. Multi-target alias drift — 1
| Legacy ID | Source line | Human decision |
|---|---|---|
| VR2-0609 | 733 | Independently confirm both NVIDIA Vera CPU and Vera Rubin frame participants; the current evidence loses both specific links while adding generic CPU. |
Already formalized Golden rows still visible as non-ready in corpus preflight
These are not part of the 19 outstanding revision slots because a Golden/repair revision already exists:
NIEK2-0054NIEK2-0215VR2-0242VR2-0504
Review rule
Do not convert any of the 19 rows to READY solely because the raw text still resembles the prior claim. A reviewer must explicitly resolve the ontology/entity identity first; any accepted repair should remain source/hash-bound and must not create an APPROVE decision automatically.