temporal-boundary-enforcer

Enforce tick and phase boundaries by inspecting logs, events, and snapshots to detect the earliest boundary breach during transitions. This skill validates all code actions against explicit tick, phase, and window boundaries to prevent cross-phase leakage.

Cross-phase leakage in tick-based simulations happens when code actions execute outside defined phase or window boundaries. This skill identifies delayed corruption by analyzing artifacts and generating a deterministic, evidence-driven boundary report.

Detect boundary breaches during phase transitions by inspecting event-sourced artifacts like logs and snapshots. This skill extracts phase timelines and window intervals using optional scripts to validate actions against absolute time boundaries.

Extract phase timelines from event logs using the optional scripts provided by this skill. These scripts extract phase timelines and window intervals for repeated checks against defined tick and phase boundaries.

This boundary enforcement approach works with existing event-sourced snapshots by inspecting them alongside logs and events. It operates directly on these artifacts to detect the earliest boundary breach without requiring external dependencies.

Avoid temporal boundary enforcement when your simulation lacks explicit tick, phase, or window boundaries, as this skill validates code actions against absolute boundaries and requires defined time constraints to generate evidence-driven reports.