Validation Center

Trust, controls, and limitations for fiduciary review

Winzinvest is automated active management infrastructure: broker-connected execution, explicit risk controls, and labeled performance context. This page documents how metrics are presented, what can go wrong, and what is not claimed.

Not investment advice. Nothing here is a recommendation to buy or sell any security. Advisors remain responsible for client suitability and mandate design. Past performance does not guarantee future results.

Sample / illustrative data (Stage 1)

Metrics on this page are placeholders for layout and process — not verified performance. Replace via lib/validation/validation-center-config.ts or a future read-only data feed. Last config label: April 2026 (sample data).

Performance validation

Every metric is tagged with provenance (live, paper, backtest, or demo) and review status. We do not mix hypothetical backtests with live labels. For a more detailed track-record narrative, see Performance — still read disclosures there in full.

Illustrative performance (not live)

Figures below are placeholder examples for UI and process validation only. They do not represent verified live results. Replace via config or API before publishing real numbers.

Demo / samplePending review
CAGR (example)

Populate after defining measurement window and methodology.

Demo / samplePending review
Total return (example)
Demo / samplePending review
Sharpe ratio (example)
Demo / samplePending review
Sortino ratio (example)
Demo / samplePending review
Max drawdown (example)
Demo / samplePending review
Win rate (example)
Demo / samplePending review
Trades (example count)
Demo / samplePending review
Current exposure (example)

FUTURE: optional read-only % of NLV in equities/options from snapshot.

Demo / samplePending review
Since inception (label)
TBD
Demo / samplePending review
Losing months (example count)

Define consistently (calendar month vs rolling) before publishing.

Demo / samplePending review
Volatility (e.g. ann. stdev, example)
Demo / samplePending review
Leverage / margin utilization (example)

FUTURE: optional read-only metric from snapshot (gross leverage, Reg T, etc.) — label definitions matter.

Backtest / research context (hypothetical)

Backtests are hypothetical, subject to modeling assumptions, and not indicative of live results. Any internal research metrics must be labeled separately from live or paper trading.

Backtest / hypotheticalSelf-reported
Backtest Sharpe (illustrative)

Shown only when you choose to publish a specific validated study; otherwise omit.

Backtest / hypotheticalSelf-reported
Backtest max drawdown (illustrative)

Required caution

  • Past performance — live, paper, or hypothetical — does not guarantee future results.
  • Sample or self-reported figures are not substitutes for independent verification.
  • Consult qualified professionals for tax, legal, and investment advice for your situation.

Monthly performance (table)

Rows below are structural placeholders. Publish only reconciled, clearly labeled data.

Monthly performance sample rows
MonthReturnMax DDNotes
Sample Month APlaceholder row. Replace with reconciled month-end data if published.
Sample Month BPlaceholder row.

Risk transparency

The system may underperform or lose money. Below are straightforward descriptions of common risk channels — not an exhaustive list.

Drawdowns and losing periods

Rules-based automation does not eliminate losses. The system can experience multi-week or multi-month drawdowns, sequences of losing trades, and periods when risk controls reduce position size or block new entries entirely.

Volatility and leverage

Volatility changes margin requirements, option marks, and gap risk. If your account uses margin or options, effective leverage can fluctuate. Exposure limits in configuration are targets, not guarantees under stress.

Concentration and correlation

Sector and single-name limits are enforced by design, but correlations can spike in crises — diversification benefits may shrink when markets move together.

Kill switch and defensive halts

Automated halts (for example, daily loss tiers or operator kill switch) are intended to cap damage in degraded conditions. They also mean the system may sit in cash or reduced risk while opportunities pass.

When automation may lag or suffer

  • Trend-following and momentum sleeves tend to struggle in sharp, choppy reversals after extended trends.
  • Mean-reversion logic can underperform in persistent one-direction markets.
  • Options income is not linear: assignment, rolls, and volatility spikes can dominate short-term outcomes.
  • Slippage, borrow costs, and tax frictions are not fully captured in most backtests.
  • Any dependency on broker APIs or data vendors introduces operational tail risk during outages.

