The Nexural Live Desk · Nexural Server Handbook

The Live Desk is the member-facing record of Sage’s swing posts and the canonical signal ledger. It shows what was said, what the market is doing now, and whether the original plan is still intact—without turning a signal into an instruction to trade.

See the system before it goes live

This preview uses illustrative prices and the same fields as the production feed. It is not connected to a market provider in this local handbook, and none of the cards below represents a current Nexural position.

DEMO STATE

Position intelligence, not trade instruction

Same schema · Illustrative prices · No live provider configured

Illustrative dataFreshness shown per record

Swing book

Tracked positions

2 illustrative records

NXR-ALong

Open

Current44.10

From average+4.5%

Stop: 40.80
Average: 42.20
Target: 47.80
Planned R:R: 4R

InvalidationDaily close below the demand shelf.

Source: #swing-trades
Freshness: Demo
Updated: Example only

NXR-BShort

Needs review

Current116.7

From average+1.44%

Stop: 121.1
Average: 118.4
Target: 110.3
Planned R:R: 3R

InvalidationAcceptance back above the failed breakout.

Source: #swing-trades
Freshness: Demo
Updated: Example only

Canonical ledger

Signal state

2 illustrative records

NQLong

Open

Signal IDSTS-NQ-DEMO-0184

SetupPOC bounce

Timeframe15m → 3m

Quality88/100

Stop: 20,098
Entry: 20,124
Current: 20,161
Target: 20,202

InvalidationThree-minute acceptance below the reclaimed POC.

Source: Canonical signal ledger
Freshness: Demo

ESShort

Closed

Signal IDSTS-ES-DEMO-0185

SetupSupply rejection

Timeframe1h → 5m

Quality82/100

Stop: 5,680
Entry: 5,672.5
Current: 5,659
Target: 5,650

InvalidationAcceptance above the supply zone.

Source: Canonical signal ledger
Freshness: Demo

Educational, read-only tracking. Quotes may be delayed. Confirm the original post, timestamp, source, stop, and invalidation. Never copy a signal blindly.

Where to find a signal and what each surface owns

The fastest route depends on whether you need the original message, the current state, or the history of the system. Use one canonical identifier when you move between them.

Surface	Use it for	What to verify
#swing-trades	Sage’s original swing entry, add, stop, target, or close message.	Author, timestamp, symbol, direction, and whether a newer update exists.
/swings	The currently projected open swing book with available quote context.	Quote source, as-of time, stop, target, review flag, and missing fields.
/signals	Signal performance and symbol-level history for supported markets.	Status, sample size, date window, and the difference between a record and a new setup.
Signal ID	Following one signal across entry, level updates, close, and review.	That every event resolves to the same canonical ID and no later event was missed.
Symbol channels	Market context, member discussion, and follow-up questions around the instrument.	The channel discussion is context—not an amendment to Sage’s original plan.

How a Sage swing becomes a trackable record

The system preserves the difference between the source event and the latest state. That makes corrections, partial information, and later closes auditable instead of silently rewriting history.

01
Sage posts
A message appears in the restricted #swing-trades channel.
02
Parser reads
The tracker identifies an add, average, stop, target, close, or review-needed note.
03
Event is stored
The original change becomes an append-only swing event with time and source.
04
Position is projected
Events resolve into the latest open or closed position state.
05
Quotes enrich
The market-data layer adds provider, price, as-of time, and freshness.
06
Member view renders
A role-gated website proxy exposes only the sanitized read-only fields.
07
Close and review
The final state and process review remain connected to the same record.

Read every card in the same order

A good interface makes uncertainty visible. Read identity and state first, risk second, market-data quality third, and performance last.

Field	Question it answers	Failure check
Status	Is the idea open, closed, cancelled, or waiting for review?	Never treat a closed card as a fresh entry.
Entry / average	Where is the tracked reference price?	An average is not your available fill.
Stop	Where was planned risk bounded?	Missing or widened stops require review.
Target	Where was the planned objective?	A target is a scenario, not a promise.
Invalidation	What market behavior breaks the thesis?	Price can damage a thesis before a hard stop prints.
Source	Which system produced this state?	Follow the original source before trusting a projection.
Freshness	How old is the quote or event?	Stale and unavailable data must remain visibly stale and unavailable.
Signal ID	Which events belong to this decision?	Use it to prevent updates from being confused across trades.

Production access and safety boundary

The bot endpoint is server-to-server only. The member website must proxy it, confirm Discord membership and the required role or tier, and then return the safe view. The website key never belongs in browser JavaScript.

Require Discord sign-in and current server membership before showing the Live Desk.
Apply a documented role or membership-tier policy on the website backend.
Keep WEBSITE_API_KEY and all provider credentials on the server.
Expose no allocations, brokerage details, account balances, raw Discord text, or internal database identifiers.
Show provider, as-of time, quote coverage, and stale or partial states on every response.
Fail closed when membership, credentials, source data, or quote data cannot be verified.
Keep the surface read-only; do not place orders or calculate personalized size.

Next steps

Learn the system behind the state before using the state to inform a decision.

Use the signal workflowTurn a complete signal into your own freshness, thesis, risk, and execution checks.Build a swing planDefine horizon, thesis, catalyst, invalidation, stop, target, and review cadence.Review the processSeparate signal quality, rule adherence, and outcome after the position closes.