Category: noise
-
Intel Report 086: A Retry Is Not Necessarily a New Request
A lost confirmation leaves users unsure whether an action succeeded. Distinguish the underlying request from repeated delivery before creating another consequence.
-
Field Note 088: The Second Receipt
The terminal asks the traveler to try again. Two desks then summon him for the same request, each certain that its receipt is the original.
-
Operator Brief: Test a Deadline Boundary
Use a synthetic clock and invented receipts to test the exact deadline, a delayed worker, and two displays of the same recorded event.
-
Intel Report 085: A Timestamp Needs an Event
Submission, receipt and processing are different events. A defensible deadline record identifies the relevant event, time reference and uncertainty.
-
Field Note 087: The Minute Between Clocks
The traveler finally answers the station notice. His receipt says on time. The review desk says late. Mara asks which clock the deadline belonged to.
-
Operator Brief: Test an Unanswered Notice
Run four synthetic cases through a notification workflow and check whether explicit answers stay distinguishable from delivery failures and timeouts.
-
Intel Report 084: Silence Is Not a Response
A timed-out workflow can record that no reply arrived. It cannot explain why without further evidence. Keep delivery, action and default outcomes separate.
-
Field Note 086: The Unanswered Notice
A blue receipt says the traveler accepted the station decision. Mara finds that nobody pressed accept: the response window simply expired.
-
Operator Brief: Reconstruct a Rule Timeline
Use invented procedures and cases to distinguish approval, publication, effective scope and the rule reference recorded at a decision.
-
Intel Report 083: Current Is Not Necessarily Applicable
Reviewing a decision requires more than finding the newest instructions. Separate version identity, effective dates, scope and the procedure for reconsideration.