Public completion record
Archive status and known limitations
· Older inventory figures are historical, not current totals.
Follow verified archive updates
See what readers can use after a verified website release. These updates describe website changes—not new evidence, agency findings or confirmed search indexing.
Open the Atom subscription feed. Copy this address into your preferred feed reader: https://www.david-medeiros.com/updates.xml. No account or email address is required by this website.
This selected release history begins September 19, 2026. Dates below record completed publication verification, not the original dates of underlying documents. Future entries require a completed release receipt; this is not a promise of continuous monitoring.
Compare and read the three principal reports
Layered explanations, source links and citations distinguish the 2023, 2024 and 2026 reports without implying government findings or supersession.
Verified
Choose one of six direct archive paths
Start Here now links directly to the principal archive destinations.
Verified
Separate published tools from unfinished review
A dated status update distinguishes recent publications from historical inventories and pending human review.
Verified
Trace six sources across priority pages
A bounded index shows 24 main-content relationships. Repetition is not independent corroboration.
Verified
Remove a duplicate priority sitemap entry
The priority sitemap retains 27 canonical destinations. Sitemap inclusion does not establish indexing.
Verified
Start research with five selected records
A source-linked starter supplies methods, limits and citation paths. Selection is not an independent ranking of evidence strength.
Verified
Compare claims against three sources
A five-question comparison separates what the records support from what remains unknown.
Verified
Copy source-specific citations
Three citation tools connect the worked example to its source records and limits.
Verified
Publication update · September 19, 2026
What can readers use now?
These reader tools are published and technically verified. They do not mean every archive workstream, human review or search-engine outcome is complete.
- Livewire articles, videos and reader search — use the article’s available player, captions, transcript and source links. Technical publication is separate from full listening review, which remains pending.
- State and federal roles and the source-linked advocacy timeline — distinguish institutions, David’s advocacy and the dates recorded by sources.
- Follow One Record — follow an acknowledgment, closure and referral without turning receipt into a finding.
- Three source-specific citation tools — copy a citation with its source, date, case identifier and limits.
- Source-to-claim comparison — compare five questions against three records and see what remains unanswered.
- Five-record research starter — open selected reports and agency records with methods, file identities and reuse limits.
- Six-source reuse index — trace 24 main-content link relationships across 27 priority pages. Repeated links are not independent corroboration.
Published is not the same as fully reviewed or indexed
Full listening, screen-reader and comprehension review remain unfinished. Older transcript and document-accessibility gaps are not closed by newer video publication. Protected research still requires its named human/source approvals. Google/Bing submission, crawling, indexing and AI citation are separate states; none is established by this publication update.
How to read the older numbers below
The inventory and workstream figures below are a historical snapshot, not current site-wide totals. Their original audit label was July 31, 2026; the machine-readable status record is dated August 7, 2026. In particular, its six-video count describes the older media catalog, not the subsequently published Livewire collection. The status JSON remains that dated inventory, not a live release ledger. No new archive-wide count is asserted here.
Historical published inventory snapshot
Published files
32,634
Historical verified deployment payload, including the two Cloudflare configuration files.
HTML pages
23,126
Current verified production snapshot. This count does not prove search indexing.
Sitemap files (older snapshot)
14
Historical count, not the current sitemap inventory. Use the published sitemap index for current membership.
Unique sitemap page URLs (older snapshot)
19,966
Historical count, not a current indexing result. Specialized sitemap entries can overlap page entries.
PDF files (older snapshot)
425
Historical inventory count. Complete manual document review remains unfinished.
Physical image files
1,691
The current media catalog contains 1,691 images. 1,217 have non-empty automated OCR; the OCR remains unreviewed.
Published video files
446
All local videos are in the video sitemap; synchronized caption coverage remains incomplete.
Verified official YouTube uploads
357
Public source records from the official ABI Resources channel; 0 reviewed transcripts are currently published on this site.
Historical workstream measurements
Progress is shown only where both a completed count and a defensible target exist. These bars measure inventory coverage, not accuracy, legal sufficiency, search indexing, or manual accessibility conformance.
MuckRock request reconstruction
PartialNo defensible completion percentage is available.
170 verified distinct MuckRock requests are documented in the current source inventory. A historical target of 200 is not supported as a verified request count. Complete communication threads and all direct attachments have not yet been established by the current evidence inventory.
Open supporting archive sectionImage OCR coverage
PartialAutomated OCR is an unreviewed discovery aid, not a verified transcript. Readers must compare it with the source image.
Open supporting archive sectionYouTube transcript publication
IncompleteVideo titles and embeds are published, but they are not substitutes for synchronized captions or reviewed transcripts.
Open supporting archive sectionPeople Index cross-references
PartialThe candidate registry is not an exhaustive extraction of every person in every PDF, image, video, FOIA thread, or article. A reference is not a finding of wrongdoing.
Open supporting archive sectionPDF editorial and accessibility review
PartialNo defensible completion percentage is available.
All 425 PDFs are public and discoverable in the verified release snapshot. Complete OCR, metadata, tagging, reading-order, and manual accessibility review is not yet proven.
Open supporting archive sectionExternal search and AI indexing
External stateNo defensible completion percentage is available.
The archive can publish crawlable pages, sitemaps, manifests, and structured data. It cannot guarantee crawling, indexing, ranking, retention, citation, or interpretation by a third party.
Open supporting archive sectionMachine-readable status sources
- Evidence-control architecture 8 human-reviewed public control records
- Media catalog current source manifest
- MuckRock request archive current verified reconstruction
- People cross-reference index current conservative candidate registry
- Sitemap index current crawler discovery index
Explicit limitations
- Evidence-control labels govern archive presentation; they are not judicial, agency, or expert determinations.
- No percentage is reported when the project lacks a defensible completed-item count.
- Automated OCR is kept separate from reviewed transcription.
- Published and sitemapped does not mean indexed by a search engine.
- Automated accessibility checks do not replace manual assistive-technology testing.
- A SHA-256 digest verifies bytes, not authorship, context, truth, or legal effect.
- The referenced G: source drive was unavailable during the latest MuckRock reconciliation.
Known incomplete or externally controlled areas
MuckRock request reconstruction
Partial170 verified distinct MuckRock requests are documented in the current source inventory. A historical target of 200 is not supported as a verified request count. Complete communication threads and all direct attachments have not yet been established by the current evidence inventory.
Open the MuckRock archivePeople and entity registry
PartialThe current People Index contains 75 conservative candidate name strings derived from the historical AccountabilityActors import. It is not an exhaustive extraction of every person named in the Livewire, FOIA, PDF, image, and video corpus.
Open the People IndexUnified PDF forensic catalog
PartialAll 425 PDFs are public and sitemapped. The unified forensic manifest has been expanded to include published evidence_derived and evidence_documents PDFs; the release gate now fails if any published PDF is absent.
Review forensic readinessVideo accessibility
IncompleteSeptember 27, 2026 inventory: the local video catalog has 446 file records, separate from 357 official-channel YouTube upload records. Existing text is linked for 440 local records: 440 caption files, 430 transcripts and 10 narration scripts. Availability does not establish verbatim accuracy, correct timing or independent human approval. Six older records still lack matching text; listening and accessibility review remain unfinished.
Open the video archiveUnique search metadata
PartialEvery indexable page has the baseline title, description, canonical URL, H1, structured data, and machine-readable manifest links. Duplicate-title and duplicate-description groups remain and require page-specific editorial revision.
Read the editorial methodologyExternal indexing and AI use
External stateThe archive can provide public HTML, sitemaps, robots directives, structured data, and AI manifests. It cannot guarantee that Google, Bing, ChatGPT, or another system will crawl, index, cite, retain, rank, or interpret every record.
Read the verification boundariesPrioritized completion work
- 1.Review orphan communication and binary artifacts against the 170 verified MuckRock requests without treating 30 unsupported historical positions as missing requests.
- 2.Build a manually reviewed entity registry from the full Livewire and evidence corpus before publishing person-specific profiles.
- 3.Record OCR, metadata, tagging, and accessibility status for all 425 PDFs and remediate priority documents.
- 4.Review the existing local caption, transcript and narration-script files against their recordings, and supply matched text for the six older records that still lack it. Prioritize official-channel videos separately; never invent spoken content or treat a narration script as a verified transcript.
- 5.Replace duplicated search titles and descriptions with page-specific editorial metadata.
- 6.Complete manual keyboard, screen-reader, zoom, reflow, document, caption, privacy, factual, and legal review.
- 7.Monitor current Search Console and Bing reports without treating sitemap submission as proof of indexing.
Standing acceptance checks
These checks condense the high-leverage audit questions into release requirements. They are tests to satisfy, not claims that every item is already complete.
Completeness
Every published record has an identified source, stable URL, discoverable parent index, and documented status.
FOIA reconstruction
A request is not marked complete until its request, agency, dates, communications, attachments, disposition, and source basis are accounted for.
Named people
A person-specific profile requires source review, identity disambiguation, relevant context, careful attribution, and links back to the underlying records.
Claims and findings
Allegations, testimony, archive summaries, technical observations, and adjudicated findings must remain visibly distinct.
Authorship
Every article must identify a verified author or accurately identify the archive as maintainer when imported attribution is uncertain.
Search metadata
Indexable pages require a descriptive title, description, canonical URL, one clear H1, useful internal links, and matching visible structured-data content.
Accessibility
Automated checks are followed by manual keyboard, screen-reader, zoom, reflow, contrast, document, caption, and transcript review.
Evidence integrity
Published hashes identify bytes; they do not by themselves prove origin, truth, legal effect, or chain of custody.
Privacy and safety
Personal, medical, contact, witness, sealed, privileged, and other sensitive material receives human review before publication.
Corrections
Material changes preserve an intelligible correction record, date, reason, and right-of-reply path.
Machine readability
Sitemaps, manifests, HTML, and schema are validated as discovery aids without claiming control over third-party crawling or interpretation.
Release evidence
A deployment is complete only after the build, release checks, live status codes, canonical host, key pages, assets, sitemaps, and error routes are verified.