The split was analytically correct
Link isolated facts about logical relationships, endpoints, paths, transports, identities, and network-conditioned observations. Edge isolated external capabilities, provider operations, bodies, Receipts, Artifacts, remote uncertainty, and residual state. That distinction remains useful inside the architecture.
The repository boundary was wrong
An open Task does not first solve an abstract network problem and then begin an unrelated execution problem. The intended Effect determines which endpoint, identity, locality, transport, session, and provider are acceptable. The chosen path and provider can change what the Task observes or what consequence occurs.
A timeout demonstrates the coupling. The request may not have been delivered, the provider may have accepted but not completed it, the Effect may have succeeded while the response was lost, or the Artifact may have reached storage while the Receipt failed. Recovery must understand delivery and execution together before retry.
Boundary decision
One continuity boundary for conditioned external interaction
Connectivity and external action remain distinct internal planes, while continuity is modeled where they meet.
External work is a graph
Local-to-remote calls are only one case. Remote work may call back to a changed Host generation. A Sandbox may send a large Artifact directly to object storage or another provider. One Task may fan out to several browsers, Sandboxes, Agents, or verifiers and later join their independently conditioned results.
Ordivon should preserve why those interactions occur, which authority applies, which identities and revisions were used, what evidence was produced, and which outcome remains unknown. It should not route every byte through a central proxy merely to claim control.
World Interaction is the new research object
The unified project correlates Task, Attempt, Effect, Dispatch, target, participant, endpoint, path Observation, transport session, provider execution, Receipt, Artifact, Claim, and Verification. It does not collapse them into one ID. Connectivity and action remain independently versioned internal planes; continuity is where they meet.
What was migrated
The production Cloudflare Fetch, Browser, private R2, Receipt, fencing, reconciliation, release, and rollback implementation now lives under providers/cloudflare/. Route, DNS, endpoint, HTTP/TLS, QUIC, transfer, lifetime, Network World, reference transport, and private egress work now lives under modules/network-observation/. Both Git histories were imported into Ordivon World.
What was not created
There is no universal World schema, global identity, automatic resolver, route or provider selector, central data plane, general Sandbox, new VPN, CNI, Service Mesh, workflow engine, or permanent Agent body. The first experiment must show that a thin shared boundary prevents a real failure better than direct Host integration.
The correction is part of the evidence
Architecture should follow the object that must remain continuous, not the repositories that happened to exist first. Edge and Link were useful prototypes. Deleting their project boundary preserves the useful code while removing the assumptions that the code had begun to impose on the research.