Detect drift. Contain its effect. Preserve the record.

Incident classes

• Version lag
• Relationship-language conflict
• Source-role conflict
• Unavailable route
• Redirect change
• Content mismatch
• Stale API metadata
• Correction-propagation failure

8 incidents

• EVI-DRIFT-001 · Monitoring

  Deployed Eviulon release version lag

  The observed public Technical Status identified an older release than the accepted local package.

• EVI-DRIFT-002 · Monitoring

  Deployed Site Index version lag

  The observed Site Index route count and layout preceded the accepted successor package.

• EVI-DRIFT-003 · Open

  Evulgare relationship-language conflict

  Some contractor wording does not restate the full Eviulon relationship boundary.

• EVI-DRIFT-004 · Open

  International Intelligence About-page control conflict

  The observed About page described independence or no government affiliation inconsistent with the owner-authorized Eviulon-control relationship.

• EVI-DRIFT-005 · Open

  International Intelligence source-role conflict

  Observed methodology or affiliation wording could be read as independent of Eviulon despite the controlled publication relationship.

• EVI-DRIFT-006 · Contained

  International Intelligence root redirect change

  The root public URL redirected to the language-specific publication surface.

• EVI-DRIFT-007 · Monitoring

  Patefacere protected-workflow verification gap

  Public Apply, Operator, and Audit routes responded, while protected workflow behavior remains outside public observation.

• EVI-DRIFT-008 · Open

  Cross-site correction-propagation gap

  Accepted relationship and source-role corrections have not yet been evidenced across every downstream repository.

Interpretation boundary

Drift can result from release lag, editorial mismatch, changed routing, or incomplete correction propagation. It is not automatically evidence of bad faith, compromise, or contractor failure. Every incident preserves its predecessor context and correction history.