Regime
advancedMonitor operational regime, view transition history, and inject anomalies for testing.
Get current regime
GET
/v1/memory/regimeGet current operational regime and safety policy overrides.
200Response
{
"regime": "normal",
"anomaly_active": false,
"policy_overrides": {
"force_exact": false,
"bypass_consolidation": false,
"learning_rate_multiplier": 1
},
"modulation_signal": 0.67
}The regime field can be one of: normal, high_surprise, anomaly, recovery.
Regime history
GET
/v1/memory/regime/historyGet regime transition history.
last_nintegerDefault: 50Number of recent transitions to return.
200Response
{
"history": [
"normal",
"high_surprise",
"anomaly",
"recovery",
"normal"
],
"distribution": {
"normal": 0.72,
"high_surprise": 0.15,
"anomaly": 0.08,
"recovery": 0.05
},
"transitions": 12
}Inject anomaly
POST
/v1/memory/regime/inject-anomalySimulate an anomaly to test the safety circuit.
magnitudenumberDefault: 3.0Anomaly magnitude (minimum: 0.0). Higher values trigger stronger safety responses.
200Response
{
"anomaly_triggered": true,
"previous_regime": "normal",
"new_regime": "anomaly",
"burst_duration": 5
}Warning
This endpoint is intended for testing only. Injecting anomalies temporarily activates safety policy overrides (force_exact, bypass_consolidation) until the system recovers.
Next steps
- Explainability — XAI reports and surprise analysis
- Neuromodulation — Neuromodulation state
- Security Engine — Threat detection