Research Methodology
Decision-support research across equities, fixed income, commodities, currencies, and geopolitical context.
Research and decision-support information. Forecasts are uncertain and may be wrong. Historical model results do not guarantee future outcomes. Content is not personalized investment advice.
Data sources and coverage
- Categories: public market prices and yields, macroeconomic releases, permitted public research and news context, and platform-specific research notes.
- Attribution: public sources are cited on the originating article or report page when published. Licensed feeds are not redistributed as raw dumps.
- Update frequency: varies by platform (intraday market desks where live feeds are connected; journal articles on editorial schedule). Exact timestamps appear on the publishing surface when available.
- Time zones: market desks generally use the trading calendar of the instrument's primary venue; research timestamps are shown in the page's stated zone or UTC when labeled.
Gap: a single cross-platform data catalog with uniform coverage tables is not yet published (P3 backlog).
Forecast targets and outputs
- Targets: instrument- or sector-level directional or level forecasts where a market platform publishes them; horizons are stated on each forecast surface.
- Calendars: equity and FX desks follow their respective trading calendars; bonds and commodities follow the instrument conventions documented on those sites.
- Output types: point estimates, directional labels, and research narratives as implemented per platform. Probabilistic intervals are described as such only when the producing system generates and validates them.
Models and validation
- Families in use: quantitative forecasting and signal ensembles on market platforms where production feeds are connected; editorial and geopolitical analysis on Zevin Insight. Exact model family labels and run identifiers appear on the originating platform when published.
- Training / evaluation separation: walk-forward or out-of-sample checks are documented on platforms that publish verification pages (for example Aizevin Stocks methodology and verification surfaces). Where not published, no walk-forward claim is made here.
- Leakage safeguards: production forecast publication is expected to use point-in-time inputs; any residual risk of revised data is disclosed as a limitation.
Gap: a unified model-version registry across all desks is not yet complete.
Missing, stale, and revised data
Platforms should surface unavailable or stale inputs rather than silently filling gaps. Revised macroeconomic prints can change historical context; published articles retain their publication date and note revisions when editors update them. Unresolved holdings in any future portfolio tool must not be treated as zero exposure.
Scores, intervals, and confidence
Any probability, interval, or confidence score is meaningful only with its definition, calibration status, and evaluation window. Uncalibrated scores are not presented as probabilities. Invented ranges around point estimates are not used.
Performance evidence
Accuracy percentages, when shown on a market platform, must identify the metric, evaluation dates, sample count, asset universe, forecast horizon, model or run provenance, and whether results are out-of-sample. Directional accuracy is not profitability. Strategy results, when present, should disclose drawdown and trading-cost assumptions; inventing a P&L record is not permitted.
Gap: a single audited cross-asset performance table is not published on this hub. Refer to each platform's verification or disclosures pages for platform-specific evidence.
Human review, monitoring, and limitations
- Publication controls and editorial review apply to journal content.
- Experimental forecast features may carry a "Beta — not for trading" notice consistent with their intended use.
- End-to-end portfolio aggregation (Portfolio Intelligence) is planned; cross-links alone are not integrated analytics.
- This methodology page documents intended practice and known gaps. It does not claim that every listed control is fully implemented on every platform.