Files
personal-agent-os/memory-systems/agent-os/facts/20260919-214721-project-audit-pipeline-skill-created--.md
T

27 lines
1.8 KiB
Markdown
Raw Blame History

This file contains ambiguous Unicode characters
This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.
# audit-pipeline skill created (2026-09-18)
category: project
tags: audit, hallucination, gate-detection, blind-fact-check, tie-breaking
stored: 20260919-214721
updated: 2026-09-19T22:17:00Z
audit-pipeline skill created (2026-09-18)
Three corrections applied to the audit pipeline design after retrorevolution case:
1. Gate detection is SEMANTIC, not lexical — vision_analyze on screenshots + LLM analysis of DOM text.
2. Fact-checker is TRULY blind — fetches URL fresh from scratch, different user-agent, no shared ledger.
3. Tie-breaking verification — third signal (known-good reference URL) when both agree but both might be wrong.
## Failure evidence (required for grep / post-mortem)
- case: retrorevolution age-gate misread as 404
- exact_url: https://retrorevolution.com/stores/dallas-location/
- known_good_reference: https://retrorevolution.com/
- false_finding: BROKEN / Page not found (404)
- actual_state: CONFLICT — do not publish until human verification past Cloudflare wall
- independent_check_2026-09-19T22:11Z: HTTP/2 200 on both URLs; body title "One moment, please..."; visible text "Please wait while your request is being verified..."
- pipeline_claim_2026-09-19T22:08Z: HEAD 404 + title "Page not found – Retro Revolution" on store path
- gate_type_observed_here: BOT_WALL (Cloudflare / request verification), not confirmed AGE_GATE on the store path
- prior_screenshot_age_gate: attributed to homepage or another live path; must not be reused as evidence for /stores/dallas-location/
- publish_rule: disagreement or unresolved interstitial → human review; never forced consensus
- hash_rule: write evidence file first, then hash the written file; store hash separately
- tie_break_rule: compare response shape against known-good reference URL on the same domain, not merely an alternate-IP HEAD