Public completion record

Archive status and known limitations

This page distinguishes what is published and technically verified from what remains partial, unresolved, manually reviewable, or controlled by an external search or AI system.

Audited July 20, 2026 · Counts are a dated build snapshot and will change with later releases.

Verified published snapshot

Published files

5,872

Current verified deployment payload, including the two Cloudflare configuration files.

HTML pages

3,452

3,246 are indexable; 206 are intentional noindex pages or aliases.

Sitemap files

One sitemap index and six child sitemaps.

Unique sitemap URLs

5,220

Unique URLs across the six child sitemaps; page, evidence, image, video, MuckRock, and X-capture entries can overlap.

PDF files

425

Every published PDF is linked from HTML and listed in the evidence sitemap.

Physical image files

1,230

The media manifest and image sitemap both contain 1,230 verified image records.

Published video files

All six are in the video sitemap; synchronized caption coverage remains incomplete.

Verified official YouTube uploads

357

Public source records from the official ABI Resources channel; these are embedded and indexed but are not represented as locally preserved video files.

Known incomplete or externally controlled areas

MuckRock request reconstruction

Partial

170 unique requests are source-verified and published against a stated total of 200. Thirty remain unresolved. The current source set does not prove a complete start-to-finish communication thread and every attachment for every request.

Open the MuckRock archive

People and entity registry

Partial

The 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 Index

Unified PDF forensic catalog

Partial

All 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 readiness

Video accessibility

Incomplete

Six locally archived video files and 357 verified official-channel YouTube uploads are public. The current audit does not verify synchronized caption tracks or reviewed transcripts for them. A transcript-boundary notice is not a substitute for captions or a reviewed transcript.

Open the video archive

Unique search metadata

Partial

Every 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 methodology

External indexing and AI use

External state

The 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 boundaries

Prioritized completion work

1.Recover and source-verify the 30 unresolved MuckRock requests and missing communication artifacts.
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.Create synchronized captions and reviewed transcripts for the six local files and the highest-priority official-channel videos without inventing spoken content.
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.