Unfavorable conditions (examples)

  • Sharp reversals after extended trends (whipsaw).
  • Liquidity stress: wide spreads, halted names, or constrained short availability.
  • Volatility spikes that widen stops and option marks faster than models assume.
  • Gap-down or gap-through-stop events when markets reopen beyond protective prices.
  • Broker or API outages that delay reconciliation, stops, or hedges.

Methodology overview

High-level description only. Proprietary parameters and full rule sets are not exposed here. This is software infrastructure for systematic execution — not personalized advice.

Regime-aware gating

The automation evaluates market context before expanding risk. Signals can be scaled down or disallowed when configured regime or stress indicators are unfavorable — a deliberate trade-off between participation and drawdown control.

Systematic selection

Candidates are ranked and filtered by rules designed for consistency and auditability. The public Validation Center does not disclose proprietary parameter sets or full rule logic — only the class of behavior (systematic, repeatable, logged).

Execution via Interactive Brokers

Orders are transmitted through your brokerage connection according to your permissions and account settings. Winzinvest is software that automates workflows; it does not custody assets or guarantee fills.

Risk controls

Position sizing, exposure caps, options overlays where enabled, and defensive halts are part of the operating system — not one-off discretion. Controls can block trades that would otherwise be allowed by a signal alone.

Audit logging

Decision and execution trails are designed for post-hoc review: what was considered, what passed gates, and what was sent to the broker. Logging depth may vary by module; Stage 1 focuses on transparency of process, not performance promises.

Portfolio-level safeguards

Beyond single-trade checks, portfolio-level monitors (integrity, concentration, operational health) aim to catch gaps between intended risk and broker state. These are safeguards, not proof against all failure modes.

Trust & compliance foundation

Disclosures

  • Winzinvest provides software and tooling for self-directed investors. It is not a registered investment adviser, broker-dealer, or fiduciary.
  • You remain responsible for your brokerage relationship, account permissions, tax choices, and every investment decision. Automation does not transfer that responsibility.
  • Results vary with account size, margin rules, commissions, slippage, borrow costs, tax treatment, and market conditions. Past or hypothetical results do not guarantee future outcomes.
  • Backtests and simulations are hypothetical unless clearly labeled otherwise and are subject to modeling limitations.
  • Any live or paper track record published here must be labeled by source (live vs paper vs backtest) and should align with how numbers are calculated and reconciled.

Review placeholders (Stage 1)

  • Legal review: pending — placeholder for counsel sign-off on public disclosures.
  • Independent quantitative review: pending — placeholder for third-party methodology / backtest scrutiny.
  • Security review: pending — placeholder for penetration test or security assessment summary suitable for public release.

Validation status

Labels describe attestation state — not marketing badges. No item implies SEC registration or third-party verification unless explicitly stated.

  • Performance metrics (public page)

    Stage 1: placeholders until reconciliation policy and labeling are finalized.

    Self-reported
  • Broker statements vs dashboard

    FUTURE: optional read-only linkage or periodic attestation workflow.

    Pending review
  • CPA / financial statement review

    Not claimed in Stage 1.

    Pending review
  • Independent quant review

    Not claimed in Stage 1.

    Pending review
  • Security review (publishable summary)

    Not claimed in Stage 1.

    Pending review
  • Legal review of public copy

    Required before treating this page as final.

    Pending review

Operator philosophy

Why this exists

Winzinvest was built to run a disciplined, rules-based portfolio operating system with less day-to-day manual intervention — while preserving auditability and explicit risk limits.

The philosophy favors transparency of process over promotional claims: show controls, labeling, and limitations clearly; let sophisticated users decide fit.

Stage 1 prioritizes a credible trust layer (disclosures, provenance labeling, and honest risk language) before scaling distribution or performance marketing.

Validation Center - Winzinvest | Winzinvest