Three TCP lanes hold four requests. Cold and reuse share connection 1, with one and zero new handshakes. Resume uses connection 2 with one resumed handshake; no cache uses connection 3 with one full handshake.

TLS handshakes add latency you can shrink

HTTPS latency combines several stages, and a warm request may avoid some without making cryptography faster. DNS, connection acquisition, TCP setup, TLS authentication, server work, and response transfer have different clocks. First determine which stages actually ran. Request duration alone cannot distinguish an existing connection from a new connection that resumed a TLS session. ...

June 28, 2027 · 6 min · XB Field Notes
An audit ledger keeps policy, TLS and deployment evidence on separate lines, with a reminder that evidence has scope.

Audit the trust of a public edge

Inspect security policy, verified TLS identity, issuance restrictions, and deployment trust with explicit limits.

August 6, 2026 · 7 min · XB Field Notes
An illustrative two-column ledger separates HTTP headers, final URL and status from TLS dates and expiry. Body equality requires another check.

Read the public edge in two commands

Two small read-only helpers turn the public endpoint into evidence you can inspect before and after a release.

July 13, 2026 · 4 min · XB Field Notes