You’re absolutely right that specifying routing and encapsulation is critical for any Internet replacement.

The Betanet v1.1 spec does indeed define detailed routing and encapsulation mechanisms, though they may be distributed across sections and layered abstractions:
• Routing is handled explicitly at Layer 1 (L1) using the SCION protocol combined with HTX-tunnelled transitions for interoperability with non-SCION links. This is described in §4 and provides path selection, AS-hop validation, and multi-path failover.
• Encapsulation is specified at Layer 2 (L2) with the HTX protocol, which runs covertly over TCP/QUIC port 443 using origin-mirrored TLS fingerprints and adaptive HTTP/2/3 behavior to blend seamlessly with normal traffic (§5).
• Edge bridging and transition across non-SCION networks are handled via HTX control streams with strict anti-replay and signed metadata (§4.2).

The spec aims to fully specify how traffic enters, routes through, and exits the network with strong anti-censorship and anti-correlation features, tightly integrated with the layered design.

That said, I agree the spec could improve clarity by consolidating or cross-referencing these elements more explicitly in the overview or adding a routing+encapsulation focused section to aid new readers.

If you’d find it helpful, I’d be happy to help draft a summary or diagram that pulls these components together more clearly.