# NoahAI v3.9.1.17 Strategy Studio source-candidate boundary

Date: 2026-09-01
Status: source candidate; not the stable public Windows release

## AI mentor and service roles

- The structured eight-question AI mentor runs inside the NoahAI Client Strategy Studio.
- Its two or three candidates are educational drafts loaded into the source input area.
- A candidate is not automatically saved, approved, historically validated, run in PAPER, or applied to LIVE.
- daltrading operates member-controlled strategy submission, review, discovery, passports, downloads, and acquisition licenses.
- NoahAI Labs explains the product and technical boundary and links users to the client and strategy hub. Neither website automatically collects private Strategy Studio drafts.

## Strategy semantic gates in the source candidate

- A confirm strategy with an explicit LONG or SHORT direction cannot approve the opposite NoahAI candidate.
- A dual-direction strategy must preserve separate LONG and SHORT entry branches or remain blocked for clarification.
- Supported Pine aliases are resolved; unresolved entry-condition variables cannot leave only an unconditional direction.
- TP/SL require explicit units. Unitless values are not guessed as percentages.
- Stored, PAPER, and order boundaries share TP 0.05-5%, SL 0.05-3%, position size 1-50%, leverage 1-10x, and signal threshold 0-1. Out-of-range user values are rejected rather than silently clamped.
- Final edited rules are revalidated by the local service immediately before a new inactive version is saved.

These gates do not make NoahAI fully compatible with every Pine program. User functions, arrays, external data, and unsupported order-state logic remain clarification or unsupported cases.

## Validation and reconciliation boundary

- Crypto historical replay follows the selected execution market: Upbit/Bithumb KRW spot and Binance/Bybit/OKX/Bitget USDT futures.
- Bithumb uses the public 30-minute interval available to this integration; the other crypto venues use 15-minute candles.
- Validation records venue, spot/futures market type, interval, and quote currency.
- PAPER and LIVE, venue or broker, strategy version, and currency remain separate. KRW and USDT are not added into one PnL total without an explicit exchange-rate basis and timestamp.
- Today, week, month, and recent-hour report detail uses the same confirmed-close ledger as the summary. Count, currency PnL, and fee checksum mismatches must be shown as reconciliation failures.

## Release boundary

Passing source tests and web builds does not publish v3.9.1.17. A stable claim requires a Windows installer, embedded engine, blockmap, `latest.yml`, and `release-manifest.json` with the same version and `publish_ready=true`, followed by install/update/restart and venue-specific PAPER validation.