Skip to main content
Every Hizz strategy is a composition of small, deterministic modules. The graph is generated from that strategy’s actual engine and manifest; it is not a shared set of decorative layers. Each module has typed input/output ports, a constrained JSON parameter schema, and a runtime implementation. The same definition is compiled for backtesting and agent execution.

Open the visual workbench

Inspect a complete strategy as a Houdini/Grasshopper-style node graph. Select a node to see its actual parameters and highlight its immediate upstream and downstream connections. On desktop, drag any node to rearrange the canvas; typed cables update with it.

​
Directional pipeline

Triggers emit long, short, or none. Filters independently allow or reject each side. The risk block builds protective exits, sizing converts the approved intent into margin/notional, and execution creates safe order intents.

​
Approved module catalog

​
Data

​
Signals

​
Filters

​
Risk, portfolio, and execution

The live registry is available at:

​
Engine-specific graphs

Different engines use different node sets and contracts. Strategies only share a module when they really share that runtime primitive. Every returned graph edge identifies source, sourcePort, target, targetPort, and dataType. Compilation rejects a missing port or a mismatched type instead of drawing an invalid cable. In the workbench, hover a node for its responsibility; select it for parameters, typed ports, and immediate connections. The API response is canonical and includes complete property descriptions, bounds, enumerations, examples, and port data types. Prefer it over copying this summary into an AI system prompt.

​
Composition rules

  • Exactly one trigger and one risk block are required
  • Zero or more filters are combined as gates
  • Every referenced base, mid, or high timeframe must exist in data.frames
  • Fast periods must be lower than corresponding slow periods
  • At least one of allowLong or allowShort must be true
  • riskFraction is a margin allocation fraction, not a guaranteed loss cap
  • feeBps is per fill; published maker strategies may instead preserve separate maker/taker costs
  • Arbitrary code, imports, callbacks, webhooks, and shell commands are not valid modules