System Requirements Document for trading-analyzer

1. Introduction

trading-analyzer is a trading analysis tool whose single purpose is to tell a trader where to place their entry level, stop loss, and take profit for a market instrument they intend to trade.

The product exists because a self-directed trader about to risk real money needs three exact numbers — not a chart playground, not a portfolio tracker, not a social feed. The analyzer accepts the trader's instrument or market context, runs an AI analysis, and returns the three trade levels as its output. Those three numbers are the entire deliverable.

The audience is a single active human role: the Trader — someone who analyzes a market instrument and needs concrete, actionable trade levels before committing capital. The product is delivered as a first-party web application with a public entry surface, an analysis input surface, and a results surface. No account is required to use the analyzer.

2. System Overview

trading-analyzer is a custom-UI web application backed by a server-side analysis service. The Trader moves through three surfaces:

1. Landing — an anonymous public entry surface that explains what the analyzer does and what it outputs (entry, stop loss, take profit), with a specimen of the three-number output and a primary call to action into the analyzer.
2. Analyzer — accepts the Trader's instrument or market context and initiates the trading analysis.
3. Results — presents the suggested entry level, stop loss, and take profit together after the analysis completes.

The analysis itself is performed by an AI analysis capability invoked by the backend. The Trader supplies the instrument/context; the AI analysis executes; the three levels are then presented. The Trader is the only active human actor. The AI analysis service is a system-side actor, not a persona.

Narrow exclusions (current horizon): No order placement, no brokerage connection, no portfolio or position tracking, no account registration or login, no watchlists, no alerts, no historical trade journal, no social or sharing features, no charting workstation. The product produces three numbers and nothing beyond them.

2a. Product Interpretation and Delivery Boundary

Delivery ownership. The product is a first-party custom web application. All three surfaces — Landing, Analyzer, Results — are application-owned pages. The AI analysis that produces the trade levels runs server-side behind the Analyzer's submit action; the Trader never interacts with the analysis engine directly, only with its result.

Access ownership. All three surfaces are reachable without an account. The Trader's journey is a single continuous session: arrive anonymously, supply an instrument, receive three numbers. Nothing in the accepted behavior requires the Trader to privately own or resume durable state across sessions, and no commitment, entitlement, or value transfer must remain bound to a returning identity. Therefore no identity establishment, verification, or account-management capability is introduced. The Analyzer and Results surfaces are reachable directly and do not gate on authentication.

Current vs. future boundary. Current: the anonymous three-surface analyzer producing entry, stop loss, and take profit from a Trader-supplied instrument or market context. Future (not built now, not in current pages or acceptance): saved analyses, accounts, alerts, broker integration, order execution, and any additional instrument analytics beyond the three levels.

2b. Source Content Inventory

Not applicable — no reference directive in this project declares a content_source.

2c. Page Content and Component Coverage

Landing

• Information / state: Anonymous public entry. Explains the trading analyzer, its intended Trader, and its entry / stop-loss / take-profit output before analysis begins. Displays a single ruled specimen row showing the three-number output format (instrument · entry / stop / target · R:R) as the only place the three numbers appear on this page.
• Primary action: A champagne-filled chamfered call-to-action block pinned beneath the specimen row, routing the Trader into the Analyzer.
• Supporting actions: None beyond the primary CTA; no secondary navigation into unbuilt capabilities.
• Domain entities: Instrument (as specimen label), trade-level triple (entry, stop, target), R:R ratio (as specimen).
• Component responsibilities:
  • Oversized condensed three-line headline ENTRY. STOP. TARGET. set flush-left against a champagne hairline rule, with a teal live-tick dot before the first word.
  • Ruled specimen row in tabular condensed numerals.
  • Right-column stacked instrument rig of three circular gauges (Entry in champagne, Stop in muted steel, Target in teal), each with engraved tick marks and a needle at rest, on raised instrument panels with 1px highlights.
  • Faint topographic contour layer drifting behind the hero at 6% opacity.
  • One expedition-grade monochrome warm-graded ridge-line photograph permitted on the lower band.
