Description
Audit collisions under an explicit NFC plus JavaScript lowercase opaque-key normalization policy; not locale-aware Unicode full casefolding.
An opaque key’s representation can affect equality and ordering even when its underlying value is unchanged. Delimiter joining can be ambiguous, fixed-width padding can preserve numeric order within agreed bounds, and typed length-prefix framing keeps scalar types distinct. Lengths in this family count UTF-16 code units unless a different unit is stated.
Audit collisions under an explicit NFC plus JavaScript lowercase opaque-key normalization policy; not locale-aware Unicode full casefolding.
When to use this tool
Use this tool to audit collisions under an explicit NFC plus JavaScript lowercase opaque-key normalization policy; not locale-aware Unicode full casefolding.
How to use the tool and how it works
- Enter keys using the field definitions below.
- Run the operation. Correct input errors before interpreting an output.
- Read result.collisions. Use the ordering, boundary rules and absence conditions described below.
Normalize each key using NFC and lowercase, then return repeated normalized groups with original indexes.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| keys | Opaque key strings in original order. | Dense list of at most 128 strings, each at most 8,192 UTF-16 code units. |
| Output field | Interpretation |
|---|---|
| result | Object containing the named fields below. |
| result.collisions | Repeated/colliding normalized or joined keys with original indexes. |
{
"input": {
"keys": [
"A",
"a",
"b"
]
},
"output": {
"result": {
"collisions": [
{
"key": "a",
"indexes": [
0,
1
]
}
]
}
}
}Limitations and assumptions
- Normalization can merge distinct spellings; it is not locale-sensitive or a guarantee against confusable identifiers.
- String framing and alphabet digits use UTF-16 code units, not bytes or grapheme clusters. Exact integer text accepts a signed decimal spelling of at most 256 digits before operation-specific range checks.
- Every declared top-level input field is required and unexpected fields are rejected. Ordinary strings are limited to 8,192 UTF-16 code units and lists to 128 entries, with tighter operation-specific bounds where stated. JSON text has bounded nesting and node counts.
- Numeric outputs must be finite and no larger in absolute magnitude than the safe-integer limit; operations returning exact large integers use decimal text. Positions are zero-based and spans end exclusively unless the operation explicitly states a different convention.
Alternative or Complementary methods
Use typed framing when distinct scalar types or tuple boundaries must remain distinguishable. Keep alphabet, width, normalization and numeric bounds consistent between producers and consumers.
References
Similar or alternative tools
- Opaque Key Affix Normalizer
Ensure caller prefix and suffix are present after stripping/reapplying at most one matching affix; repeated inner affixes remain literal data, no recursive stripping or path semantics.
- Opaque Key Alphabet Audit
Audit opaque key UTF-16 code units against an explicit caller alphabet with positions; not Unicode grapheme, entropy or checksum validation.