任何两个模块之间有两条箭头：谁在运行时调用谁，和谁在源码里 import 谁。平时它们同向，所以我们从不区分；hexagonal 做的全部事情，就是把 outbound 那一侧的第二条箭头掰回来。从四层结构讲起，包括大多数介绍会漏掉的 application 层，以及一件几乎没人提的事：架构违规在类型系统里完全不可见。

Between any two modules there are two separate arrows: who calls whom at runtime, and who imports whom in the source. They normally align, so we never distinguish them; everything hexagonal does is bend the second one back on the outbound side. Starting from the four layers — including the application layer most introductions skip — and ending on something almost nobody writes about: an architectural violation is completely invisible to the type system.

加州要求的最低人身伤害责任险是 1.5 万美元 —— 这个数字从 1967 年一直用到 2025 年 1 月,比阿波罗 11 号还早两年。我原本以为有一个艰难的取舍在压着最低限不让它涨,去查了证据,发现没有。真正压着它的东西更无聊,也更糟。

California required $15,000 of injury coverage from 1967 until January 2025 — a number set two years before Apollo 11. I assumed there was a hard trade-off keeping minimums low. I went looking for the evidence and it isn't there. What's actually holding them down is duller, and worse.

A declarations page is eight abbreviations and no explanation of which ones are for you. Here is every coverage on a U.S. auto policy, sorted by whose contract it belongs to — and then one $180,000 injury run through all of them, which shows what no-fault actually did and what it left completely untouched.

保单首页是八个缩写,没有一行告诉你哪些是给你的。这篇把美国车险上每一个条款按「这是谁的合同」摊开讲一遍,然后拿一场 18 万美元的伤情从头跑到尾 —— 你会看到 no-fault 到底做了什么,以及它一点都没碰到的那部分。

Every insurance policy is cut along one seam, and the seam is defined by a question nobody says out loud: who signed this contract? Count the signatures and the whole thing reorganizes — why the other driver's adjuster is allowed to lowball you, where no-fault's speed actually comes from, and why the coverage that pays a stranger's medical bills sits on the liability side.

每一张保单都是沿着同一条缝切开的,而这条缝取决于一个没人说出口的问题:这份合同是谁签的?把签字的人数一遍,整件事就会重新排列 —— 为什么对方的理赔员有权压你的价,no-fault 的快是从哪来的,以及为什么那个替陌生人付医疗费的条款,站在责任险那一边。