Literal Enumeration Alias Resolver
Resolve caller-defined enumeration aliases with cycle/path evidence and check the terminal against an explicit allowed bank.
Description
Resolve caller-defined enumeration aliases with cycle/path evidence and check the terminal against an explicit allowed bank.
An enumeration alias chain may resolve to an allowed terminal or enter a cycle. Returning the path makes that distinction reviewable.
When to use this tool
Resolve caller-defined enumeration aliases with cycle/path evidence and check the terminal against an explicit allowed bank.
- Prepare the supplied token, aliasesJson, allowed fields for this operation.
- Compare the complete example with the representation used by your own input before carrying the result into another step.
How to use the tool and how it works
- Enter token, aliasesJson, allowed. Use the exact text syntax, units and index conventions explained below.
- Run the tool. If input validation fails, correct the supplied fields before interpreting any result.
- Read result.path, result.terminal, result.cycle, result.allowed. Interpret false, null and empty lists using the distinctions below; they can be valid outputs.
Parse aliasesJson objects with unique name and target strings. Follow exact aliases from token until a terminal or repeated name. Return path, terminal or null, cycle and whether the terminal belongs to allowed.1
| Input field | Meaning and representation | Accepted input |
|---|---|---|
| token | token. | Text; at most 8,192 UTF-16 code units, subject to the grammar above |
| aliasesJson | JSON text, entered as one text field. The decoded structure is illustrated below; it is not a separate file. | Text |
| allowed | allowed. | List of strings; at most 128 entries |
For the JSON text fields, the following decoded structures show the example records before they are serialized into input strings. Keep field names, list nesting and value types as shown.
[
{
"field": "aliasesJson",
"decoded": [
{
"name": "a",
"target": "A"
}
]
}
]| Output field | Interpretation |
|---|---|
| result | Object containing the named outputs below. |
| result.path | The path list in the ordering and representation described above. |
| result.terminal | The terminal value under the stated formula or text convention. |
| result.cycle | Flag for cycle under the exact condition described above. |
| result.allowed | Flag for allowed under the exact condition described above. |
{
"input": {
"token": "a",
"aliasesJson": "[{\"name\":\"a\",\"target\":\"A\"}]",
"allowed": [
"A"
]
},
"output": {
"result": {
"path": [
"a",
"A"
],
"terminal": "A",
"cycle": false,
"allowed": true
}
}
}Limitations and assumptions
- No case folding or external registry is used. Reaching a terminal does not itself mean allowed is true.
- All declared input fields are required and unexpected top-level fields are rejected. Numbers must be finite; lists are limited to 128 entries and ordinary text fields to 8,192 UTF-16 code units, with tighter limits where stated.
- JSON text inputs must parse within bounded nesting and size limits. Numeric outputs outside the safe finite range are rejected; large exact integer results use decimal strings. Indexes and half-open spans are zero-based unless a rank is explicitly described as one-based.
Alternative or Complementary methods
Use a parser for the actual target format when the task requires CSV, shell, URL, calendar or filesystem semantics. These tools implement the specific small grammars stated here, without adding those surrounding conventions.
References
Similar or alternative tools
- Literal Enumeration Token Check
Check exact membership in a caller-provided literal token enumeration; no case folding, aliases or authoritative vocabulary.
- Balanced Parenthesis Token Splitter
Split a literal delimiter only outside balanced parentheses; parentheses are retained, quotes and escapes have no special meaning.