Skip to content

Design explicit scripted shock and regime scenarios #85

Description

@Tim55667757

Parent Feature: #43
Parent roadmap: #28

Scope

Provide deterministic or stochastic stress scenarios for trading-system QA when the use case requires shocks/regimes.

Acceptance criteria

  • each scenario type maps to a test objective;
  • shock/regime parameters have precise semantics;
  • seeded behavior is reproducible where stochastic;
  • market-data invariants remain valid;
  • scenarios are not marketed as empirical forecasts.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

Projects

No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions