Problem
The Institute Naming pack (API-NAME-002, compound member identifiers) has no exemption for member names that are verbatim tokens of an externally specified contract. Concrete case: a TLS configuration surface at the L2/L3 boundary spelling RFC 6066's Server Name Indication field as `serverName` draws API-NAME-002, though L2's mission is fidelity to externally specified vocabulary, and the corpus already treats L2 spec mirrors as carrying spec spellings (e.g. createdAt-style names existing only in L2 spec mirrors).
Found during the Pre-Launch Foundation Programme TX-VG0 compliance measurement (106 representative declarations; this was the only finding requiring a principal exemption rather than a lawful respelling). Principal approved the exemption for the concrete case on 2026-08-06.
Proposed outcome
The Naming pack gains a typed, evidence-carrying exemption for spec-token member names: a member spelling is exempt from API-NAME-002 when it is a verbatim token of the externally specified contract the declaring target mirrors, with the authority citation (RFC/spec section) recorded at the exemption site. Observable outcome: the concrete `serverName` case lints clean under the exemption with its RFC 6066 citation, a near-miss control (a compound member that is NOT a spec token in the same target) still fires, and the exemption is unavailable in L1.
Problem
The Institute Naming pack (API-NAME-002, compound member identifiers) has no exemption for member names that are verbatim tokens of an externally specified contract. Concrete case: a TLS configuration surface at the L2/L3 boundary spelling RFC 6066's Server Name Indication field as `serverName` draws API-NAME-002, though L2's mission is fidelity to externally specified vocabulary, and the corpus already treats L2 spec mirrors as carrying spec spellings (e.g. createdAt-style names existing only in L2 spec mirrors).
Found during the Pre-Launch Foundation Programme TX-VG0 compliance measurement (106 representative declarations; this was the only finding requiring a principal exemption rather than a lawful respelling). Principal approved the exemption for the concrete case on 2026-08-06.
Proposed outcome
The Naming pack gains a typed, evidence-carrying exemption for spec-token member names: a member spelling is exempt from API-NAME-002 when it is a verbatim token of the externally specified contract the declaring target mirrors, with the authority citation (RFC/spec section) recorded at the exemption site. Observable outcome: the concrete `serverName` case lints clean under the exemption with its RFC 6066 citation, a near-miss control (a compound member that is NOT a spec token in the same target) still fires, and the exemption is unavailable in L1.