About this collection: Brett Haddock and Brett Haddoak
Brett Haddock’s website, 2012–2020, served as captured.
Brett Haddock, Brett Haddoak, Brett Taylor Haddock: bretthaddock.com and bretthaddoak.com
This is a preserved copy of the personal blog of Brett Haddoak, who published and ran for Santa Clarita City Council under the name Brett Haddock (legal name Brett Taylor Haddock from docket aggregators, not a primary document the archive holds). The blog first ran at bretthaddock.com and now runs at bretthaddoak.com. Posts written as Brett Haddock now appear under the Haddoak byline (not yet sourced by the archive; the archive’s own captures record bretthaddock.com redirecting to bretthaddoak.com from December 2022, and the archive sends no request to bretthaddoak.com).
How Brett Haddock became Brett Haddoak: the name change
Haddock ran for City Council in 2016 and 2018 as Brett Haddock (not yet sourced by the archive). In May 2017 Sean Weber, a fellow applicant for a council seat, petitioned for a civil harassment restraining order against him, for himself, his mother, his father-in-law and his brother (Los Angeles Superior Court BS168929, Commissioner Laura Hymowitz). The court granted a two-year order. The Court of Appeal affirmed it on 16 October 2018 (B284011).
That opinion describes the blog post at issue as apparently including Weber’s phone number, address, date of birth and a photograph of his license plate, together with his parents’ address and phone number, which it says led to prank calls and harassment. The opinion states that the post’s text was not in the record. Haddock said he had edited the post to remove Weber’s and his parents’ addresses and phone numbers, and the court did not resolve whether he had. Weber’s counsel told the trial court that the redaction was incomplete and that the information was reposted while a temporary restraining order was in effect. That is counsel’s statement as the opinion records it, not a finding.
The trial court renewed the order in 2019 and 2021 (from docket aggregators, not a primary document the archive holds).
In June 2022, while the renewed order was in effect, Haddock filed to change his legal name. Weber opposed the petition. The court granted the name change on 5 August 2022, and Haddock filed that same day to end the restraining order. In October 2022 the court denied a third renewal and the order ended (from docket aggregators, not a primary document the archive holds).
His 2026 campaign says he and his wife changed their surnames to Haddoak when they married, combining their names. In 2026 he ran for City Council District 2 as Brett Haddoak (not yet sourced by the archive).
Brett Haddock and Brett Haddoak are the same person.
The opinion, B284011
B284011 is an unpublished opinion. Its header reads “NOT TO BE PUBLISHED IN THE OFFICIAL REPORTS”, and California Rule of Court 8.1115(a) bars courts and parties from citing or relying on it except as rule 8.1115(b) allows. Its disposition: “The order is affirmed. Weber is awarded costs on appeal.”
Sources
- The opinion
- Weber v. Haddock, B284011, Court of Appeal, Second Appellate District, Division Eight, filed 16 October 2018. Live: https://www4.courts.ca.gov/opinions/nonpub/B284011.PDF. Archived: Wayback Machine, 11 November 2026 (byte-identical to the court’s copy). archive.today: not archived; the service did not respond on 11 November 2026. SHA-256 of the court’s copy as the archive holds it:
1cee80cf72c0efa69ecc62c2c2825b344e202965849b44ac7dc60adf9f2b9dfc - Docket aggregators
- The legal name, the renewals, the name change and the October 2022 denial come from docket aggregators (Trellis, UniCourt), not from a primary document the archive holds. They are marked where they appear until the archive holds the court’s own records.
- Not yet sourced
- The 2016 and 2018 candidacies, the 2026 campaign’s statement and candidacy, and the Haddoak byline on bretthaddoak.com are the editor’s account and are marked until the archive records a source for each.
Why it is here
It was taken into the archive on the editor’s ruling R-20261110-01. [For the editor: the public statement of the ruling’s ground. The ruling’s own wording is in ACQUISITION.md; how much of it this page repeats is your call.]
The archive publishes it as it was published. It claims no ownership of these posts, asserts no licence over them and does not republish them as its own. Under the editor’s ruling R-20261111-01, nothing in this collection is taken down on request.
Corrections to the archive’s own work here, a date, a title, a count, go to contact@archivescv.com and are logged on the library’s Corrections page.
Where it came from
Every capture here was fetched by the archive itself, from the Wayback Machine’s raw copies and from Common Crawl’s crawl records. The Wayback Machine lists 2,196 captures of the site; every one of them is accounted for, held, a repeat of a capture already held, or recorded with the reason it is not. Each file’s SHA-256 was written to a fixity manifest the moment it was fetched, 1,968 entries in all, and each was checked against the source archive’s own digest. 2 served captures do not match theirs, and every page showing one says so.
On 10 November 2026 the archive asked the Wayback Machine again for every capture it holds from there. 1,205 of 1,208 were still served. Each capture’s page says which. If one is later withdrawn, the archive’s copy and its hash are what remain.
A second, encrypted copy of everything was made and verified against the fixity manifest on 11 November 2026.
What the archive changed
The captures are served as captured. The archive changes only what the library’s facsimile rules permit, and logs every change:
- 6,182 links and asset addresses pointed at the archive’s own copies;
- 4,898 references to files nobody holds, to other sites’ servers or to pages outside this collection pointed at local stand-ins, so that reading a page sends no request anywhere else;
- 1 compressed file decompressed so a browser can read it;
- 23 links to a file the archive holds and does not serve here, because it is larger than the host’s limit on a single file, pointed at a page giving its SHA-256 and its Wayback Machine address. The file was not altered to fit;
- the archive’s own furniture added around each page: the skip link, the provenance bar, the citation box, the focus outline and the library footer, each marked in the page source as the archive’s.
No text was edited and nothing was redacted. Pages that link to something the archive does not hold show the gap. What is missing lists it.
Changes between captures
2 posts read differently in later captures. The comparisons are mechanical and say nothing about why.
Timestamped
The archive’s fixity manifest as served on 13 November 2026 (SHA-256 6f873b7425feaeae…), which listed every file the archive served at that moment, 786 of them from this collection, was submitted to the OpenTimestamps calendars on 13 November 2026; its proof records an attestation in Bitcoin block 975,675 which the archive has not yet checked against a copy of the Bitcoin chain. The checksum list of the collection’s held captures (1,968 files; SHA-256 e726eaf1c90043c1…) was submitted the same way on 13 November 2026; its proof records an attestation in Bitcoin block 975,654 which the archive has not yet checked against a copy of the Bitcoin chain. Each proof and the manifest it covers are kept in the archive’s records, so anyone can check that the files have not changed since.