Every requirement of a profile MUST be accepted by defineRequirement of Archon, MUST say why it holds (the profile and the controls it answers), MUST depend on the requirements it needs (the package before its files, the files before the service) and MUST name the same subject; the ids MUST be stable, services.<service>.<part>.
Enforced (check): .github: cd commons/linux-services && bun run verify — suite/services.test.ts
Proved by: linux-services/suite/services.test.ts
Written in: linux-services/src/logical/services.ts
Tests: passed: suite/services.test.ts PostgreSQL's requirements are the package, the drop-in folder, the drop-in and the cluster; passed: suite/services.test.ts the mail relay is a null client that relays over implicit TLS, rewrites senders and sends ; passed: suite/services.test.ts the certificate's requirements install certbot and its plugin, configure DNS-01, issue onc