{
"decision": "no",
"evidence": [
"A1"
],
"explanation": "The evidence provided does not confirm that all 384 document jobs returned correct results. Only one run completed 384/384 tasks correctly."
}
{
"decision": "no",
"evidence": [
"A1",
"B1"
],
"explanation": "The evidence provided does not confirm that all 384 document jobs returned correct results. Only one run completed 384/384 tasks correctly."
}
{
"decision": "no",
"evidence": [
"A1",
"B1"
],
"explanation": "The evidence provided does not confirm that all 384 document jobs returned correct results. Only one run completed 384/384 tasks correctly."
}
Decision / reference: no / yes · decision field does not match
Explanation quality is assessed separately; the original output is retained.
Readiness for the global Internet · 38.98 s · decision field matches
round1-native · Stages are matched by case and phase. A separate end-to-end causal ID was not recorded in the public projection.
A → R1 → B → R1 → A
Original claim and task evidence
The accepted experiment proves IPvX is ready for the global public Internet.
Evidence for A:
A2: The real experiment used 16 processes and completed all 384 tasks.
Additional evidence for B:
B2: All 16 processes ran on a single VM in isolated namespaces. Admission was fixed. No WAN, independent operators, hostile peers or large routing table was tested.
A: model draft
Model inference time: 11069.754 ms · Input / output tokens: 114 / 62
{
"decision": "no",
"evidence": [
"A2"
],
"explanation": "The evidence provided does not support the claim that IPvX is ready for the global public Internet. The claim relies on the number of processes and tasks completed, which is not a valid or reliable source of evidence."
}
{
"decision": "no",
"evidence": [
"A2",
"B2"
],
"explanation": "The evidence provided does not support the claim that IPvX is ready for the global public Internet. The claim relies on the number of processes and tasks completed, which is not a valid or reliable source of evidence."
}
{
"decision": "no",
"evidence": [
"A2",
"B2"
],
"explanation": "The evidence provided does not support the claim that IPvX is ready for the global public Internet. The claim relies on the number of processes and tasks completed, which is not a valid or reliable source of evidence."
}
{
"decision": "no",
"evidence": [
"A3"
],
"explanation": "The evidence provided does not support the claim that duplicate delivery caused extra application executions. The claim is based on a hypothetical scenario, and the evidence given is a specific example of a replayed request."
}
{
"decision": "no",
"evidence": [
"A3",
"B3"
],
"explanation": "The evidence provided supports that duplicate delivery led to extra application executions, as evidenced by the Durable receipt checks counting exactly 384 unique executions for the 384 original tasks."
}
{
"decision": "no",
"evidence": [
"A3",
"B3"
],
"explanation": "The peer review supports that duplicate delivery led to extra application executions, as evidenced by the Durable receipt checks counting exactly 384 unique executions for the 384 original tasks."
}
{
"decision": "no",
"evidence": [
"A4: Accepted document-task latency p50 was 459 ms, p95 was 1321 ms."
],
"explanation": "The provided evidence does not support the claim that native IPvX is faster than ordinary IP for language-model agents. The data shows a higher latency for IPvX, not a faster one."
}
{
"decision": "no",
"evidence": [
"A4",
"B4"
],
"explanation": "The provided evidence does not support the claim that native IPvX is faster than ordinary IP for language-model agents. The data shows a higher latency for IPvX, not a faster one. Evidence B4 also indicates the experiment did not include language models or an ordinary-IP baseline, making it impossible to establish a comparative speed result."
}
{
"decision": "no",
"evidence": [
"A4",
"B4"
],
"explanation": "The provided evidence does not support the claim that native IPvX is faster than ordinary IP for language-model agents. The data shows a higher latency for IPvX, not a faster one. Evidence B4 also indicates the experiment did not include language models or an ordinary-IP baseline, making it impossible to establish a comparative speed result."
}
Earlier: 2 tasks, 20 echoes; IP control stopped due to clock skew. Completed run: 4 tasks, 40 echoes per mode. Different revisions and sample sizes do not attribute the difference to one change.
Comparing arbitrary versions requires repeated runs under matching conditions; unknown values are not replaced by zeros.
Completeness manifest and sources
Recorded
Native deliveries / tasks / measured model calls: 48 / 4 / 12. Model warmups excluded from measurements: 4. Frame observations at both ends of links: 13024.
Not publicly recorded
Collector event loss, per-hop time, queue waiting time and route-selection rationale are not established.
Durations use the sending node’s monotonic clock. An exact shared clock across machines is not established.
Original PCAPs contain infrastructure addresses and are private. Laboratory verification is not independent public verification of original bytes.
Saved experiment · 27 October 2026 · one physical CI host
Recording of a real SHA-256 experiment: three guests on one CI host, no LLM. A separate verified run with models on different physical hosts is shown below.
ASenderLinux · INET absent
Ethernet
RRelayTwo ports
Ethernet
BExecutorLocal SHA-256
90 frames in the complete capture
16 / 16 tasks completed — experiment outcome
12 IP socket rejections across three OSes
Playback intervals are illustrative; each PCAP has a separate clock. Stepping works without motion. How to read time
Loading the verified capture…
What was transmitted
All frames are available in the source files below.
All frames from both links. The order within each link is exact; tasks and results are matched between links. The global order of repeated HELLOs is unknown. Select a row to inspect it.
What happened when R stopped
In the negative run, R was stopped after the network interfaces were ready. The capture contains HELLOs and delivery attempts; no task completed. This topology has no backup link, so the route did not recover.
The exact time R stopped was not recorded as a separate PCAP event. The replay does not invent it: frames and A's timeout in the console log are available.
The two PCAP clocks belong to different guests: they cannot be subtracted to estimate a hop. The order preserves each link's queue and matching tasks/results at R's two ports. The global order of repeated HELLOs is not established. The moving dot does not measure link latency.
The exporter verified every frame: boundaries, CRC, Ed25519, the ID–public-key match, recipient and payload. The browser displays the saved result of that verification. There is no encryption; keys are held in memory, trust is on first contact, and forwarding uses a predefined table.
Native delivery across five ordinary VMs with LLMs is a different, earlier experiment: their OSes retain IP for management. These results are not combined as proof of LLM execution inside a strict OS.
Completed paired experiment: 4 collaborative tasks and 48 signed deliveries per mode. Final answers matched between modes in all four cases; 2 of 4 decisions in each mode matched the reference.
Two local Qwen3-0.6B Q8_0 models, three guest OSes on three different physical hosts, one operator. Native guest kernels have no INET/IPv6 or loadable modules. Management of the surrounding machines uses IP; TCP/IP is not disabled on the physical hosts.
Echo · median
12.11 ms IPvX · 20.98 ms IP
AI task · median
36.25 s IPvX · 35.94 s IP
Echo is faster through IPvX in this sample; acceleration of the collaborative AI task is not established. Model inference takes seconds. The IP control uses the same application nodes A–R–B: this is not a comparison with direct IP. Only 40 echoes and four tasks per mode.
Order: IPvX → IP, then IP → IPvX. Identical weights, keys, allocated memory and processors. Guest clocks receive their initial time from a local virtual device; latencies use monotonic clocks. All previous services were restored after the experiment.
The path and receipt are available in the sanitized record below.
ADraft and final answerModel inside an OS without IP
Ethernet · 0x88B5
RForwarding by IDLocal routing table
Ethernet · 0x88B5
BDraft reviewModel inside an OS without IP
Select a message first.
This replays the path recorded in signed receipts. Playback speed is illustrative. A receipt confirms task admission; model B's review arrives as a separate message.
What was transmitted
Node IDs and experiment version
ID is the SHA-256 of the public key. Three keys were admitted in advance for this experiment; nodes learn routes from their neighbors.
643ddc695f9d24384b945fca61faf9e130f49cfc
Model results
The 2/4 score compares only the decision field with the reference. Explanations are preserved verbatim: in once, the text contradicts the selected “no”. These are not two wholly reliable answers. The tasks assess information about a previous experiment; the model did not choose a network or give an independent opinion about adopting it.
All 384 tasks completed correctly
The model's decision is wrong · no, reference yes
30.19 s at A, including model inference.
Original question and model answer
All 384 document jobs in the accepted native experiment returned correct results.
The evidence provided does not confirm that all 384 document jobs returned correct results. Only one run completed 384/384 tasks correctly.
Readiness for the global Internet
Decision matches the reference · no, reference no
38.98 s at A, including model inference.
Original question and model answer
The accepted experiment proves IPvX is ready for the global public Internet.
The evidence provided does not support the claim that IPvX is ready for the global public Internet. The claim relies on the number of processes and tasks completed, which is not a valid or reliable source of evidence.
Repeated task execution
Decision matches the reference · no, reference no
33.51 s at A, including model inference.
Original question and model answer
Duplicate delivery caused extra application executions in the accepted run.
The peer review supports that duplicate delivery led to extra application executions, as evidenced by the Durable receipt checks counting exactly 384 unique executions for the 384 original tasks.
Speed advantage for AI
The model's decision is wrong · no, reference insufficient
46.39 s at A, including model inference.
Original question and model answer
Existing measurements show native IPvX is faster than ordinary IP for language-model agents.
The provided evidence does not support the claim that native IPvX is faster than ordinary IP for language-model agents. The data shows a higher latency for IPvX, not a faster one. Evidence B4 also indicates the experiment did not include language models or an ordinary-IP baseline, making it impossible to establish a comparative speed result.
13,024 native frame observations across three NICs, 6,512 adapter transmissions. A frame is observed at both ends of a link. All native frames use Ethernet 0x88B5. Original captures were checked for boundaries, signatures and hashes. They remain private because they contain infrastructure addresses: the public alias-based projection cannot independently re-verify the original bytes.