• States:
  • Loading: Not applicable — the Landing is static content; no data fetch gates first paint.
  • Empty: Not applicable — the specimen row is fixed illustrative content, not a data-bound collection.
  • Success: Page renders fully; CTA is visible and routes to Analyzer.
  • Error: Not applicable — no runtime data dependency on this surface.
  • Recovery: Not applicable.

Analyzer

• Information / state: The Trader's working surface for supplying the instrument or market context that the analysis requires. Shows the current input state and the readiness of the analysis request.
• Primary action: Submit the instrument/context to initiate the trading analysis.
• Supporting actions: Edit or clear the supplied instrument/context before submitting; re-submit after a failed analysis.
• Domain entities: Instrument / market context (Trader-supplied), analysis request (in-flight state), analysis result (entry, stop loss, take profit).
• Component responsibilities:
  • Ruled left input panel holding the instrument/context field, aligned to the 8px baseline grid.
  • Right gauge column showing the live market readout context for the supplied instrument.
  • Instrument micro-labels (11px uppercase Saira, +0.18em tracking) with a 1px champagne rule above the panel.
  • Submit control that initiates analysis.
• States:
  • Loading: Analysis in flight — the submit control reflects the pending request and the Trader cannot double-submit the same request.
  • Empty: No instrument/context supplied yet — the submit action is unavailable until the Trader provides one.
  • Success: Analysis completes and the Trader is taken to the Results surface showing the three levels.
  • Error: The analysis fails or returns no usable levels — the Trader is told the analysis did not produce levels and remains on the Analyzer with the supplied instrument/context preserved.
  • Recovery: The Trader can correct the instrument/context or re-submit the same request without re-entering everything from scratch.

Results

• Information / state: The three suggested trade levels — entry level, stop loss, and take profit — presented together as the output of the completed analysis, alongside the instrument they apply to.
• Primary action: Read the three levels and the supporting R:R and position-size readout.
• Supporting actions: Return to the Analyzer to run another analysis on a different instrument or context.
• Domain entities: Entry level, stop loss, take profit, instrument, R:R ratio, position size.
• Component responsibilities:
  • Three-gauge horizontal instrument rig: Entry (champagne), Stop (muted steel), Target (teal), each a circular bezelled dial with engraved ticks and a needle that sweeps to its value.
  • Ruled R:R and position-size ledger beneath the gauge rig, numbers flush-right in tabular columns.
  • Vertical price-axis ladder on the far right: a gauge strip from stop to target with the entry line marked in champagne and the R:R ratio engraved beside it.
  • Instrument micro-labels above each panel.
• States:
  • Loading: Not applicable on arrival — the Results surface is reached after analysis completes; if the Trader returns to it while a new analysis is pending, the pending state is shown rather than stale numbers.
  • Empty: No analysis result available for the current context — the Trader is directed back to the Analyzer to supply an instrument/context.
  • Success: All three levels render together with the R:R and position-size readout; needles sweep to value and numerals count up.
  • Error: The analysis produced no usable levels — the Trader is told so and offered the route back to the Analyzer.
  • Recovery: Return to the Analyzer, adjust the instrument/context, and re-run; the previous result is not silently presented as current.

3. Functional Requirements

FR-1 — Produce the three trade levels As a Trader, I should receive a suggested entry level, stop loss, and take profit from the analyzer, so that I know where to place my trade.

• Provenance: explicit
• Trigger/input: The Trader supplies an instrument or market context and initiates analysis.
• Observable result: All three levels — entry level, stop loss, take profit — are presented together as the analysis output.
• Access state: No account required.
• Failure/recovery: If the analysis yields no usable levels, the Trader is told the analysis did not produce levels and can adjust the instrument/context and re-run.
• Continuation: The Trader reads the three levels and may run another analysis.

FR-2 — Three levels are the complete output As a Trader, I should see exactly the entry level, stop loss, and take profit as the analyzer's output, so that the result is unambiguous and immediately actionable.

