@mailwoman/codex 4.11.0 → 4.13.0

package/out/address-system-conventions.d.ts

@@ -9,8 +9,8 @@
  *   detection instead of merely being nudged by it.
  *
  *   Every row is a provenance-carrying claim about a national addressing convention — the same
- *   no-load-bearing-trivia discipline as the rest of the codex. Add rows with a source, not from
- *   vibes; an absent row means "no constraints known", never "no constraints exist".
+ *   provenance-first discipline as the rest of the codex. Add rows with a source, not from vibes;
+ *   an absent row means "no constraints known", never "no constraints exist".
  *
  *   First consumer: `@mailwoman/neural`'s decoder applies `forbiddenTags` as a hard emission mask
  *   before Viterbi and treats `postcodePattern` as the system's canonical shape for the snap-only

package/out/address-system-conventions.js

@@ -9,8 +9,8 @@
  *   detection instead of merely being nudged by it.
  *
  *   Every row is a provenance-carrying claim about a national addressing convention — the same
- *   no-load-bearing-trivia discipline as the rest of the codex. Add rows with a source, not from
- *   vibes; an absent row means "no constraints known", never "no constraints exist".
+ *   provenance-first discipline as the rest of the codex. Add rows with a source, not from vibes;
+ *   an absent row means "no constraints known", never "no constraints exist".
  *
  *   First consumer: `@mailwoman/neural`'s decoder applies `forbiddenTags` as a hard emission mask
  *   before Viterbi and treats `postcodePattern` as the system's canonical shape for the snap-only
