Docs / Patterns

Patterns

Patterns

A handful of shapes cover most of what people build with Ora. Each links to a worked recipe with real responses.

Fan-out: many questions, one request

Ask every question you might need about a symbol at once, including ones you may not use. Questions are answered independently, so adding one does not change the others. Ask many questions in one request.

Fact gate, then forecast

Use a rule as a filter and a forecast as the trigger: trend >= 0.6 and up_week >= 0.55. The rule keeps the forecast from acting outside the setup it was meant for. Trend filter plus entry trigger, Rules plus forecasts in one request.

Clarity gate

Act automatically only when an answer is clearly away from 0.50, and route the middle to a person. For choice and score, the same idea uses confidence: the ticket recipe's team pick was technical at confidence 0.732. Gate actions on how clear the answer is, Confidence.

Composite score

Split a judgment into several narrow answers and weight them in code, so the weights are yours and can be tested:

w = {"trend": 0.3, "momentum": 0.2, "up_week": 0.3, "drop5": -0.2}
score = sum(w[k] * a[k]["yes_no"] for k in w)   # rank a watchlist by score

Rank, don't threshold

Over a watchlist, the order of the answers is often more useful than any fixed line: take the top five by up_week, or every name whose breakout rule is above 0.6. Rank a watchlist by probability.

Two-sided risk

Ask both directions. A high drop5 and a high rally5 together mean a wide range, not a direction. Two-way risk.

Ask the same thing three ways

Forecast answers can move with wording. Ask the important question in two or three wordings and act on agreement. Self-consistency.

Act server-side

Once the lines work, move them into actions (Slack, signed webhook) and workflows (a watchlist on a schedule, one digest). Send a Slack alert when a rule fires.