Module jidoka 

Jidoka (自働化) - Autonomous anomaly detection.

Implements Toyota’s Jidoka principle: machines that detect problems and stop automatically to prevent defect propagation.

Anomaly Types

1. Non-finite values: NaN or Inf in any state variable
2. Energy drift: Total energy deviates from initial beyond tolerance
3. Constraint violations: Physical constraints exceeded

Severity Levels

Following the Batuta Stack Review, Jidoka uses graduated severity:

• Acceptable: Within tolerance, continue normally
• Warning: Approaching tolerance, log and continue
• Critical: Tolerance exceeded, stop the line
• Fatal: Unrecoverable state, halt immediately

Advanced TPS Kaizen (Section 4.3)

• Pre-flight Jidoka: In-process anomaly detection during computation [49]
• Andon vs Jidoka: Self-healing auto-correction vs full stop [51][57]

Design

The guard runs after every simulation step, ensuring immediate detection of anomalies. This prevents error propagation and enables root cause analysis.

Structs

AbortConditions

Conditions that trigger immediate abort during computation [49][51].

JidokaConfig

Jidoka guard configuration.

JidokaGuard

Jidoka guard for autonomous anomaly detection.

PreflightJidoka

Pre-flight Jidoka guard for in-process anomaly detection [49][51].

SelfHealingJidoka

Self-healing Jidoka controller for ML training [51][57].

SeverityClassifier

Classifier for graduated Jidoka responses.

Enums

JidokaResponse

Jidoka response type: Andon (stop) vs auto-correct [51][57].

JidokaViolation

Jidoka violation types.

JidokaWarning

Warning from Jidoka check (non-critical issue).

RulePatch

Corrective patch for self-healing [57].

TrainingAnomaly

Training anomaly types for ML simulation.

ViolationSeverity

Severity levels for Jidoka violations.