ns-simulator-docs

Design DSDS chaos experiments with deterministic setup, explicit hypotheses, and measurable outcomes. Use when planning failure drills, resilience validation, pre-production risk exercises, and repeatable chaos scenarios for regression testing.

Map architecture requirements to valid DSDS component categories and component types. Use when converting system requirements into simulator node selections, resolving ambiguous type choices, and ensuring required attributes are captured before topology authoring.

Map DSDS architectures across AWS, GCP, and Azure equivalents and estimate cost-impact tradeoffs. Use when planning provider portability, comparing cloud options, and explaining cost/performance implications of design choices.

Convert DSDS UI specs, mock HTML screens, and system docs into concrete frontend component implementation tasks. Use when turning design references into React components, hooks, state contracts, and acceptance criteria.

Analyze likely cascade paths and propagation semantics in DSDS architectures. Use when estimating blast radius, diagnosing multi-hop degradation, validating containment strategies, or explaining how a localized failure can become systemic.

Define and evaluate deterministic invariants and policy checks for DSDS simulations. Use when encoding correctness rules, post-run validation gates, compliance constraints, and safety checks that must hold across scenarios.

Tune DSDS resilience controls including retries, deadlines, circuit breakers, rate limits, bulkheads, and load shedding. Use when balancing availability, latency, and resource protection under failure and saturation conditions.

Compose deterministic DSDS simulation scenarios from resilience hypotheses, load-test goals, or failure drills. Use when defining workload plus fault plus invariant bundles, built-in presets, and chaos experiments with reproducible seeds and explicit pass/fail criteria.

Detect and explain drift between DSDS TypeScript schema definitions and canonical catalogue CSV references. Use when auditing coverage, finding missing component/event/policy definitions, and proposing reconciliation updates.

Interpret DSDS simulation outputs including summary metrics, per-node time series, traces, causal graphs, and invariant breaches. Use when reviewing run results, comparing design alternatives, diagnosing bottlenecks, and proposing mitigation steps.

Execute DSDS roadmap tickets using dependency-aware, acceptance-criteria-first delivery. Use when selecting the next unblocked ticket, implementing code changes, validating behavior, and reporting completion against ticket AC.

Author and validate DSDS TopologyJSON from architecture descriptions, diagrams, or UI node and edge exports. Use when converting designs into simulator-ready JSON, selecting valid component types, filling queue/workload/fault fields, and checking structural consistency before simulation.