@@ -27,18 +27,18 @@ export const ADDRESS_SYSTEM_CONVENTIONS = {
      * suffix decomposition has no French counterpart).
      *
      * Provenance / why this is NOT a blanket prefix+suffix forbid (#719, 2026-06-18): an earlier
-     * model mis-tagged the leading "Rue" as a US-style `street_suffix` (RUE is genuinely a Pub-28
-     * suffix variant) — the 2026-06-10 v1.1.0 gate — so #511 forbade BOTH affix tags to stop that
-     * leakage. That forbid was correct for THAT model but became a live production bug for the
-     * current one: the shipped model (v1.5.0) emits the FR `street_prefix` correctly, but the
-     * conventions mask was a hard −1e9 on every B-/I-street_prefix emission, so the detected-FR parse
-     * could never KEEP a prefix — it destroyed `street_prefix` wholesale (measured on
-     * data/eval/external/ fr-street-prefix-real.jsonl at conventions=auto: F1 0.0 with the forbid on
-     * → 80.0 with it off; the larger real-FR eval reported the same collapse, ~96 → ~0.6). We keep
-     * ONLY `street_suffix` forbidden: the current model with the forbid OFF shows zero FR
-     * street_suffix leakage (fp=0 on that same slice) and FR genuinely has no trailing street suffix,
-     * so the constraint costs nothing while still guarding against any future suffix mis-tag.
-     * Postcode: exactly five digits (NF Z 10-011; see fr/code-postal).
+     * model mis-tagged the leading "Rue" as a US-style `street_suffix` (RUE is a Pub-28 suffix
+     * variant) — the 2026-06-10 v1.1.0 gate — so #511 forbade BOTH affix tags to stop that leakage.
+     * That forbid was correct for THAT model but became a live production bug for the current one:
+     * the shipped model (v1.5.0) emits the FR `street_prefix` correctly, but the conventions mask was
+     * a hard −1e9 on every B-/I-street_prefix emission, so the detected-FR parse could never KEEP a
+     * prefix — it destroyed `street_prefix` wholesale (measured on data/eval/external/
+     * fr-street-prefix-real.jsonl at conventions=auto: F1 0.0 with the forbid on → 80.0 with it off;
+     * the larger real-FR eval reported the same collapse, ~96 → ~0.6). We keep ONLY `street_suffix`
+     * forbidden: the current model with the forbid OFF shows zero FR street_suffix leakage (fp=0 on
+     * that same slice) and FR has no trailing street suffix, so the constraint costs nothing while
+     * still guarding against any future suffix mis-tag. Postcode: exactly five digits (NF Z 10-011;
+     * see fr/code-postal).
      */
     fr: {
         forbiddenTags: ["street_suffix"],

package/out/fr/cedex.d.ts

@@ -11,7 +11,7 @@
  *
  *   This slice closes the gap PR #516 documented: the shard builder sourced the shape from SCHEMA.mdx
  *   prose because codex had no cedex home. Now it does — the builder and any future consumer import
- *   from here (the no-load-bearing-trivia discipline: one provenanced source).
+ *   from here (the provenance-first discipline: one provenanced source).
  */
 /** Matches a CEDEX phrase: the keyword plus an optional 1–2 digit office number. */
 export declare const CEDEX_PATTERN: RegExp;

package/out/fr/cedex.js

@@ -11,7 +11,7 @@
  *
  *   This slice closes the gap PR #516 documented: the shard builder sourced the shape from SCHEMA.mdx
  *   prose because codex had no cedex home. Now it does — the builder and any future consumer import
- *   from here (the no-load-bearing-trivia discipline: one provenanced source).
+ *   from here (the provenance-first discipline: one provenanced source).
  */
 /** Matches a CEDEX phrase: the keyword plus an optional 1–2 digit office number. */
 export const CEDEX_PATTERN = /\bCEDEX(?:\s+(\d{1,2}))?\b/i;

package/out/fr/departement.d.ts

@@ -6,9 +6,9 @@
  *   The 101 French départements (96 metropolitan including Corsica's 2A/2B, plus the 5 overseas DOM),
  *   each mapped to its région.
  *
- *   The département is the load-bearing admin unit for French postal geography: a code postal's first
- *   two digits ARE the département number (see `code-postal.ts`), and the région is derived from
- *   the département. This table is therefore the hinge between `code-postal.ts` and `region.ts`.
+ *   The département is the key admin unit for French postal geography: a code postal's first two
+ *   digits ARE the département number (see `code-postal.ts`), and the région is derived from the
+ *   département. This table is therefore the hinge between `code-postal.ts` and `region.ts`.
  */
 import type { FrenchRegionCode } from "./region.js";
 /** Per-département record: code (2-digit, or `2A`/`2B`, or 3-digit DOM) + name + its région. */

package/out/fr/departement.js

@@ -6,9 +6,9 @@
  *   The 101 French départements (96 metropolitan including Corsica's 2A/2B, plus the 5 overseas DOM),
  *   each mapped to its région.
  *
- *   The département is the load-bearing admin unit for French postal geography: a code postal's first
- *   two digits ARE the département number (see `code-postal.ts`), and the région is derived from
- *   the département. This table is therefore the hinge between `code-postal.ts` and `region.ts`.
+ *   The département is the key admin unit for French postal geography: a code postal's first two
+ *   digits ARE the département number (see `code-postal.ts`), and the région is derived from the
+ *   département. This table is therefore the hinge between `code-postal.ts` and `region.ts`.
  */
 /** Département code → info. 96 metropolitan (incl. 2A/2B) + 5 overseas = 101. */
 export const FR_DEPARTEMENTS = {

package/out/gb/postcode.d.ts

@@ -39,11 +39,11 @@ import type { Tagged } from "type-fest";
  */
 export type Postcode = Tagged<string, "UkPostcode">;
 /**
- * UK postcode shape. A robust, slightly permissive form of the Royal Mail / UK-gov regex: one or
- * two leading letters (the area), a district digit, an optional district letter-or-digit, then the
- * inward sector digit and two unit letters, with the inward space optional so an un-spaced
- * `SW1A1AA` still validates. The full UK-gov pattern additionally whitelists the British Overseas
- * Territory codes (`ASCN`, `STHL`, `BBND`, …); those are rare enough to leave to the gazetteer.
+ * UK postcode shape. A permissive form of the Royal Mail / UK-gov regex: one or two leading letters
+ * (the area), a district digit, an optional district letter-or-digit, then the inward sector digit
+ * and two unit letters, with the inward space optional so an un-spaced `SW1A1AA` still validates.
+ * The full UK-gov pattern additionally whitelists the British Overseas Territory codes (`ASCN`,
+ * `STHL`, `BBND`, …); those are rare enough to leave to the gazetteer.
  */
 export declare const UK_POSTCODE_PATTERN: RegExp;
 /**

package/out/gb/postcode.js

@@ -27,11 +27,11 @@
  *   internal space, and cleaving outward from inward — not a prefix→admin lookup.
  */
 /**
- * UK postcode shape. A robust, slightly permissive form of the Royal Mail / UK-gov regex: one or
- * two leading letters (the area), a district digit, an optional district letter-or-digit, then the
- * inward sector digit and two unit letters, with the inward space optional so an un-spaced
- * `SW1A1AA` still validates. The full UK-gov pattern additionally whitelists the British Overseas
- * Territory codes (`ASCN`, `STHL`, `BBND`, …); those are rare enough to leave to the gazetteer.
+ * UK postcode shape. A permissive form of the Royal Mail / UK-gov regex: one or two leading letters
+ * (the area), a district digit, an optional district letter-or-digit, then the inward sector digit
+ * and two unit letters, with the inward space optional so an un-spaced `SW1A1AA` still validates.
+ * The full UK-gov pattern additionally whitelists the British Overseas Territory codes (`ASCN`,
+ * `STHL`, `BBND`, …); those are rare enough to leave to the gazetteer.
  */
 export const UK_POSTCODE_PATTERN = /^[A-Z]{1,2}\d[A-Z\d]? ?\d[A-Z]{2}$/i;
 /**

package/out/jp/prefecture.js

@@ -88,7 +88,7 @@ export function isJapanesePrefectureCode(input) {
  *
  * The suffix is only stripped when it is a genuine appendage — separated by a
  * hyphen/space/middle-dot (`Tokyo-to`, `Osaka fu`) or trailing the macron-bearing long-vowel form.
- * That guard is load-bearing: four bare romaji names already END in a suffix syllable (Kyo**to**,
+ * That guard is essential: four bare romaji names already END in a suffix syllable (Kyo**to**,
  * Gi**fu**, Hokkai**do**, Kumamo**to**), and a blind trailing-strip would maim them. We never strip
  * from an unseparated bare name, so `kyoto` stays `kyoto`.
  */

package/out/us/zipcode.d.ts

@@ -32,8 +32,8 @@ export type ZipCodeDigit = 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9;
  *           (City)
  * ```
  *
- * Note that ZIP codes are not truly areas, but rather a group of deliverable addresses, which can
- * and do change over time.
+ * Note that ZIP codes are not areas, but rather a group of deliverable addresses, which can and do
+ * change over time.
  *
  * @category Delivery
  * @category Postal
@@ -59,8 +59,8 @@ export type ZipCode = Tagged<string, "ZipCode">;
  *                (Post Office)
  * ```
  *
- * Note that ZIP codes are not truly areas, but rather a group of deliverable addresses, which can
- * and do change over time.
+ * Note that ZIP codes are not areas, but rather a group of deliverable addresses, which can and do
+ * change over time.
  *
  * @category Delivery
  * @category Postal

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@mailwoman/codex",
-  "version": "4.11.0",
+  "version": "4.13.0",
   "description": "Per-address-system postal reference data + branded types (USPS street suffixes, US ZIP codes). Pure, zero-runtime-dep — the shared canonical home for postal-system primitives the parser, resolver, and synthesis layers all reach for.",
   "license": "AGPL-3.0-only",
   "repository": {