September 21, 2026 / Chronology control
Unresolved dates remain visible
Houston contacts. The published September 9 chronology distinguishes correspondence displaying October 24, 2020 from a recalled in-person contact around October 2021. The September 21 supervisory-review request separately recalls a later office meeting around December 2021. The October and December recollections remain unresolved. Neither is substituted for the displayed 2020 correspondence date, and this note does not decide whether they refer to one visit or separate visits.
Las Vegas residential encounter. Earlier briefs used August placements; the later chronology records July/August uncertainty. The mediation calendar, property records, dispatch records, and original communications should establish the date. The earlier brief now flags that conflict beside the relevant text.
May 2024 detention. The later chronology uses May 18–19, 2024 from the described Certificate of Release. Earlier summaries placing the event in late July are not used as the timeline anchor.
Chronology source note P2 · Source note P6 · Source note P10 · September 21 prepared request
This note records differences among sources. It does not amend a submitted claim or alter any original record.
Reading standard
Statements about misconduct, motive, identity, conspiracy, retaliation, information access, or responsibility should be read according to their stated evidence basis. Original sources control over summaries.
Original sources control
Summaries exist for readability. If a summary differs from an original message, recording, filing, government letter, photograph, transcript, metadata record, log, or other source, the original source controls.
Corrections are part of the record
This site may be narrowed, supplemented, or corrected when better evidence becomes available. A correction is not treated as a failure of the project. It is evidence that the record is being maintained rather than frozen around an early theory.
How to evaluate a correction request
A useful correction request identifies the specific statement at issue and provides the document, native communication, witness information, or other source supporting the requested change. Where two competent sources conflict, the conflict should be displayed rather than silently choosing the version that better fits a theory.
Redactions and nonpublic evidence
Some evidence may remain nonpublic because it contains personal identifiers, witness information, privileged material, source-sensitive law-enforcement information, investigative methods, account identifiers, or records whose publication could prejudice preservation or an ongoing process. Nonpublication is not a claim that the material proves the allegation.
Evidence integrity rules
- Keep original evidentiary files unchanged.
- Work from copies when annotating or redacting.
- Preserve filenames, timestamps, source device information, transmission history, and metadata.
- Use hashes when forensic preservation becomes appropriate.
- Separate witness observations from what the witness was told.
- Identify the evidence classification supporting important assertions.
- Preserve contrary evidence and plausible alternative explanations.
Legal citations
Legal statutes on this website are issue-spotting and source links, not findings. A statute may be relevant only if jurisdiction, act, intent, attribution, authority or exception, causation, remedy, and deadline requirements are independently satisfied. RICO predicate status is controlled by 18 U.S.C. § 1961 rather than by the mere fact that another federal statute appears on the site.
Versioning
Material changes should update the “last modified” date and, where the change matters to interpretation, be reflected in the text rather than hidden. The objective is a record that can be audited over time.