Trader workspace
Mayospell becomes useful when the platform is the trader's daily room, not just a checkout confirmation page.
Platform
The software has to feel as real as the challenge ladder.
Mayospell is more than a pricing page. Traders work inside one room that shows the scorecard, rules, review flow, and next payout gate together.
Mayospell software snapshot: July 5, 2026. A Mayospell product snapshot covering account state, performance review, journaling, seat routing, bracket controls, API access, data add-ons, and incident workflow.
Review-first execution
An options desk needs tagging, playbook attribution, and reviewer notes attached to every trade if it wants to graduate traders toward real risk.
Payout visibility
The platform should make payout lanes, qualifying days, best-day concentration, and reset status visible without forcing a trader to guess.
Software map
This is the Mayospell platform layer, shown in public.
The platform story is concrete: account state, options automation, review evidence, and support posture live beside the program rules.
Surface
Room capability
Mayospell
Why it matters
Account board
The Mayospell room keeps the selected seat, buying power, realized and open P&L, and rule state together.
Mayospell pins buying power at risk, premium deployed, DLL state, structure permissions, and seat-review status at the top of the options desk.
The trader should know their live rule posture before they click into a chain or place an order.
Performance dashboard
The Mayospell room exposes performance stats, trade log, journal entries, calendar P&L, and export tools.
Mayospell keeps fills, screenshot review, playbook tags, options structure notes, and exportable cycle history in the same room.
An options prop product needs process review, not only an equity curve.
Risk controls
The Mayospell room includes account lockout and account-level profit and risk bracket controls.
The options room adds manual lockout, per-structure bracket defaults, event lockouts, and premium-at-risk caps before orders leave the room.
Discipline tools have to be interactive or they become empty marketing.
Multi-account scaling
Seat routing links an approved lead seat to eligible follower seats; any future live seat remains excluded by policy.
Mayospell uses seat-stack routing with catalyst-overlap warnings and options-specific concentration controls across seats.
Scaling is where the interior starts feeling like a prop desk instead of a single-account app.
Automation
Mayospell API access is a separately billed developer lane, and local automations remain the member's responsibility.
Mayospell supports local automations, alert relays, custom risk checks, and journal sync while keeping third-party code outside desk support.
A serious desk product needs a credible developer lane with clear guardrails.
Data ladder
Baseline options quotes are included; advanced depth and flow tools are separate add-on lanes.
Baseline options chains and greeks are included, with paid upgrades for depth, flow, volatility surfaces, or advanced event tooling.
Software monetization in this category does not end at the challenge fee.
Practice and support
Every active combine has an options practice lane, and platform incidents begin with a stop-and-document workflow.
Mayospell pairs every active combine with an options sandbox plus a visible incident workflow that captures order IDs, screenshots, and reviewer notes.
Trust grows when the recovery path is operational instead of informal.
Core modules
A serious options platform needs these rooms from day one.
Mayospell gets more credible when the combine, funded seat, review queue, and research surface all live inside one operational workspace.
Command board
- Live combine or funded-seat status with loss-floor tracking
- Daily loss lock state, flatten warnings, and event restrictions
- Payout lane counters, best-day concentration, and request readiness
Options lab
- Quick symbols for SPY, QQQ, NVDA, and TSLA plus manual ticker search
- Long-option contract discovery with call and put ladder navigation
- Top-of-book quotes, latest prints, starter Greeks, selected underlying quote, and manual limit premium
Review system
- Server-recorded fills, exits, and size progression in the activity drawer
- Deterministic scorecard and risk state; staffed annotations and playbook permissions are not launch controls
- Account-bound reset, progression, and payout request routes outside the terminal
Payout and progression
- Standard versus consistency request lanes in one panel
- Funded-seat history with payout resets and re-qualification markers
- Funded progression readiness tied to the server scorecard, not a live-allocation promise
Desk controls
The public product also documents the control surface.
Mayospell earns trust when traders can tell exactly what the room will let them do on day one.
Reviewed limit-order lifecycle
The desk saves one-click profit and risk presets for long premium, debit spreads, and staged exits by structure type.
Discipline switches that actually work
Account lockout, event bans, same-day expiry limits, and premium caps are active controls inside the desk rather than reminders in a FAQ.
Seat-stack operating system
Multiple combines and funded seats need one routing layer for lead-seat execution, payout readiness, reset state, and cross-seat risk before the trader tries to scale.
Review, export, and escalation
The room exports fills, preserves screenshots, tracks exceptions, and shows exactly how a support or review ticket moves when a ruling is needed.
Workstation tour
The public platform page shows the actual Mayospell trading workstation.
This is the bridge between challenge copy and the member interior: the visitor can see the seat-aware ticket, chain, depth strip, and execution audit before signing up.
Account-safe order ticket
The terminal confirms lane, account ID, seat ID, contract, side, quantity, and limit premium before routing. A changed account invalidates the staged review.
Catalog, chain, and top of book
A trader can move from watchlist to options chain to depth context in one strip, keeping the decision and execution surfaces together.
Orders, positions, and fills
Open positions, working and completed orders, recent fills, cancel or replace actions, and close-position controls sit beside the ticket.
Scorecard and incident truth
The terminal shows pass criteria, high-water equity, trailing floor, daily loss, concentration, and durable breach state. It does not pretend to auto-capture screenshots or a support bundle.
Layer
Room contract
Mayospell room
Visible proof
Order entry
Seat selection, keyboard actions, bracket controls, and fast order entry are core Mayospell room behaviors.
Long-option limit ticket with buy-to-open, sell-to-close, exact-account review, tier contract caps, replace, cancel, and close.
The authenticated /trade terminal routes every mutation through the selected server-confirmed account identity.
Market strip
Depth and market-data upgrades are explicit product lanes, not hidden back-office settings.
Quick symbols, options catalog, expiration and strike navigation, starter Greeks, selected underlying quote, and top-of-book option quotes.
Public platform copy names top-of-book data and does not relabel it as Level 2 depth.
Execution audit
Trade history, journal, and performance stats live inside the Mayospell platform.
Open positions, working and completed orders, recent fills, account scorecard, and durable risk events.
The terminal shows real order lifecycle and server-backed scorecard state as first-class artifacts.
Copier and stack logic
Seat routing has explicit lead/follower restrictions and excludes any future live account.
Not available at launch. Orders route only to the explicitly selected practice, combine, or funded-combine account.
Account ID and optional seat ID are verified on each mutation; there is no decorative copier control in /trade.
Support path
Members stop trading and document the issue when platform behavior breaks.
The terminal exposes exact order and account identity plus current execution and breach state; the room gives a manual incident checklist.
Automatic screenshot and evidence-pack export are labeled unavailable rather than presented as completed functionality.
Inside the day
The product leads the trader from prep to review without leaving the desk.
This is the daily loop that makes the site feel like a platform business instead of a static evaluation funnel.
01
Pre-market brief
The desk opens with levels, catalysts, expected volatility posture, and the structures approved for the session.
02
Execution window
The trader works inside structure permissions, premium sizing rails, daily loss controls, and event-specific lockouts.
03
Review and tagging
Orders, fills, settled days, and concentration update the account scorecard; journal, screenshot, and reviewer-note automation remain roadmap items.
04
Progression loop
The same platform then drives payout requests, reactivation decisions, and the eventual call-up toward live options buying power.
Access ladder
A platform business also needs a believable add-on and sandbox story.
Mayospell's offer is more than a combine fee: software access, data depth, API usage, and practice workflow each have a clear lane.
Module
Mayospell detail
Mayospell adaptation
Product note
Included market data
Baseline options quotes and starter greeks are included with an active combine.
Chains, greeks, and baseline quote depth included with every active options combine.
This is the baseline expectation before any premium tooling is sold.
Advanced data add-on
Advanced depth and flow tools are available as a separate monthly add-on.
Optional advanced flow bundle for full depth, volatility surface tools, and richer earnings-event monitoring.
The paid layer should feel like desk tooling, not cosmetic upsells.
API lane
API access is billed separately from the core combine subscription.
Options API kit for local automations, execution relays, journal sync, and custom risk enforcement.
Developer access becomes part of the product story, not a hidden side channel.
Sandbox account
Active combines get an options practice seat for rehearsal and replay.
Every active combine unlocks an options paper seat for playbook testing, replay, and dry-run automation.
A desk business wins when experimentation stays inside the same system.
Why it sticks
The platform is the part traders keep coming back to.
The program gets traders started; the room keeps daily work coherent through reactivation, payouts, and planned live review.
Mirror accounts and staged sizing
The platform teaches traders to operate multiple Mayospell seats cleanly, with staged sizing and grouped scorecards.
Research artifacts in the same room
Strategy prompts, setup journals, and trade reviews belong in the same workspace as the combine scorecard so behavior compounds over time.
Desk tone over social noise
The community layer feels like a prop floor: opening notes, midday adjustments, reviewer callouts, and ranked examples of disciplined execution.
Platform routes
The platform page sends traders straight into the surfaces that prove the software exists.
This is where the public software story starts behaving like a real product map instead of a promise deck.
Trading workstation
Open the seat-aware desk where ticket controls, watchlists, chain context, fills, and incident capture all live together.
Dashboard
Walk the scorecard, payout counters, funded readiness, and review queue that the public platform page is promising.
Accounts stack
See how stacked combines and funded seats are managed once the trader stops being a single-account story.
Add-ons
Open the software lane for included data, controlled API access, active-combine practice, and clearly labeled unavailable roadmap upgrades.
Status and support
Check the public health surface the desk expects traders to verify before treating a platform issue like a personal mistake.
Member POP center
Open the member artifact archive where payout history, share state, and seat-level release records stay attached to the platform relationship.
Platform proof
Software trust gets stronger when payout and seat artifacts stay attached to the same system.
These shared POP records make the platform story feel tied to real account history, release timing, and member-proof objects.
Next surface