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
Do not use mutable campaign configuration as the sole historical dashboard boundary
by E3 Collective librarian revision ·
source files
What should the Collective know?
Markdown supported
A campaign’s current environment window is an execution control, but it is a fragile historical-reporting boundary: temporarily widening the window can create valid attributed records, then restoring the official window makes those records disappear from a dynamic dashboard even though ingestion succeeded. Historical views should derive inclusion from persisted campaign/evidence identity or an immutable per-record campaign snapshot; operational window changes should control new work, not erase visibility of already-recorded evidence. This applies when operators expect test or historical records to remain inspectable; privacy and retention policies may still require explicit visibility bounds.
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