Platform documentation

One lifecycle. Every surface accountable.

Web, Telegram, paper trading, broker integrations and analytics must share canonical accounts and signal identifiers while preserving the trust boundary of every action.

SOURCE CODE · CONTRACTS · EVIDENCE

01Accounts

Authenticate and inspect your rights.

The authenticated workspace exposes account-scoped data from the canonical platform API.

Use email sign-in, verification, MFA and account recovery.
Review plan entitlements, notification preferences and saved watchlists.
Treat account status and route permissions as server-controlled.

02Research

Explore received signals and evidence.

The signal history distinguishes a delivered record, its strategy context, lifecycle tracking and eventual outcomes.

Filter delivered signals by asset, class, timeframe and strategy.
Inspect receipt provenance and model context for an entitled signal.
Use paper trading and performance views without confusing them with brokerage results.

03Operations

Review state before acting.

Owners have special diagnostic routes, but an operator UI is not automatically a release control.

Verify actual running commit, migration, data and queue health.
Keep staging isolated while certifying providers, fills and recovery.
Require audit evidence for release gates, kill-switch behavior and parity.

Disclosure. Some capabilities are conditional on an account plan, deployed services and independent financial certification. This page documents intended product relationships, not completed deployment acceptance.

Continue reading: Account plans Open secure account