Adelson Case Evidence Map & Trial Timeline Explorer

This explainer describes the saved interface code, not verified legal evidence or current case status. The timeline renderer loops through the saved milestone array directly. It does not sort by the date labels. An illustrative three-item array therefore renders three cards in source order even if its dates are out of order. The bar is three hundred pixels at one hundred pixels per item. The initial active card uses array index twelve, which is the thirteenth item because indices start at zero. Clicking a milestone changes a selected subject through a fixed list of identifier branches. Neither source order, active styling nor a selected subject proves chronology, guilt, corroboration or authenticity. All underlying case assertions remain unverified saved text. Selecting an evidence category filters the visible subject exhibit cards by exact category equality. It also fades or highlights graph edges if the graph exists. The JSON export instead writes the complete selected-subject exhibit array, even when a category is active. For an illustrative subject with four saved exhibits and two matching a selected category, the visible count is two while export contains four. Bars share eighty pixels per exhibit, widths one hundred sixty and three hundred twenty. Export includes a filter-applied label, but that label does not mean the saved array was filtered. A missing subject exhibit array also differs: the visible inspector can show one generic fallback card while export uses an empty array. These mechanics do not validate any evidence. Application boot first initializes Cytoscape, then renders timeline and matrix, binds controls and selects the initial subject. If the unavailable graph library throws at the first step, later steps do not execute. This is the expected limitation of the isolated offline check; it is not evidence that a live production page is broken. The diagram shows one attempted boot stage versus five planned stages at sixty pixels per stage, widths sixty and three hundred. Full behavior must be checked with the original dependencies available under authorized conditions. The video must preserve the original handlers and data. Exported timeline milestones is a saved metadata field rather than a serialized copy of every milestone card. A successful download, when verified, still proves serialization only, not legal accuracy.