Function json_bare_scalar_name 

pub fn json_bare_scalar_name(n: &str) -> bool

Why a ## Route cannot be lowered to a plain function yet.

A route body IS a function body, so the ones this understands need nothing new from any tier. The rest are refused BY NAME rather than lowered into something that half-works: a route that answers the wrong thing is worse than one that will not start. The types whose LOGOS display IS valid JSON with no quoting — a number, a boolean.

ONE definition, read by the record derive and by the router. A route answering an Int and a record FIELD holding one have to agree about what reaches the wire, and two lists drift the first time a numeric type is added.