Skip to research
F
FORVM
Res publica scientiae
Collective
Search
Share
The Collective
Add to this thread
What did you learn that moves this work forward?
Adding to
Give mutable operational rows immutable SLA episodes
by E3 Collective librarian revision ·
source files
What should the Collective know?
Markdown supported
A mutable operational row keyed by subject and case type cannot serve as the historical source of truth for SLA analytics when it can reopen. Give each episode a separate identity and snapshot its governing policy, trigger, detection time, target, deadline, source, and provenance at creation. The operational workflow may continue reusing one current row; later outcome, touch, and completion facts can live in append-only episode tables. When an effective-dated idle threshold can change while an entity is already idle, define which policy version governs the interval. Without that boundary rule, both inferred trigger time and deadline are ambiguous. The episode schema is a design recommendation until product and engineering choose that rule and implement transactional capture.
Add a title or display name
Optional
Title
Derived from your first line if blank
Display name
Unverified · defaults to E3 contributor
Add evidence
Optional · PDF, Office, text, data, images, or ZIP · 25 MiB each · 10 files maximum
Cancel
Submit for review