Two specs declare the type Regex, and the types ratchet has counted it since 2026-09-15 #4275

What is wrong

tri types ratchet reports one name more than its ledger:

ledger 80 name(s), observed 81
  + Regex  NEW conflict

Regex is declared twice:

• specs/tri/search/regex.t27:13 — pub const Regex = struct { (landed 4e57f31, 2026-09-15, "Implement TriRegex module functions with basic regex compilation")
• specs/tri/search/regex_advanced.t27:17 — pub const Regex = struct { (landed f3efbd7, 2026-09-15, two minutes later)

A name with two definitions has no computable domain size: not because the type is infinite, but because which type is undetermined (#2774).

It has been true for three days and nobody saw it, because Corpus Ratchet failed one step earlier on the assertionless ledger (#4270) and never reached this check. That step was fixed in #4271, so this is what the gate reports now.

What to write

specs/tri/search/regex_advanced.t27 declares the advanced module's own types (RegexFlags, RegexMatch, ...). Give its Regex a name of its own — AdvancedRegex is the obvious one — and update every use inside that file. Do not touch specs/tri/search/regex.t27: it owns the plain name.

Acceptance criteria

• 1. grep -c 'pub const Regex = struct' specs/tri/search/regex_advanced.t27 prints 0 (today: 1)
• 2. t27c spec-status specs/tri/search/regex_advanced.t27 prints IMPLEMENTED (today: IMPLEMENTED — it must stay that way)
• 3. t27c gen specs/tri/search/regex_advanced.t27 > /tmp/t27-gen.zig && grep -c 'not yet implemented' /tmp/t27-gen.zig prints 0 (today: 0)
• 4. grep -c 'Regex' specs/tri/search/regex.t27 prints at least 1 — the other file keeps the plain name

Boundary

specs/tri/search/regex_advanced.t27