# Graphs and connections

How a signal becomes a decision, an order or an alert.

Human page: https://docs.orbi.gg/guides/graphs

## Read the graph from left to right

A source observes an event, filters decide whether it qualifies, Open trade creates a position, and exits lead to sell/close actions. Connections carry context; putting two compatible node types next to each other is not enough.

Use one Start and no graph loops. A bot executes at most one active Open trade. Wallet, Aegis, runner and company sources can also be active when their outgoing path joins the active graph; a completely loose draft node stays inert.

## Branches have different meanings

1. Balance Pass can continue into supported candidate paths; Fail must go to Stop bot.

2. Open trade’s successful/filled path can reach position exits. A failed entry can terminate at Skip trade or End, not an exit that assumes a position exists.

3. Notifications attach to successful signals, fills or exit triggers. They do not attach to no/fail/failed branches.

4. Every exit condition needs exactly one Sell position or Close trade action. Notification side branches do not replace that action.

## Keep a complete exit path

Every Open trade needs a reachable Close trade and a direct Time exit → Close trade path to dispose of remaining tokens. Every sell/close action also needs a path to End.

A partial profit-taking branch does not replace the remaining-position safety path. A disconnected exit or a Time exit that only partially sells makes the strategy invalid.

### A basic paper copy workflow

Illustrative template wiring, not a profitability recommendation. Configure your own wallet and review every amount and exit before starting.

- Start → next: Wallet signal

- Wallet signal → Open trade

- Open trade → filled: Profit target; filled: Stop loss; filled: Time exit

- Profit target → yes: Close trade

- Stop loss → yes: Close trade

- Time exit → yes: Close trade

- Close trade → next: End

- End → terminal

[Time exit](https://docs.orbi.gg/nodes/time-exit)

[Close trade](https://docs.orbi.gg/nodes/close-trade)

## Use a graph only for signals

A supported candidate path can end at End without Open trade. It records a qualifying candidate without making an order. This is useful when an Orbi supervises paper entries and exits instead of a deterministic order graph.

### Signal-only workflow

Record qualified candidates without Open trade. An eligible Orbi-supervised paper task can then decide on supported simulated actions.

- Start → Wallet signal

- Wallet signal → Token filter

- Token filter → End

- End → terminal

## Save drafts deliberately

Save the graph after editing. A local or review draft is not the same thing as the saved executable strategy. Keep a graph paused while resolving issues; compare analytics by graph version when evaluating a change.

Node reference connection lists are type-level compatibility. The editor also checks branch, position, plan and complete-path rules. Two instances of the same compatible type are different nodes; a node cannot connect to itself.