{
 "_doc": "One result as verifycorelabs.com prints it: the headline, the problem and the buyer cut (never reworded) from the lab's plain-English account of the result, the one figure a buyer is shown and its limit, and the lab's current claim and limits verbatim, copied at the commit named in source. A field is left out, never reworded, when it uses a word this site keeps for its own process or names a file this site does not serve (not_reprinted).",
 "slug": "uec-interconnect-essentiality",
 "company": "OrbitalProof",
 "order": 7,
 "rank": 7,
 "served_receipt": "wireless-reliability/results/uec-interconnect-essentiality.json",
 "lab_file_older": false,
 "headline": [
  "In a computer model, the lab shows that its design for the",
  "recovery step of the new Ultra Ethernet networking standard always passes",
  "on in sequence order and never twice"
 ],
 "qualification": [
  "which is what one sentence of the published standard requires of any correct implementation, so this shows the design conforms, not that it is essential, since the standard allows other compliant designs",
  "four checking tools agree, but all check the lab's one model"
 ],
 "why": [
  "A network-card designer implementing the standard's reliable ordered delivery wants machine-checked evidence that a given recovery design keeps the standard's ordering rule"
 ],
 "buyer": [
  "makers of network cards, switches and chips for artificial-intelligence data-centre networks implementing the Ultra Ethernet standard"
 ],
 "figure": "by four independent engines",
 "figure_from": "claim",
 "limit": "This is a **modeling entailment, not a legal or SEP opinion**",
 "limit_from": "lab limits",
 "plain": "four checking tools agree",
 "quotes": {
  "converse": "in the same model the mandate as literally stated does not require the gate (39 distinct compliant receivers do without it)"
 },
 "claim": "The UET delivery sublayer's Reliable-Ordered-Delivery recovery gate is proven to entail the published UEC 1.0.2 rule that data be delivered to the wire in the order of its sequence number — by four independent engines, against a copy of the third party's own text checked by its SHA-256 hash, with the naive one-deep window refuted by counterexample.",
 "not_reprinted": [
  "limits"
 ],
 "prior_work": [
  {
   "title": "Ultra Ethernet Specification v1.0.2",
   "by": "Ultra Ethernet Consortium (PDF metadata author Paul Congdon), 2026-01-28",
   "url": "https://ultraethernet.org/wp-content/uploads/sites/20/2026/01/UE-Specification-1.0.2-1.pdf"
  },
  {
   "title": "Mechanical verification of a two-way sliding window protocol",
   "by": "Bahareh Badban, Wan Fokkink, Jan Cornelis van de Pol, Communicating Process Architectures 2008",
   "url": "https://research.utwente.nl/en/publications/mechanical-verification-of-a-two-way-sliding-window-protocol/"
  },
  {
   "title": "ETSI Intellectual Property Rights Policy (ETSI Rules of Procedure, Annex 6)",
   "by": "ETSI",
   "url": "https://www.etsi.org/images/files/IPR/etsi-ipr-policy.pdf"
  },
  {
   "title": "Ultra Ethernet's Design Principles and Architectural Innovations",
   "by": "Torsten Hoefler et al., arXiv 2508.08906, 2025-08-12",
   "url": "https://arxiv.org/abs/2508.08906"
  }
 ],
 "source": {
  "claims_file": "registry/CLAIMS_CURRENT.jsonl",
  "claims_sha256": "81776df15a1498abec7228ea179c952d01c54e031ffd4144498a30660963074b",
  "ranking_file": "views/VALUE_RANKING.md",
  "ranking_sha256": "2e980e26178b34dc49ec1d365f966be292f57d7c636143fc62c12feab72ae470",
  "dossier_sha256": "7318665d95947f6a6bd76e5290396f7e3b265782c4f7a13856804cdec14c9abe",
  "commit": "25d755d2f06518b632c3658ae83f20312daac53e"
 }
}