Finite Relation Composition Pairs
Compose finite relations by following first then second, coalescing duplicate witnesses into unique endpoint pairs; order convention is explicit.
Description
Compose finite relations by following first then second, coalescing duplicate witnesses into unique endpoint pairs; order convention is explicit.
Relation composition joins through a shared middle element. Direction matters when the two relations differ.
When to use this tool
Compose finite relations by following first then second, coalescing duplicate witnesses into unique endpoint pairs; order convention is explicit.
- Prepare the supplied firstJson, secondJson, universe 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 firstJson, secondJson, universe. 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.pairs. Interpret false, null and empty lists using the distinctions below; they can be valid outputs.
Validate both pair lists on the same unique universe. For each first pair [a,b] and second pair [b,d], emit [a,d] once. The convention applies first, then second.1
| Input field | Meaning and representation | Accepted input |
|---|---|---|
| firstJson | JSON text, entered as one text field. The decoded structure is illustrated below; it is not a separate file. | Text |
| secondJson | JSON text, entered as one text field. The decoded structure is illustrated below; it is not a separate file. | Text |
| universe | universe. | 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": "firstJson",
"decoded": [
[
"a",
"b"
]
]
},
{
"field": "secondJson",
"decoded": [
[
"b",
"c"
]
]
}
]| Output field | Interpretation |
|---|---|
| result | Object containing the named outputs below. |
| result.pairs | The pairs list in the ordering and representation described above. |
{
"input": {
"firstJson": "[[\"a\",\"b\"]]",
"secondJson": "[[\"b\",\"c\"]]",
"universe": [
"a",
"b",
"c"
]
},
"output": {
"result": {
"pairs": [
[
"a",
"c"
]
]
}
}
}Limitations and assumptions
- The result is a set of pairs in first-discovery order. No transitive closure, function totality or alternate composition direction is inferred.
- 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
Declare the full universe and distinguish testing a property from adding its closure. Use separate functionality and totality checks before interpreting a relation as a function.
References
Similar or alternative tools
- Finite Relation Converse Pairs
Form the converse of a supplied finite homogeneous relation, coalescing duplicate input pairs but retaining first-appearance pair order.
- Finite Relation Domain and Image
Return finite homogeneous relation domain and image in explicit universe order; preserve isolated universe elements as absent, not inferred pairs.