• Provenance: explicit
• Trigger/input: A completed analysis.
• Observable result: The output consists of the three trade levels; no additional trade recommendation categories are presented as the analyzer's output.
• Access state: No account required.
• Failure/recovery: If fewer than three levels can be produced, the result is presented as a failed analysis rather than a partial recommendation.
• Continuation: The Trader uses the three levels to plan the trade.

FR-3 — Supply instrument or market context As a Trader, I should provide the instrument or market context I want analyzed, so that the analyzer can produce levels for the market I actually intend to trade.

• Provenance: required_inference
• Trigger/input: The Trader enters or selects the instrument/market context on the Analyzer surface.
• Observable result: The supplied instrument/context is held as the subject of the analysis request and is shown back to the Trader.
• Access state: No account required.
• Failure/recovery: If no instrument/context is supplied, the analysis cannot be initiated; the Trader is prompted to provide one.
• Continuation: With a valid instrument/context, the Trader initiates analysis.

FR-4 — AI analysis executes before levels are presented As a Trader, I should have the analysis run before any levels are shown, so that the numbers I see are the product of an actual analysis rather than a placeholder.

• Provenance: required_inference
• Trigger/input: The Trader initiates analysis with a supplied instrument/context.
• Observable result: The analysis executes server-side; the three levels are presented only after it completes.
• Access state: No account required.
• Failure/recovery: If the analysis fails or times out, the Trader is informed and the supplied instrument/context is preserved for retry.
• Continuation: On success, the Trader is taken to the Results surface; on failure, the Trader remains on the Analyzer to retry.

FR-5 — Understand the product before analyzing As a Trader, I should understand what the analyzer does and what it outputs before I start, so that I can decide whether to use it.

• Provenance: required_inference
• Trigger/input: The Trader arrives at the public Landing surface.
• Observable result: The Landing explains the analyzer, its intended Trader, and its entry / stop-loss / take-profit output, and offers a route into the Analyzer.
• Access state: Anonymous — no account required.
• Failure/recovery: Not applicable — static content with no runtime data dependency.
• Continuation: The Trader proceeds to the Analyzer.

FR-6 — Read the levels with supporting readout As a Trader, I should see the three levels together with the instrument they apply to and the supporting R:R and position-size readout, so that I can judge the trade before committing capital.

• Provenance: required_inference
• Trigger/input: A completed analysis.
• Observable result: Entry, stop, and target are shown together with the instrument, the R:R ratio, and the position-size readout.
• Access state: No account required.
• Failure/recovery: If no result is available for the current context, the Trader is directed back to the Analyzer rather than shown stale numbers.
• Continuation: The Trader returns to the Analyzer to analyze another instrument or context.

4. User Personas

Trader

Product context. The Trader is a self-directed market participant who is about to risk real money on a single instrument. They are not looking for a research terminal or a charting workstation; they are looking for the three numbers that turn an intention into an order they can place. Their working moment is short and consequential: they have already decided what to trade and need to know where.

Primary goal. Obtain a concrete entry level, stop loss, and take profit for the instrument they intend to trade, and understand the relationship between those three numbers well enough to commit capital.

Distinct accepted responsibilities.

• Supplying the instrument or market context that the analysis will operate on (FR-3).
• Initiating the analysis and waiting for it to complete (FR-4).
• Reading and interpreting the three returned levels together with the instrument, R:R ratio, and position-size readout (FR-1, FR-2, FR-6).
• Deciding whether to act on the levels, and returning to run another analysis on a different instrument or context (FR-6).

Relevant inputs or decisions. The instrument or market context; the decision to initiate analysis; the decision to accept, reject, or re-run the result.

Interactions with other accepted participants. The Trader is the only active human actor. The AI analysis service is a system-side actor that the Trader triggers and whose output the Trader consumes; the Trader never interacts with it directly.

Observable success. The Trader sees all three levels — entry, stop loss, take profit — presented together for the instrument they supplied, with the R:R and position-size readout, and can act on them or run another analysis.

