Field Guide Key Coupleta Path Resolution Step Tracker
Track explicit binary field-guide couplet decisions; answers must be independently observed and terminal labels are not authenticated species identifications.
Description
Follow a supplied yes/no field-guide key and return the traversed path and current node.
A dichotomous field-guide key is a sequence of choices between paired branches. Tracking a supplied path can preserve those choices without establishing that the observations or identification are correct.
When to use this tool
Follow a supplied yes/no field-guide key and return the traversed path and current node.
- Prepare the supplied nodeIds, yesTargets, noTargets, startNode, answers 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 nodeIds, yesTargets, noTargets, startNode, answers. 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.currentNode, result.terminal. Interpret false, null and empty lists using the distinctions below; they can be valid outputs.
Require aligned nonempty nodeIds/yesTargets/noTargets, distinct nonblank nodeIds and binary zero/one answers. Begin at startNode; for each answer, locate its current node and follow the corresponding yes or no target. Return the complete path, currentNode and terminal true when that label is absent from nodeIds.1
| Input field | Meaning and representation | Accepted input |
|---|---|---|
| nodeIds | node ids. | At most 128 strings, each at most 128 UTF-16 code units |
| yesTargets | yes targets. | At most 128 strings, each at most 128 UTF-16 code units |
| noTargets | no targets. | At most 128 strings, each at most 128 UTF-16 code units |
| startNode | start node. | Text; at most 8,192 UTF-16 code units, subject to the grammar above |
| answers | answers. | List of finite numbers; bounded by the operation |
| Output field | Interpretation |
|---|---|
| result | Object containing the named outputs below. |
| result.path | The path list in the ordering and representation described above. |
| result.currentNode | The current node value under the stated formula or text convention. |
| result.terminal | Flag for terminal under the exact condition described above. |
{
"input": {
"nodeIds": [
"a"
],
"yesTargets": [
"species-x"
],
"noTargets": [
"species-y"
],
"startNode": "a",
"answers": [
1
]
},
"output": {
"result": {
"path": [
"a",
"species-x"
],
"currentNode": "species-x",
"terminal": true
}
}
}Limitations and assumptions
- One means yes and zero means no. An unknown current node is an error only when another answer must be followed; an unmatched target can be terminal. Cycles and unreachable nodes are not rejected, and no fungus, edibility or safe handling is established.
- Every declared top-level field is required and unexpected fields are rejected. Numeric inputs must be finite; ordinary text fields are bounded to 8,192 UTF-16 code units, with tighter operation-specific limits where stated.
- Ordinary string lists have at most 128 entries of at most 128 code units each; numeric lists and matrices have separate bounded size checks. Nonfinite results and excessively large serialized outputs are rejected.
- Indexes are zero-based and spans have an exclusive end unless explicitly stated otherwise. A valid false, null or empty-list result is distinct from malformed input.
Alternative or Complementary methods
Check each observation against the complete qualified field guide and retain the route used to reach a label. Compare terminal labels with independently established identification evidence; a traversed key path does not establish edibility or safe handling.
References
Similar or alternative tools
- aerial substrate layer note generator
Generate a descriptive note for a recorded culture layer observation.
- amatoxin cap assay classifier
Classify a reported amatoxin assay result as a potential lethal-toxin risk. Non-detection does not establish that a mushroom is edible or free of other toxins, and this tool does not replace laboratory or poison-control interpretation.