Datasets:
Update README.md
Browse files
README.md
CHANGED
|
@@ -1,3 +1,425 @@
|
|
| 1 |
-
---
|
| 2 |
-
|
| 3 |
-
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
---
|
| 2 |
+
language: en
|
| 3 |
+
license: mit
|
| 4 |
+
task_categories:
|
| 5 |
+
- text-classification
|
| 6 |
+
tags:
|
| 7 |
+
- clinical-trials
|
| 8 |
+
- five-node-cascade
|
| 9 |
+
- closed-loop-control
|
| 10 |
+
- mof-boundary
|
| 11 |
+
- clarus-v1.0
|
| 12 |
+
size_categories:
|
| 13 |
+
- 1K<n<10K
|
| 14 |
+
pretty_name: Clinical Five Node MOF Cascade Boundary v1.0
|
| 15 |
+
---
|
| 16 |
+
|
| 17 |
+
# ClarusC64/clinical-five-node-mof-cascade-boundary-v1.0
|
| 18 |
+
|
| 19 |
+
## What this repo does
|
| 20 |
+
|
| 21 |
+
This repository provides a Clarus v1.0 benchmark for multi-organ-failure cascade boundary dynamics using a five-node clinical cascade:
|
| 22 |
+
|
| 23 |
+
- metabolic_stress
|
| 24 |
+
- perfusion_deficit
|
| 25 |
+
- renal_strain
|
| 26 |
+
- hepatic_drift
|
| 27 |
+
- buffer_capacity
|
| 28 |
+
|
| 29 |
+
The v1.0 upgrade is Closed-Loop Control Geometry.
|
| 30 |
+
|
| 31 |
+
The task is no longer limited to detecting deterioration, forecasting cascade spread, or ranking one intervention against another.
|
| 32 |
+
|
| 33 |
+
It tests whether a controller can:
|
| 34 |
+
|
| 35 |
+
- choose the right cascade rescue path
|
| 36 |
+
- apply that path in the right sequence
|
| 37 |
+
- read feedback from the system
|
| 38 |
+
- adapt in time
|
| 39 |
+
- maintain durable recovery across the cascade
|
| 40 |
+
|
| 41 |
+
## Concept ladder
|
| 42 |
+
|
| 43 |
+
| Version | Capability |
|
| 44 |
+
|---|---|
|
| 45 |
+
| v0.1 | cascade detection |
|
| 46 |
+
| v0.2 | trajectory awareness |
|
| 47 |
+
| v0.3 | cascade forecasting |
|
| 48 |
+
| v0.4 | boundary discovery |
|
| 49 |
+
| v0.5 | recovery geometry |
|
| 50 |
+
| v0.6 | intervention reasoning |
|
| 51 |
+
| v0.7 | uncertainty-aware intervention |
|
| 52 |
+
| v0.8 | regime transition geometry |
|
| 53 |
+
| v0.9 | intervention competition geometry |
|
| 54 |
+
| v1.0 | closed-loop control geometry |
|
| 55 |
+
|
| 56 |
+
## Core five-node cascade
|
| 57 |
+
|
| 58 |
+
### metabolic_stress
|
| 59 |
+
|
| 60 |
+
Primary metabolic burden driving multi-organ-failure escalation.
|
| 61 |
+
|
| 62 |
+
### perfusion_deficit
|
| 63 |
+
|
| 64 |
+
Circulatory under-delivery and tissue perfusion failure.
|
| 65 |
+
|
| 66 |
+
### renal_strain
|
| 67 |
+
|
| 68 |
+
Renal stress and clearance instability within the cascade.
|
| 69 |
+
|
| 70 |
+
### hepatic_drift
|
| 71 |
+
|
| 72 |
+
Hepatic destabilization and downstream metabolic drift.
|
| 73 |
+
|
| 74 |
+
### buffer_capacity
|
| 75 |
+
|
| 76 |
+
Remaining reserve available to absorb cascade stress.
|
| 77 |
+
|
| 78 |
+
## Clinical variable mapping
|
| 79 |
+
|
| 80 |
+
| Variable | Clinical interpretation | Typical measurement proxies |
|
| 81 |
+
|---|---|---|
|
| 82 |
+
| metabolic_stress | metabolic burden | lactate load, acidosis burden, oxygen debt |
|
| 83 |
+
| perfusion_deficit | tissue under-delivery | MAP instability, capillary refill deficit, peripheral shutdown |
|
| 84 |
+
| renal_strain | renal destabilization | creatinine rise, urine drop, clearance burden |
|
| 85 |
+
| hepatic_drift | hepatic deterioration | bilirubin drift, transaminase strain, synthetic stress |
|
| 86 |
+
| buffer_capacity | remaining reserve | perfusion reserve, metabolic reserve, organ tolerance |
|
| 87 |
+
|
| 88 |
+
These five variables define the structural state of the multi-organ-failure cascade rather than isolated bedside readings.
|
| 89 |
+
|
| 90 |
+
## Prediction target
|
| 91 |
+
|
| 92 |
+
The target is `label_mof_boundary`.
|
| 93 |
+
|
| 94 |
+
### Default stronger v1.0 rule
|
| 95 |
+
|
| 96 |
+
`label = 1` if all of the following hold:
|
| 97 |
+
|
| 98 |
+
- `stabilization_success = 1`
|
| 99 |
+
- `trajectory_shift < -0.10`
|
| 100 |
+
- `intervention_alignment_score >= 0.60`
|
| 101 |
+
- `control_sequence_alignment_score >= 0.60`
|
| 102 |
+
- `recovery_consistency_score >= 0.60`
|
| 103 |
+
|
| 104 |
+
### Mid-strength variant
|
| 105 |
+
|
| 106 |
+
`label = 1` if:
|
| 107 |
+
|
| 108 |
+
- `stabilization_success = 1`
|
| 109 |
+
- `trajectory_shift < -0.10`
|
| 110 |
+
- `control_sequence_alignment_score >= 0.60`
|
| 111 |
+
|
| 112 |
+
### Relaxed variant
|
| 113 |
+
|
| 114 |
+
`label = 1 if stabilization_success = 1`
|
| 115 |
+
|
| 116 |
+
## Example row
|
| 117 |
+
|
| 118 |
+
The following simplified row shows a near-miss under the strict v1.0 label rule.
|
| 119 |
+
|
| 120 |
+
| Field | Value |
|
| 121 |
+
|---|---|
|
| 122 |
+
| stabilization_success | 1 |
|
| 123 |
+
| trajectory_shift | -0.11 |
|
| 124 |
+
| intervention_alignment_score | 0.64 |
|
| 125 |
+
| control_sequence_alignment_score | 0.59 |
|
| 126 |
+
| recovery_consistency_score | 0.74 |
|
| 127 |
+
|
| 128 |
+
Four of the five conditions are satisfied.
|
| 129 |
+
|
| 130 |
+
But `control_sequence_alignment_score = 0.59` falls below the threshold of `0.60`.
|
| 131 |
+
|
| 132 |
+
Therefore:
|
| 133 |
+
|
| 134 |
+
`label = 0`
|
| 135 |
+
|
| 136 |
+
This shows why v1.0 rewards true closed-loop cascade control, not temporary improvement alone.
|
| 137 |
+
|
| 138 |
+
## Row structure
|
| 139 |
+
|
| 140 |
+
Each row represents a multi-organ-failure cascade boundary scenario with:
|
| 141 |
+
|
| 142 |
+
- five cascade nodes
|
| 143 |
+
- trajectory signals
|
| 144 |
+
- boundary geometry
|
| 145 |
+
- regime transition signals
|
| 146 |
+
- intervention competition signals
|
| 147 |
+
- closed-loop control signals
|
| 148 |
+
- perturbation and recovery signals
|
| 149 |
+
- delta signals
|
| 150 |
+
- intervention path and final label
|
| 151 |
+
|
| 152 |
+
## Signal groups
|
| 153 |
+
|
| 154 |
+
### Five-node cascade variables
|
| 155 |
+
|
| 156 |
+
- metabolic_stress
|
| 157 |
+
- perfusion_deficit
|
| 158 |
+
- renal_strain
|
| 159 |
+
- hepatic_drift
|
| 160 |
+
- buffer_capacity
|
| 161 |
+
|
| 162 |
+
### Trajectory signals
|
| 163 |
+
|
| 164 |
+
- drift_gradient
|
| 165 |
+
- drift_velocity
|
| 166 |
+
- drift_acceleration
|
| 167 |
+
- trajectory_shift
|
| 168 |
+
|
| 169 |
+
### Boundary geometry
|
| 170 |
+
|
| 171 |
+
- boundary_distance
|
| 172 |
+
- secondary_boundary_distance
|
| 173 |
+
- boundary_competition_ratio
|
| 174 |
+
|
| 175 |
+
### Uncertainty signals
|
| 176 |
+
|
| 177 |
+
- boundary_uncertainty
|
| 178 |
+
- trajectory_uncertainty
|
| 179 |
+
- regime_confidence
|
| 180 |
+
- transition_uncertainty
|
| 181 |
+
- intervention_uncertainty
|
| 182 |
+
- controller_confidence
|
| 183 |
+
- feedback_noise_ratio
|
| 184 |
+
|
| 185 |
+
### Regime transition signals
|
| 186 |
+
|
| 187 |
+
- regime_transition_score
|
| 188 |
+
- transition_direction
|
| 189 |
+
- regime_separation_margin
|
| 190 |
+
- transition_velocity
|
| 191 |
+
|
| 192 |
+
### Intervention signals
|
| 193 |
+
|
| 194 |
+
- intervention_leverage_score
|
| 195 |
+
- intervention_alignment_score
|
| 196 |
+
- rescue_window_width
|
| 197 |
+
- pathway_divergence_margin
|
| 198 |
+
- intervention_competition_ratio
|
| 199 |
+
- primary_intervention_path
|
| 200 |
+
- secondary_intervention_path
|
| 201 |
+
- pathway_switch_velocity
|
| 202 |
+
- minimal_intervention_path
|
| 203 |
+
|
| 204 |
+
## Closed-loop control signals v1.0
|
| 205 |
+
|
| 206 |
+
- control_sequence_alignment_score
|
| 207 |
+
- control_horizon
|
| 208 |
+
- feedback_response_score
|
| 209 |
+
- intervention_timing_score
|
| 210 |
+
- adaptation_latency
|
| 211 |
+
- control_stability_margin
|
| 212 |
+
- sequence_divergence_margin
|
| 213 |
+
- controller_confidence
|
| 214 |
+
- recovery_consistency_score
|
| 215 |
+
- control_recalibration_count
|
| 216 |
+
- terminal_pathway_state
|
| 217 |
+
|
| 218 |
+
Possible terminal pathway states include:
|
| 219 |
+
|
| 220 |
+
- stabilized
|
| 221 |
+
- partially_stabilized
|
| 222 |
+
- unstable_recovery
|
| 223 |
+
- relapse
|
| 224 |
+
- irreversible_collapse
|
| 225 |
+
|
| 226 |
+
### Optional control diagnostics included
|
| 227 |
+
|
| 228 |
+
- feedback_noise_ratio
|
| 229 |
+
- controller_oscillation_score
|
| 230 |
+
- rollback_trigger_count
|
| 231 |
+
|
| 232 |
+
## Recovery signals
|
| 233 |
+
|
| 234 |
+
- recovery_distance
|
| 235 |
+
- recovery_gradient
|
| 236 |
+
- return_feasibility
|
| 237 |
+
|
| 238 |
+
## Perturbation signals
|
| 239 |
+
|
| 240 |
+
- perturbation_radius
|
| 241 |
+
- collapse_trigger
|
| 242 |
+
|
| 243 |
+
## Delta signals
|
| 244 |
+
|
| 245 |
+
- delta_metabolic_stress
|
| 246 |
+
- delta_perfusion_deficit
|
| 247 |
+
- delta_renal_strain
|
| 248 |
+
- delta_hepatic_drift
|
| 249 |
+
- delta_buffer_capacity
|
| 250 |
+
|
| 251 |
+
## Dataset construction
|
| 252 |
+
|
| 253 |
+
Each scenario is generated using a structured simulation of five-node multi-organ-failure cascade deterioration and intervention sequences.
|
| 254 |
+
|
| 255 |
+
### 1. Cascade initialization
|
| 256 |
+
|
| 257 |
+
A baseline multi-organ-failure cascade state is sampled across the five nodes.
|
| 258 |
+
|
| 259 |
+
### 2. Instability evolution
|
| 260 |
+
|
| 261 |
+
The cascade evolves using trajectory signals that determine movement toward collapse or recovery boundaries.
|
| 262 |
+
|
| 263 |
+
### 3. Intervention competition
|
| 264 |
+
|
| 265 |
+
Candidate rescue sequences are evaluated using intervention competition geometry.
|
| 266 |
+
|
| 267 |
+
### 4. Closed-loop control execution
|
| 268 |
+
|
| 269 |
+
A selected rescue path is applied through a sequence of actions.
|
| 270 |
+
|
| 271 |
+
Control signals measure:
|
| 272 |
+
|
| 273 |
+
- sequence alignment
|
| 274 |
+
- timing
|
| 275 |
+
- feedback interpretation
|
| 276 |
+
- adaptation speed
|
| 277 |
+
- durability of recovery across the cascade
|
| 278 |
+
|
| 279 |
+
The final state determines:
|
| 280 |
+
|
| 281 |
+
- `stabilization_success`
|
| 282 |
+
- `terminal_pathway_state`
|
| 283 |
+
- `label_mof_boundary`
|
| 284 |
+
|
| 285 |
+
## Files
|
| 286 |
+
|
| 287 |
+
- `data/train.csv`
|
| 288 |
+
Labeled training set with the full v1.0 schema.
|
| 289 |
+
|
| 290 |
+
- `data/tester.csv`
|
| 291 |
+
Test-style file. `stabilization_success` is withheld.
|
| 292 |
+
|
| 293 |
+
- `scorer.py`
|
| 294 |
+
Reference scorer for binary metrics and v1.0 control diagnostics.
|
| 295 |
+
|
| 296 |
+
- `benchmark_spec.json`
|
| 297 |
+
Canonical machine-readable benchmark spec.
|
| 298 |
+
|
| 299 |
+
- `dataset_schema.json`
|
| 300 |
+
Machine-readable structural schema with column groups, types, ranges, and row order.
|
| 301 |
+
|
| 302 |
+
## Evaluation
|
| 303 |
+
|
| 304 |
+
### Primary metric
|
| 305 |
+
|
| 306 |
+
- `recall_correct_control_sequence_selection`
|
| 307 |
+
|
| 308 |
+
### Secondary metric
|
| 309 |
+
|
| 310 |
+
- `false_effective_control_rate`
|
| 311 |
+
|
| 312 |
+
### Binary metrics
|
| 313 |
+
|
| 314 |
+
- accuracy
|
| 315 |
+
- precision
|
| 316 |
+
- recall
|
| 317 |
+
- f1
|
| 318 |
+
- confusion matrix
|
| 319 |
+
|
| 320 |
+
### Closed-loop diagnostics
|
| 321 |
+
|
| 322 |
+
- primary_intervention_path_accuracy
|
| 323 |
+
- secondary_intervention_path_accuracy
|
| 324 |
+
- control_sequence_alignment_accuracy
|
| 325 |
+
- control_horizon_error
|
| 326 |
+
- feedback_response_accuracy
|
| 327 |
+
- intervention_timing_accuracy
|
| 328 |
+
- high_uncertainty_control_miss_rate
|
| 329 |
+
- narrow_window_control_miss_rate
|
| 330 |
+
- adaptation_latency_error
|
| 331 |
+
- control_stability_error
|
| 332 |
+
- recovery_consistency_error
|
| 333 |
+
- recalibration_overuse_rate
|
| 334 |
+
- controller_oscillation_misread_rate
|
| 335 |
+
- terminal_pathway_state_accuracy
|
| 336 |
+
|
| 337 |
+
## Structural interpretation
|
| 338 |
+
|
| 339 |
+
Earlier Clarus datasets asked:
|
| 340 |
+
|
| 341 |
+
**Which rescue path is best?**
|
| 342 |
+
|
| 343 |
+
v1.0 asks a harder question:
|
| 344 |
+
|
| 345 |
+
**Can the controller stay aligned with reality while a five-node multi-organ-failure cascade evolves?**
|
| 346 |
+
|
| 347 |
+
Real systems fail not only because the first action is wrong.
|
| 348 |
+
|
| 349 |
+
They also fail because:
|
| 350 |
+
|
| 351 |
+
- feedback is misread
|
| 352 |
+
- adaptation is delayed
|
| 353 |
+
- interventions are mistimed
|
| 354 |
+
- control oscillations destabilize recovery
|
| 355 |
+
|
| 356 |
+
v1.0 measures these failure modes directly.
|
| 357 |
+
|
| 358 |
+
## Dataset limitations
|
| 359 |
+
|
| 360 |
+
This dataset models structural control dynamics, not detailed clinical treatment protocols.
|
| 361 |
+
|
| 362 |
+
Important limitations:
|
| 363 |
+
|
| 364 |
+
- intervention paths are simplified abstractions
|
| 365 |
+
- control signals represent structural decision quality, not pharmacological precision
|
| 366 |
+
- physiological variables are normalized system indicators rather than raw bedside measurements
|
| 367 |
+
- the dataset does not capture the full biological variability of real multi-organ-failure cascades
|
| 368 |
+
|
| 369 |
+
The benchmark evaluates control reasoning, not medical safety.
|
| 370 |
+
|
| 371 |
+
## Intended use
|
| 372 |
+
|
| 373 |
+
This dataset is intended for research on:
|
| 374 |
+
|
| 375 |
+
- instability prediction
|
| 376 |
+
- sequential decision reasoning
|
| 377 |
+
- closed-loop cascade control modeling
|
| 378 |
+
- intervention planning under uncertainty
|
| 379 |
+
- AI robustness in dynamic clinical-like environments
|
| 380 |
+
|
| 381 |
+
## Not intended for
|
| 382 |
+
|
| 383 |
+
This dataset must not be used for:
|
| 384 |
+
|
| 385 |
+
- real clinical decision support
|
| 386 |
+
- medical diagnosis
|
| 387 |
+
- treatment recommendation systems
|
| 388 |
+
- automated ICU control systems
|
| 389 |
+
- deployment in patient care environments
|
| 390 |
+
|
| 391 |
+
## Structural note
|
| 392 |
+
|
| 393 |
+
This v1.0 dataset marks the move from intervention competition to actual control logic across a five-node cascade.
|
| 394 |
+
|
| 395 |
+
The benchmark asks whether the controller stays aligned with reality across time.
|
| 396 |
+
|
| 397 |
+
That is the threshold where Clarus becomes a control-layer instrument rather than only a detection or ranking layer.
|
| 398 |
+
|
| 399 |
+
## Production deployment
|
| 400 |
+
|
| 401 |
+
This dataset format is suitable for controlled benchmarking in domains where sequential intervention quality matters more than one-shot classification.
|
| 402 |
+
|
| 403 |
+
Examples include:
|
| 404 |
+
|
| 405 |
+
- multi-organ-failure cascade stabilization
|
| 406 |
+
- ICU escalation pathway planning
|
| 407 |
+
- multistage rescue benchmarking
|
| 408 |
+
- distributed system control
|
| 409 |
+
- multi-step recovery planning
|
| 410 |
+
|
| 411 |
+
## Enterprise and research collaboration
|
| 412 |
+
|
| 413 |
+
This repo is part of the broader Clarus ladder for modeling instability, recovery, and control under feedback.
|
| 414 |
+
|
| 415 |
+
It is designed for:
|
| 416 |
+
|
| 417 |
+
- benchmark development
|
| 418 |
+
- model evaluation
|
| 419 |
+
- intervention policy testing
|
| 420 |
+
- control-sequence auditing
|
| 421 |
+
- future cross-domain transfer into other high-stakes systems
|
| 422 |
+
|
| 423 |
+
## License
|
| 424 |
+
|
| 425 |
+
MIT
|