Skip to content

OrbitalProof · AI-cluster networking · for a technical reader

An Ultra Ethernet recovery design, proved in a model: the lab’s exact wording

The lab’s own sentences and figures for this result, word for word, in its working terms, with its limits in plain words where the lab’s text cannot be reprinted. The plain account is on the result’s page; it says the same things in plain words.

The lab’s plain-English sentence

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

  • 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

Checking tools, in the lab’s words

by four independent engines

The limit to read first, in the lab’s words

This is a modeling entailment, not a legal or SEP opinion

The converse, in the same model

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.

[Plain gloss: the “four independent engines” are four checking tools that all read the lab’s one model of the standard, so a modelling mistake would pass all four, and only one of them is not limited to a small model size. “Proven to entail” means the design meets the standard’s ordering rule in that model; it is about ordering, not delivery.]

Limits

[The lab’s limits name a file this site does not serve, so they are not reprinted word for word. In plain words: this is a result in a model, not a legal opinion or a claim that the design is essential to the standard; it runs one way only, since other compliant receivers in the same model do without the design; and the model has no resend of lost data, so no receiver in it is guaranteed to make progress.]

All resultsFormal statements

How we show numbers

Every number on this site links to the file it comes from. How each result is checked

  • We never show a number before its file has loaded.
  • A question we have not checked yet is marked as unchecked.
  • A check that found nothing says so.
  • A file with no value for a question says so.
  • A number whose file is missing or has changed is not shown.
  • Two files that disagree about what a number describes are both flagged.
  • A number from too few samples shows its sample size.
  • Two files that give different values are both shown.
  • A file we cannot publish is listed by its fingerprint only.
  • A measurement more than a week old shows its age.
  • A question that does not apply to a page is left off it.
  • A measurement whose program failed is shown as failed.