risk-nexus

History

tegwick 2ebdc133bc Drop dedupe_key_strategy from the inbox watch and say what actually happens activity-core corrected us: it governs Temporal schedule overlap, not per-message suppression, and there is no dedupe at the sink — so an unread message re-emits hourly until read. Removed the field rather than leave it implying a guarantee it does not give, and kept the repetition deliberately: an hourly line in the progress log is a cheap price for the failure this exists to prevent, and it stops when somebody reads. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>	2026-08-20 12:02:14 +02:00
..
daily-register-check-sweep.md	RISK-WP-0004-T01: schedule the checks on activity-core	2026-08-20 08:55:48 +02:00
hourly-register-inbox-watch.md	Drop dedupe_key_strategy from the inbox watch and say what actually happens	2026-08-20 12:02:14 +02:00

tegwick 2ebdc133bc Drop dedupe_key_strategy from the inbox watch and say what actually happens

activity-core corrected us: it governs Temporal schedule overlap, not
per-message suppression, and there is no dedupe at the sink — so an
unread message re-emits hourly until read. Removed the field rather than
leave it implying a guarantee it does not give, and kept the repetition
deliberately: an hourly line in the progress log is a cheap price for the
failure this exists to prevent, and it stops when somebody reads.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

2026-08-20 12:02:14 +02:00

daily-register-check-sweep.md

RISK-WP-0004-T01: schedule the checks on activity-core

2026-08-20 08:55:48 +02:00

hourly-register-inbox-watch.md

Drop dedupe_key_strategy from the inbox watch and say what actually happens

2026-08-20 12:02:14 +02:00