What makes this role's work different. The Trader's work is a single decision under risk, not an ongoing management task. There is no portfolio to maintain, no history to curate, no collaboration to coordinate. The entire value of the product is delivered in the moment the three numbers appear, which is why the product's output is a set of instrument readings rather than a workspace.

5. Core User Flows

Flow 1 — Understand the product and begin (Trader)

1. The Trader arrives at the Landing surface anonymously, with no account and no prior session.
2. The Trader reads the oversized ENTRY. STOP. TARGET. headline and the ruled specimen row showing the three-number output format (XAUUSD · 1.0842 / 1.0791 / 1.0955 · R:R 1:2.4), and sees the three resting gauges in the instrument rig.
3. The Trader understands that the analyzer outputs an entry level, a stop loss, and a take profit for a supplied instrument.
4. The Trader activates the champagne call-to-action block beneath the specimen row.
5. Observable result: The Trader is on the Analyzer surface, ready to supply an instrument.
6. Next step: Flow 2.

Flow 2 — Supply an instrument and run the analysis (Trader)

1. The Trader is on the Analyzer surface with no instrument supplied; the submit action is unavailable.
2. The Trader enters the instrument or market context they intend to trade into the ruled left input panel.
3. Observable result: The supplied instrument/context is held as the subject of the analysis request and shown back to the Trader; the submit action becomes available.
4. The Trader initiates the analysis.
5. Observable result: The analysis request is in flight; the submit control reflects the pending request and the Trader cannot double-submit the same request.
6. The AI analysis executes server-side on the supplied instrument/context.
7. On success: The Trader is taken to the Results surface. Next step: Flow 3.
8. On failure: The Trader is told the analysis did not produce levels and remains on the Analyzer with the supplied instrument/context preserved. Recovery: the Trader corrects the instrument/context or re-submits the same request without re-entering everything from scratch, returning to step 4.

Flow 3 — Read the three levels and decide (Trader)

1. The Trader arrives at the Results surface after a completed analysis.
2. Observable result: The three-gauge instrument rig renders — Entry in champagne, Stop in muted steel, Target in teal — and each needle sweeps from rest to its value over 700ms with a precise cubic-bezier(.2,.8,.2,1), while the numerals count up in tabular figures.
3. The Trader reads the three levels together with the instrument they apply to.
4. The Trader reads the ruled R:R and position-size ledger beneath the gauge rig, and the vertical price-axis ladder on the far right with the entry line marked in champagne and the R:R ratio engraved beside it.
5. Observable result: The Trader has the entry level, stop loss, take profit, R:R ratio, and position-size readout for the supplied instrument, and can judge the trade.
6. Next step: The Trader acts on the levels, or returns to the Analyzer to analyze another instrument or context (Flow 2, step 2).

Flow 4 — No result available for the current context (Trader)

1. The Trader reaches the Results surface with no analysis result available for the current context.
2. Observable result: The Trader is shown an empty state directing them back to the Analyzer; no stale numbers are presented as current.
3. The Trader returns to the Analyzer.
4. Recovery: The Trader supplies or adjusts the instrument/context and re-runs the analysis (Flow 2, step 2).

6. Visuals Colors and Theme

The creative direction is authoritative for this section. Muse: MARQ by Garmin — luxury instrument aesthetic. Headline: Precision luxury instrument for a trader's three numbers. The screen is a cockpit; the three outputs are gauges. Dark, low-glare, macro-material, expedition-serious.

Colour tokens (dark mode):

Typography:

• Headings: Barlow Condensed 500–600, uppercase, tracking +0.04em, 0.92 leading.
• Numerals: tabular form at display scale, so 1.0842 reads as an engraved dial value.
• Body: Saira 300–400 at 16–18px, 1.65 leading.
• Micro-labels: Saira 500 uppercase, +0.18em tracking, 11px fixed (ENTRY / STOP / TARGET / R:R).
• Scale: 1.25 modular on a 12/14/16/20/26/34/48/72/112 rhythm — display clamp(56px, 11vw, 128px), section head clamp(28px, 4.4vw, 48px), instrument numeral clamp(34px, 6vw, 72px), body clamp(15px, 1.6vw, 17px), micro-label 11px fixed.

