Skip to main content

Enforcement Modes

Smoltbot supports three enforcement modes that control how the system responds when alignment or integrity violations are detected. You can choose the level of intervention appropriate for your use case — from passive observation to active blocking.

Modes Overview

Observe

Detect violations, record them, take no action. This is the default mode. Ideal for initial deployment and monitoring.

Nudge

Detect violations and inject feedback into the agent’s next request via system prompt. The agent sees it and can self-correct.

Enforce

Hard block with 403 for non-streaming requests. Falls back to nudge for streaming requests.

Mode Details

Observe Mode (Default)

In observe mode, smoltbot detects and records all violations but takes no action to modify agent behavior. This is the default mode for all new agents.Behavior:
  • All API calls pass through unchanged
  • Violations are detected and recorded in the trace database
  • Integrity checkpoints are created for every interaction
  • Drift alerts are generated when behavioral patterns shift
  • No modification to agent requests or responses
When to use:
  • During initial deployment to establish behavioral baselines
  • When you want to monitor without affecting agent behavior
  • For compliance auditing where you need a record but not intervention
  • When evaluating whether to enable more active enforcement
Configuration:
curl -X PUT https://api.mnemom.ai/v1/agents/:id/enforcement \
  -H "Content-Type: application/json" \
  -d '{"mode": "observe"}'

Setting Enforcement Mode

Set enforcement mode via the API:
PUT /v1/agents/:id/enforcement
Request body:
{
  "mode": "observe" | "nudge" | "enforce"
}
Example:
# Enable nudge mode
curl -X PUT https://api.mnemom.ai/v1/agents/agent_abc123/enforcement \
  -H "Content-Type: application/json" \
  -d '{"mode": "nudge"}'

Violation Types and Enforcement

Enforcement applies to all violation types detected by the AAP verification engine and AIP integrity checks:
Violation TypeSeverityEnforcement Behavior
FORBIDDEN_ACTIONCRITICALBlocked in enforce mode; nudged in nudge mode
CARD_MISMATCHCRITICALBlocked in enforce mode; nudged in nudge mode
UNBOUNDED_ACTIONHIGHBlocked in enforce mode; nudged in nudge mode
MISSED_ESCALATIONHIGHBlocked in enforce mode; nudged in nudge mode
CARD_EXPIREDHIGHBlocked in enforce mode; nudged in nudge mode
UNDECLARED_VALUEMEDIUMNudged in nudge/enforce mode (not blocked)
In enforce mode, only CRITICAL and HIGH severity violations trigger hard blocks on non-streaming requests. MEDIUM severity violations are always handled via nudge, even in enforce mode.

Conscience Timeline

All enforcement actions are tracked in the conscience timeline, accessible via the API and the web dashboard at mnemom.ai. The timeline records:
  • When a violation was detected
  • What type and severity
  • What enforcement action was taken (observed, nudged, blocked)
  • Whether the agent self-corrected after a nudge
  • Drift patterns across enforcement events

Provider Compatibility

Enforcement works across all providers where AIP is supported:
ProviderObserveNudgeEnforce (non-streaming)Enforce (streaming)
AnthropicYesYesYesFalls back to nudge
OpenAIYesYesYesFalls back to nudge
GeminiYesYesYesFalls back to nudge