← Back to Home Independent Review →

Audit This Site

A single verification path for the site’s public claims, normative sources, CI enforcement, and reproducible audit commands.

Start with these anchors

What to Verify

Stage 1

Metadata integrity, canonical URLs, sitemap parity, and robots hygiene.

Expected pass condition: metadata audit exits 0 with no sitemap parity failures.

Stage 2

Completeness of the semantic ledger with no blank threat, failure, or verification fields.

Expected pass condition: Stage 2 gate passed.

Stage 3

Verification hardness. Weak methods are counted and CI fails on any non-zero result.

Expected pass condition: WEAK_VERIFICATION_COUNT=0 and Stage 3 gate passed.

Reproduce the Checks

Run these commands from the repository root.

powershell -ExecutionPolicy Bypass -File scripts/metadata-audit.ps1
powershell -ExecutionPolicy Bypass -File scripts/generate-must-ledger.ps1
powershell -ExecutionPolicy Bypass -File scripts/dedupe-must-ledger.ps1 -CsvPath scripts/audit-output/<latest-must-ledger.csv>
powershell -ExecutionPolicy Bypass -File scripts/semantic-ledger-audit.ps1 -GateStage2
powershell -ExecutionPolicy Bypass -File scripts/semantic-ledger-audit.ps1 -GateStage3
Cross-platform note

These scripts also run under pwsh on Linux and macOS. If you are not on Windows, use:

pwsh -File scripts/metadata-audit.ps1
pwsh -File scripts/generate-must-ledger.ps1
pwsh -File scripts/dedupe-must-ledger.ps1 -CsvPath scripts/audit-output/<latest-must-ledger.csv>
pwsh -File scripts/semantic-ledger-audit.ps1 -GateStage2
pwsh -File scripts/semantic-ledger-audit.ps1 -GateStage3

The CI workflow regenerates the ledger, deduplicates it, fills principle-specific evidence columns, then executes Stage 2 and Stage 3 gates.

Fastest Reviewer Path

  1. Open the repository and inspect the public source for the page you are checking.
  2. Run the metadata audit and Stage 2 / Stage 3 semantic gates locally with pwsh or Windows PowerShell.
  3. Review the generated evidence under scripts/audit-output/.
  4. Send structured findings through GitHub Issues or use Independent Review for confidential feedback routing.

Evidence Locations

Accessibility Contrast Spot-Check

2026-03-27 repo-backed contrast audit

Result: no contrast-driven color change is required for the audited homepage and review-page text styles based on this spot-check.

Interpret Pass Signals

A passing review should be able to point to all of the following
  1. A valid sitemap and robots file that enumerate crawlable public pages.
  2. A spec page and MUST justifications page that define the normative claims being audited.
  3. A CI workflow showing the three-stage gate sequence.
  4. Recent audit artifacts under scripts/audit-output/.
  5. Semantic gate output containing WEAK_VERIFICATION_COUNT=0.

Suggested Crawl Entry Points