Shape language: Instrument geometry — circular gauge bezels with a 1px champagne inner ring, ruled data rows with hairline dividers, chamfered panel corners at 6px (not pill, not blob), tick marks every 8px along gauge arcs. Zero soft shadows; depth comes from a single 1px top highlight (#2A2F35) and a darker 1px bottom edge, like machined aluminium.

Layout: Full-bleed dark cockpit on an 8px baseline grid; numbers flush-right in tabular columns. Landing: left 7 columns hold the oversized condensed headline and the three-level specimen; right 5 columns hold the stacked instrument rig. Analyzer: two-column instrument bay — inputs in a ruled left panel, live market readout in a right gauge column. Results: three-gauge horizontal rig with a ruled R:R and position-size ledger beneath, plus a price-axis ladder on the far right.

Imagery: No stock traders, no candlestick clip art as decoration. Macro material surfaces (brushed titanium, sapphire bezel edge, engraved tick plates) as full-bleed crops; a faint topographic contour line layer behind the hero at 6% opacity; the product's own data rendered as dial arcs and a price ladder. One expedition-grade photograph (ridge line at dusk, monochrome, warm-graded) permitted on the Landing's lower band.

Forbidden: The generic indigo/blue-on-white SaaS template look; blue or indigo primary/accent on a white ground; Inter, Roboto, Poppins, DM Sans, or any rounded friendly sans for headings or data; cards with hover-lift shadows, gradient-blob heroes, pill buttons; candlestick or line-chart clip art as decoration; stock photography of people at desks; bouncy or overshooting easing, confetti, or celebratory micro-animations on a money decision; green/red profit-loss colouring as the dominant scheme.

7. Signature Design Concept

The three-gauge instrument rig. The product's output is a dashboard of instruments, never a card grid. On the Results surface, Entry, Stop, and Target are rendered as three circular bezelled dials sitting side by side on raised #15181C panels with 1px #2A2F35 highlights. Each dial carries engraved tick marks every 8px along its arc and a 1px champagne inner ring. Entry's needle and arc are champagne (#C9A24A), Stop's are muted steel, and Target's are teal (#2FB6A6) — the single instrument signal, used only for state. On analysis completion each needle sweeps from rest to its value over 700ms with a precise cubic-bezier(.2,.8,.2,1) — no bounce, no overshoot — while the numerals count up in tabular condensed figures.

Beneath the rig, a ruled R:R and position-size ledger reads out in flush-right tabular columns, and on the far right a vertical price-axis ladder runs from stop to target with the entry line marked in champagne and the R:R ratio engraved beside it. Above every panel, an 11px uppercase Saira micro-label at +0.18em tracking sits under a 1px champagne rule, so the UI reads like bezel engraving rather than a web form.

The same rig appears at rest on the Landing surface in the right 5 columns, needles at zero, as the visual promise of what the analyzer returns. The concept recomposes only accepted content — the three levels, the instrument, the R:R and position-size readout — and introduces no new behaviour, page, or destination.

8. Interaction Model & Motion Direction

Interaction Model: Animated Motion Tempo: cinematic Hero Dimensionality: dimensional_css

Landing Hero Motion Brief

• Focal subject: The stacked instrument rig of three circular gauges (Entry in champagne, Stop in muted steel, Target in teal) on raised panels, paired with the oversized condensed three-line headline ENTRY. STOP. TARGET. set flush-left against a champagne hairline.
• Input → transformation → outcome thesis: The Trader's arrival is the input; the resting needles and the ruled specimen row (XAUUSD · 1.0842 / 1.0791 / 1.0955 · R:R 1:2.4) are the transformation that shows what the analyzer produces; the outcome is the Trader's understanding that this tool returns three exact numbers, and their activation of the champagne CTA into the Analyzer. No accepted behaviour is added — the hero only presents the product's own output format.
• Motion vocabulary: Needle sweeps and counting numerals only. A slow 24s ambient drift of the topographic contour layer at 6% opacity behind everything. Hover on a gauge raises its bezel ring brightness — no lift, no scale. No bounce, no overshoot, no confetti.
• Composed first frame: Full-bleed #0B0D0F graphite cockpit. Left 7 columns: a champagne hairline rule, then ENTRY. STOP. TARGET. stacked on three lines at clamp(56px, 11vw, 128px) in Barlow Condensed uppercase, spanning edge-to-edge, with a teal live-tick dot before the first word. Beneath it, the single ruled specimen row in tabular condensed numerals at 34–48px. Right 5 columns: the three-gauge rig at rest on #15181C panels with 1px highlights. The champagne chamfered CTA block sits pinned beneath the specimen row with black text and no glow. The topographic contour layer drifts behind at 6% opacity.
• Reduced-motion state: With prefers-reduced-motion, the ambient topographic drift stops and the needles hold at their resting positions; the headline, specimen row, gauges, and CTA render as a static composed frame. All readable text and controls remain whole and inside the viewport at 375px, 768px, and 1280px, wrapping or scaling via clamp(...) as needed.

9. Non-Functional Requirements

NFR-1 — Analysis latency and feedback. The analysis executes server-side and the Trader must receive visible in-flight feedback from the moment analysis is initiated until the three levels are presented or a failure is reported. Provenance: required_inference — the Trader must not be left without a state indication while the AI analysis runs. Rationale: the product's value is delivered at the moment of result; an unacknowledged wait is indistinguishable from a broken tool.

NFR-2 — No double submission. While an analysis request is in flight, the same request cannot be submitted twice from the Analyzer. Provenance: required_inference. Rationale: duplicate in-flight analyses on the same instrument/context produce ambiguous results and waste the analysis capability.

NFR-3 — Input preservation on failure. When an analysis fails, the Trader's supplied instrument/context is preserved on the Analyzer so the request can be corrected or re-submitted without re-entry. Provenance: required_inference. Rationale: recovery must be usable; forcing re-entry of the instrument on every failure makes the failure path punitive.

NFR-4 — No stale results presented as current. The Results surface must not present a previous analysis's levels as the result for the current context. Provenance: required_inference. Rationale: the Trader is about to risk real money on these numbers; presenting stale levels as current is a materially harmful failure.

NFR-5 — Readable text and controls at every viewport. Headlines, wordmarks, labels, numbers, and controls stay entirely inside the viewport and their container at 375px, 768px, and 1280px, wrapping or scaling (for example font-size: clamp(...) with its mobile size) to fit, with no other element covering any part of them. Imagery, decoration, and motion may be cropped, bled off an edge, rotated, overlapped, or cut as the creative direction asks, provided they cover no readable text or control. Provenance: explicit (creative direction constraint).

NFR-6 — Reduced-motion support. With prefers-reduced-motion, a usable static arrangement is provided: the ambient topographic drift stops, needles hold at rest, and any moving or scrollable content wraps into rows or allows horizontal scrolling so each item can be brought fully into view. Provenance: explicit (creative direction constraint).

NFR-7 — Anonymous access. No account, registration, login, or identity verification is required to reach the Landing, Analyzer, or Results surfaces or to run an analysis. Provenance: required_inference — no accepted behaviour requires durable actor-specific state, a commitment, or a value transfer bound to a returning identity.

10. Tech Stack

• Frontend: React (custom UI, single-page application with the three surfaces: Landing, Analyzer, Results).
• Backend: Python / FastAPI — a single shared backend service hosting the analysis endpoint that accepts the Trader's instrument/market context and returns the entry level, stop loss, and take profit.
• AI analysis: The smc-ict-fibonacci-trading-assistant skill (analyze-market operation) is the analysis capability invoked by the backend to produce the three trade levels from the supplied instrument/context.
• Storage: No durable product storage is required for the current horizon — analyses are session-scoped and no account-bound state is retained.
• Deployment: Docker / docker-compose for the frontend and backend services. Kubernetes is not required at the current scope.

11. Assumptions and Constraints

Assumptions

• A-1 [Assumption — required_inference] The Trader supplies an instrument or market context before analysis can produce the three levels. This is the minimum input needed to make the accepted journey executable and does not introduce a new product capability.
• A-2 [Assumption — required_inference] The AI analysis executes server-side and completes before the three levels are presented; the Trader interacts only with the input and the result, never with the analysis engine directly.
• A-3 [Assumption — required_inference] The three levels are presented together as a single result set for one instrument/context; the product does not compare or rank multiple instruments.
• A-4 [Assumption — required_inference] The R:R ratio and position-size readout shown alongside the three levels are derived from the three levels themselves and the supplied instrument/context, not from a separate Trader-supplied risk parameter.
• A-5 [Assumption — required_inference] No account is required; the Trader's journey is a single continuous anonymous session.

Constraints

• C-1 [Constraint — explicit] The analyzer's output is the entry level, the stop loss, and the take profit. No additional trade recommendation categories are presented as the analyzer's output.
• C-2 [Constraint — explicit] The product is a trading analyzer that tells the Trader where to place their entry level, stop loss, and take profit — nothing beyond that scope is built in the current horizon.
• C-3 [Constraint — explicit, creative direction] The generic indigo/blue-on-white SaaS template is forbidden. Blue or indigo primary/accent on a white ground, Inter/Roboto/Poppins/DM Sans for headings or data, cards with hover-lift shadows, gradient-blob heroes, pill buttons, candlestick or line-chart clip art as decoration, stock photography of people at desks, bouncy or overshooting easing, confetti or celebratory micro-animations on a money decision, and green/red profit-loss colouring as the dominant scheme are all excluded.
• C-4 [Constraint — explicit, creative direction] Readable text and controls stay whole at every viewport; imagery, decoration, and motion may be cropped, bled, rotated, overlapped, or cut as the direction asks, provided they cover no readable text or control. Where the direction asks readable text or a control to be cropped, clipped, covered, or run off an edge, the text/control stays whole and the gesture is carried with imagery or decoration instead.
• C-5 [Constraint — explicit, creative direction] Motion is needle sweeps and counting numerals only, at 700ms with cubic-bezier(.2,.8,.2,1), no bounce and no overshoot; the ambient topographic drift is 24s at 6% opacity; hover on a gauge raises bezel ring brightness with no lift and no scale.

Future (not current — excluded from current pages and acceptance)

• Saved analyses and analysis history.
• Accounts, registration, login, and any identity-bound state.
• Alerts and notifications.
• Brokerage connection and order placement.
• Portfolio and position tracking.
• Watchlists.
• Social or sharing features.
• Charting workstation capabilities.
• Any instrument analytics beyond the three trade levels.

12. Glossary

• Analyzer — The application surface where the Trader supplies an instrument or market context and initiates the trading analysis.
• Entry level — The price at which the Trader is advised to enter the trade; one of the three analyzer outputs.
• Instrument / market context — The market the Trader intends to trade, supplied to the analyzer as the subject of the analysis request.
• Landing — The anonymous public entry surface explaining the analyzer, its intended Trader, and its three-number output.
• Position size — The readout shown alongside the three levels, derived from the levels and the supplied instrument/context.
• R:R ratio — The risk-to-reward ratio shown alongside the three levels, derived from the entry, stop, and target.
• Results — The application surface presenting the suggested entry level, stop loss, and take profit together after analysis.
• Stop loss — The price at which the Trader is advised to exit a losing trade; one of the three analyzer outputs.
• Take profit — The price at which the Trader is advised to exit a winning trade; one of the three analyzer outputs; also referred to as the target.
• Trader — The single active human role in the product: a self-directed market participant who analyzes an instrument and needs concrete trade levels before committing capital.
• Trade levels — The three analyzer outputs collectively: entry level, stop loss, and take profit.