SerenQuantDocs
Sign up
Sign up
© 2026 SerenQuant. All rights reserved.
DocsPrivacyTermsStatusSupport
Docs
Documentation
Start here
Overview
Guide library
GuidesGetting Started: APIGetting Started: MCPAuth + Workspace ScopesAccount and Workspace ManagementMarkets WorkspaceMarkets Symbol WorkspaceMarket Guides and Beta ScopeFutures ReadinessResearch WorkflowResearch Workbench, Pipeline, and ExperimentsResearch Specialist MethodsResearch Context SurfacesBacktests Run LifecycleBacktests Run Detail and CompareStrategy Sweeps and OptimizerExecution WorkflowProviders and BenchmarkingSettings and Runtime ConfigAgent WorkbenchNews WorkflowDatasets WorkflowGlobal Language SelectionMFA Getting StartedMFA Recovery + Device LossMFA Trusted DevicesMFA API ReferenceLLM Market Analysis LoopStrategy Generation + Backtest LoopPromotion + Risk Guardrails
Reference
API ReferenceMCP Reference
Lifecycle
Changelog
  1. Docs/
  2. Guides/
  3. Market Guides and Beta Scope
Public docs

Guide: Market Guides and Beta Scope

Use the market-guides directory, guide detail pages, and beta-scope surface to understand tradability, validation, and current market-feature limits.

Adjacent product surface

Treat market guides as structured product education, not loose marketing copy.

This guide covers the routes that explain what the current market stack can support, how individual guide entries should be interpreted, and how the beta-scope page frames feature limits.

  • The guide directory is filterable by asset class and jurisdiction and groups entries by asset type so users can browse the right policy context quickly.
  • Guide detail pages emphasize tradability, validation, freshness, risk, and operational sections such as settlement, tax, fees, and restrictions.
  • The beta guide translates the current markets rollout into a user-facing scope statement before someone assumes every asset or workflow is production-ready.

Routes and surfaces

These routes make up the current market-education and rollout-clarity surface.

/markets/guides

Guide directory

Browse grouped guide summaries, apply asset-type filters, and recover cleanly through the empty-state fallback.

/markets/guides/[slug]

Guide detail

Open a single guide entry to inspect freshness, tradability, validation, risk notes, and the primary operational sections.

/markets/beta-guide

Beta guide

Read the current rollout scope, workflow expectation, caveats, source rights, and degradation guidance for the markets product.

/markets

Markets workspace

Jump back to the signed-in workspace after you understand the education or rollout context that applies to the current asset class.

Recommended directory flow

Use this loop to move from broad guide discovery into a specific operational interpretation without skipping the rollout context.

01

Filter by asset context first

Use the directory controls to constrain the list by asset_type and jurisdiction before you compare guides across unrelated markets.

02

Open the guide entry

Choose a single guide card and review its summary before you assume the asset is fully tradable or production-ready.

03

Interpret the detail page carefully

Read the summary card, risk note, validation state, and primary sections to understand operational constraints instead of only scanning the title.

04

Cross-check against the beta scope

Use the beta guide when you need to confirm whether the current markets product intentionally excludes certain content, assets, or live behaviors.

Directory controls

These are the controls and signals users see before they ever open a guide detail page.

Filter strip

Asset-type entry points

The directory header exposes asset-type filter links so users can jump directly into equity, ETF, index, or crypto guide scopes.

Directory layout

Grouped sections and counts

Guide results are grouped by asset type with visible count labels, which makes the directory feel like an operational catalog rather than a flat article list.

Summary cards

Freshness, tradability, and confidence chips

Summary cards surface freshness, tradability status, confidence labels, scope metadata, and reviewed dates before the user commits to a full guide read.

Source strip

Primary-source preview

When sources are present, the summary card previews linked primary sources so users can see whether the guide is grounded in current market references.

What to review on a guide detail page

The guide detail view has several distinct signals; users should know what each one means before they act on it.

Header panel

Summary card

The detail summary card compresses asset scope, tradability, and validation status into one glanceable panel before the user studies any deeper section.

Top-of-page signals

Risk and benchmark banners

Risk-note warnings and benchmark-only info banners appear above the sections so users do not miss rollout or tradability caveats.

Editorial ordering

Primary sections first

Settlement, tax, fees, hours, proxies, restrictions, and risk are promoted into the first grid because they define the operational shape of the asset.

Per-section read

Section cards and status chips

Each section card includes a completion-status chip and narrative context so readers can separate polished guidance from still-partial guide content.

Section anatomy

  • Fact rows can show critical chips, applies_when notes, and effective dates, which means users should read them as operational rules rather than generic prose.
  • FAQ, proxy, and related-links sections can render structured links instead of simple narrative blocks, so the guide detail page doubles as a curated reference hub.
  • Section-source blocks distinguish primary sources and show publisher plus effective dates, making source quality part of the reading workflow.
  • The combination of fact cards, structured links, and source strips is what turns a guide detail page into a durable reference surface.

How to use the beta guide

  • Use it to confirm the currently supported market scope, not to infer a future roadmap commitment for every asset class.
  • The page explains the expected operator workflow so new users do not skip directly into advanced compare or symbol surfaces without context.
  • Caveats and source-rights notes matter because they explain data lag, publisher limits, inferred values, and other rollout-era constraints.
  • The rollout notes set expectations for invite-only access, feedback loops, and degraded behavior when the markets stack is under stress.

Next steps

Open market guides

Browse the current asset-class directory and inspect a live guide entry.

Markets workspace guide

Move from education and rollout context into the signed-in markets workflow map.

Markets symbol workspace

Go deeper on the symbol drilldown once the asset-level context and beta limits are understood.

Last updated

Mar 24, 2026

Feedback

Report unclear guidance, stale contracts, missing coverage, or broken docs UI on this page.

Open feedback issue
Previous
Markets Symbol Workspace
Next
Futures Readiness
On this page

Jump to the section you need without losing your place.

  • Treat market guides as structured product education, not loose marketing copy.
  • Routes and surfaces
  • Recommended directory flow
  • Directory controls
  • What to review on a guide detail page
  • Section anatomy
  • How to use the beta guide
  • Next steps
Last updated

Mar 24, 2026

Feedback

Report unclear guidance, stale contracts, missing coverage, or broken docs UI on this page.

Open feedback issue