Opaque Key Width Audit

Description

Audit exact UTF-16 opaque key width without trimming or number coercion; no identity validity, entropy or byte-width claim.

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 exact UTF-16 opaque key width without trimming or number coercion; no identity validity, entropy or byte-width claim.

When to use this tool

Use this tool to audit exact UTF-16 opaque key width without trimming or number coercion; no identity validity, entropy or byte-width claim.

How to use the tool and how it works

Enter keys, width using the field definitions below.
Run the operation. Correct input errors before interpreting an output.
Read result.violations. Use the ordering, boundary rules and absence conditions described below.

Compare each key’s UTF-16 length with the required width and return mismatched original indexes and lengths.^[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.
width	Required UTF-16 width or decimal padding width under the stated operation.	A finite safe integer within the operation’s stated bounds.

Output field	Interpretation
result	Object containing the named fields below.
result.violations	Original key positions and lengths or disallowed code units, as specified above.

json

{
  "input": {
    "keys": [
      "ab",
      "a",
      "abc"
    ],
    "width": 2
  },
  "output": {
    "result": {
      "violations": [
        {
          "index": 1,
          "length": 1
        },
        {
          "index": 2,
          "length": 3
        }
      ]
    }
  }
}

Limitations and assumptions

Width is not a UTF-8 byte count, Unicode grapheme count or display-column count.
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

Tool behavior and example: Opaque Key Width Audit — tool.io

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.