reverse
Reverse-engineer what the trader POSTED before saying anything about it: a rule in words, a pasted Pine script (read statically, never run) or a chat transcript. Returns a dossier: the route (what it is and the first tool), findings each marked observation, inference or unknown with an id (E1, E2) and what would settle each unknown, the checklist (market, bar size, trigger, direction, stop, target, stand aside, numbers match the tape, run over recorded bars) as answered, partial or unresolved, and the ceiling (hypothesis until rehearsed). A Pine script is also imported by the runner's importer (import: the cubicle.script, or each refused construct with its code, Pine line and why, and the next step). Cite the ids; never present an inference or an unknown as a fact. For an attached chart use the image tool first.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"text": "<text>"
},
"name": "reverse"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| text | Yes | what the trader posted, verbatim: the rule, the Pine source or the transcript |