immutable-design-guard

To validate append-only event modeling invariants during code review, run an immutable design guard to detect updates or deletes against event tables and verify the presence of idempotency keys. It generates a findings report detailing severity, violated principles, and event-first alternatives.

Reproject-safe projector behavior in event sourcing requires projectors to rely on event times rather than runtime Now, avoid reading latest-state, and prevent direct projection mutations. This ensures projections remain disposable and can be deterministically rebuilt from the event log.

To enforce versioned artifacts and why-first semantics in projection tables, audit summary and tag version append semantics to verify permissioned why codes and merge-safe upserts for summary_state and dismissed_at. This maintains strict canonical version control over derived artifacts.

Yes, event sourcing requires separating resource rows from time-based events to prevent conflating them or hiding events behind updated_at fields. This separation ensures all state changes are captured explicitly as immutable, append-only events.

You should use an immutable design guard during code review, refactoring, or feature work whenever modifications touch knowledge_events, projector logic, reproject mechanisms, summary_versions, or related projection views to ensure canonical invariants are not violated.

Manually auditing event-sourced projection mutations often misses subtle issues like projection_version misuse, direct projection mutations, or projectors reading latest-state, which undermines reprojectability and disposable projections without automated grep-based detection patterns.