FACTUAL ACTIVITY RECORD · An activity record based on work that took place
Correcting Editorial defaults and opaque Turn synchronization
Separating product defaults from dummy data and safely preserving Turn IDs unique only within a thread
Purpose
Editorial product defaults needed separation from dummy executions, and non-UUID Turn IDs from the App Server had to synchronize without collisions across threads.
Implementation
Product-default channels and feeds were moved into a dedicated fixture, clarifying the boundary between minimal and rich dummy fixtures. Turns now use database-generated UUID primary keys while preserving opaque source Turn IDs through a compound identity with their thread, and messages link to the internal UUID.
Rendering diagram…
What was confirmed
Verification results
The checks expanded to 34 assertions, including independent ingestion of two turns and their messages when different threads share one opaque Turn ID.
The fixtures and Turn synchronization were applied to the target. Every real App Server variant had not been exhaustively verified at the cutoff.
Basis for completion
The work was complete when product-default fixtures were separated, opaque Turn IDs and internal UUIDs had distinct responsibilities, and duplicate-across-thread and atomic-ingest cases were verified.