BTHEX Signals FAQ

Clear answers about the BTHEX workflow

Understand what BTHEX Signals is, how to read market context, what you control, and how access, plans, and risk boundaries work.

General FAQ for the visible BTHEX stack

This page consolidates product orientation, context reading, execution boundaries, access model, strategy profile, and legal limits so first-time visitors can move through the stack with a clear process.

1. Product Overview

What BTHEX Signals is, what it is not, and who it is built for.

What is BTHEX Signals?

BTHEX Signals is the public layer of the BTHEX trading workflow. It surfaces market context, validation views, and workflow modules used before and during deployment.

Is this a market context platform, a signals service, or a trading bot?

It is a context and workflow product built around licensed strategy infrastructure. It is not a generic signals channel and not a black-box promise product.

Who is it built for?

It is built for traders and teams that want structure: read context, validate history, tune parameters, then deploy with controlled execution.

What makes it different from generic signal channels?

Outputs are organized by context quality, recency, validation depth, and workflow progression. You can move from high-level context to symbol detail, live monitoring, and optimization in one stack.

Is this for manual decision-making or automatic execution?

It is workflow-assisted. You can keep decisions manual or connect execution tooling, but activation, sizing, and risk remain user-controlled.

2. How To Read Context

How to interpret Bias, Ref, Levels, and Risk zone without overreading them.

What does Bias mean?

Bias is regime context, not an entry command. It describes directional posture in the current engine readout.

What is Ref?

Ref is the contextual anchor price used to map progression. It is not a prescribed fill price.

What are Levels L1-L7?

Levels are projection zones used to track contextual progression. They are not blind limit orders.

What is the Risk zone?

Risk zone is contextual invalidation structure. It is not an exchange stop order and does not replace your own risk controls.

Is context output the same as an entry signal or trade order?

No. Context output is informational guidance for decision support. Execution decisions remain separate and user-controlled.

How should I use context in practice?

Use context first to read direction and structure, confirm with symbol-level history, then apply your execution plan with explicit size and risk.

3. User Control And Execution

Who controls entries, account connections, and operational risk.

Do you execute trades for me?

BTHEX provides workflow infrastructure and monitored outputs. It is not discretionary trade execution on your behalf.

Do you manage funds or custody assets?

No. BTHEX does not manage client funds and does not custody exchange balances.

Do you access my exchange or TradingView account by default?

No account is controlled by default. Any integration depends on explicit user-side setup and permissions.

Who decides entry, size, and exit?

You do. BTHEX outputs context and infrastructure, but timing, sizing, and exit decisions stay with the user.

How should I think about context versus execution?

Context pages help decision quality. Execution pages show live operational state. They are complementary, not interchangeable.

4. Markets, Feed, And Refresh States

How to interpret freshness labels, empty tables, and symbol update timing.

What does the Markets page show?

Markets Coverage Board summarizes tracked symbols with current context state, reference readout, snapshot status, and update freshness.

What is latest context?

Latest context is the most recent published engine output available for each symbol or module view.

Why can a page show refreshing or no entries yet?

Refreshing means the board is polling for updates. Empty states usually mean there is no new eligible output yet, or your active filters return no rows.

Why can some symbols look newer than others?

Updates are symbol-dependent. A symbol refreshes when new context or snapshot data is generated for that symbol.

What is a reference snapshot?

A reference snapshot is the latest stored historical/backtest package used for validation context on a symbol.

What should I assume when a table or feed is empty?

Assume no current eligible rows for that view first. Check filters, recency labels, and refresh before treating it as an error condition.

5. Access, Plans, VIP, And History Depth

How access layers work and what changes with plan depth.

How does the trial work?

The public Plans page currently shows a free 7-day Platform Trial entry. Trial and paid activation are handled through register/checkout flow.

What do the plans include?

Layers are positioned as Platform, Platform + Edge, and Full Stack. Higher layers add deeper validation, history depth, and API/integration capabilities.

What is VIP Context?

VIP Context refers to the /vip edge dashboard with deeper reference context, segment history, and account transparency views. Access is plan-gated.

What is the difference between latest context and extended history?

Latest context is current operational readout. Extended history adds longer validation windows, historical segments, and deeper diagnostics.

Do you auto-charge?

Billing cycle and charge terms are defined at checkout. Review checkout details plus Terms before confirming any paid plan.

Can access or history depth be customized?

Yes. The platform presents standard plan layers, and custom team/integration scope can be requested through support.

6. Strategy Operating Profile

Public operating profile, without exposing proprietary internals.

Does the product include a public strategy operating profile?

Yes. The Strategy page documents the operating profile and deployment fit at a high level.

Why use Heikin structure for analysis and standard OHLC for fills?

The public profile states that structure reading uses Heikin, while execution alignment remains anchored to regular OHLC candles.

Is the strategy built mainly for Futures or Spot?

Primary operating fit is Futures. Spot is supported under long-only operating constraints.

Does it support Hedge and One-Way modes?

Yes. Hedge is presented as the primary fit, and One-Way support is explicitly documented.

Why is Spot long-only?

The public operating profile defines Spot deployment as long-only and does not use short-side behavior in that mode.

Does this FAQ reveal proprietary strategy logic?

No. It explains operating boundaries and workflow behavior, not formulas, thresholds, or confidential trigger logic.

8. How The Pages Fit Together

A practical path through the product for first-time and returning users.

What is the difference between Context and Markets?

Context is the current operational readout. Markets is the coverage board for the tracked universe with freshness and snapshot state.

What is the difference between latest context and VIP Context?

Latest context focuses on current output. VIP Context adds deeper reference history, segment-oriented validation, and account transparency views.

What is the difference between context and execution monitoring?

Context explains directional structure and reference map. Live monitor tracks open positions, mark state, and unrealized PnL.

How should I move through the product as a user?

A practical flow is: Home -> Context -> Markets (symbol detail) -> Strategy profile -> Live monitor -> Simulation/Optimize -> Plan selection.

Where do Strategy, Live, Simulation Lab, Edge, and Optimize fit?

Strategy defines operating profile, Live monitors execution state, Simulation Lab compares basket scenarios, Edge deepens diagnostics, and Optimize focuses on parameter exploration.

Where do Routing and Snapshot pages map in this stack?

Simulation routes (/simulation-lab and /copy-trading) map to the basket/routing workspace. Edge analytics are available in /edge for licensed client accounts.