> TypeScript also was specifically designed so engine could strip types and execute result code.

That's no less a build step than concating, bundling, minifying, etc. When people say "I'm against processing code before deploying it to a web site" but then also say "TypeScript is okay though" or "JSX is okay though," all they're really saying is "I like some build steps but not others." Which is fine! Just say that!

If you have proof of home ownership and proof of legal guardianship of the child, what’s the problem?

I can see it being a problem if e.g. a bunch of family members are putting their kids in a school district based on a single home owned by a grandparent. But if that grandparent was also the kid’s legal guardian, fair enough!

> It’s also very brittle and one charismatic populist away from unraveling

All sufficiently large governments (really all organizations of any kind) are necessarily like this, from the most successful attempts at open societies to the most autocratic. They all require constant vigilance both to perform their intended function and to preserve themselves into the future.

Note that even though the U.S. has a Constitution, the entire U.S. government is still, like the UK, highly reliant on inexplicit norms many of which go back hundreds of years before the U.S. was founded. They’re both still English common law systems.

That generally works for timestamps (Temporal Instant). But it doesn’t work for representing calendar dates with no time information (Temporal PlainDate) unless you add an additional strict convention like “calendar dates are always represented as midnight UTC”).