Phase 11 / Release assurance

Verification methodology

The documented static publication tests and their evidence limits.

Source snapshot 2026-10-13Static publishing, no reader write APIReview status: local assurance; live hosting unverified

Verification domains

  1. Source integrity: pin the exact Phase 10 archive SHA-256 before building; compare protected data byte-for-byte.
  2. Identity and attribution: verify 150 immutable person IDs, 50 states, 150 offices, real portraits and credited media, and never assign third-party X posts to a mentioned official.
  3. Document and link structure: inspect all internal links, valid destinations, unsafe URL schemes and exact public/private archive boundaries.
  4. Content security: a restrictive content security policy, no inline executable scripts, no public editor and no account credentials.
  5. Accessibility: language, headings, skip navigation, useful image alternatives, links and focus behavior on representative pages; do not mistake sampled audits for full WCAG certification.
  6. Performance and resilience: file-size budgets, HTML and CSS sizes, safe cache times, local no-network behavior and browser console.
  7. Numbers: reproduce each source-backed calculation from the frozen official datasets; do not produce new official observations.

Tests are not outside verification

Local tests detect packaging and many functional errors but cannot independently reauthenticate every X excerpt, court document, third-party image right or current officeholder. Historical articles are preserved with their original date and evidence limitations; new facts require a separate editorial source check.