ARC

A backend and the specification describing it drift apart from the first week, because the spec is documentation and the code is the truth. ARC inverts that: the validated OpenAPI spec is the source, and the AWS backend is generated from it.

Every team writes the spec first and then stops maintaining it. Within a month the endpoint has an extra field, the documentation does not, and everyone who depends on the contract learns about the change by hitting an error. The tooling treats the spec as a description, so it is only ever as accurate as the last person who remembered.

ARC makes the spec the artifact that is deployed, so drift becomes structurally impossible rather than a discipline problem. The published pilot is the useful evidence: a multi-tenant, compliance-sensitive notification platform, five services and several hundred AWS resources, most of it standing up on the first day. The interesting claim is not the speed, it is that the running system and its contract cannot disagree.