facts: lock retrorevolution audit as CONFLICT, split gate types

This commit is contained in:
Ty
2026-09-19 22:17:57 +00:00
parent 9118c8c91f
commit 548e79b509
@@ -2,6 +2,7 @@
category: project category: project
tags: audit, hallucination, gate-detection, blind-fact-check, tie-breaking tags: audit, hallucination, gate-detection, blind-fact-check, tie-breaking
stored: 20260919-214721 stored: 20260919-214721
updated: 2026-09-19T22:17:00Z
audit-pipeline skill created (2026-09-18) audit-pipeline skill created (2026-09-18)
@@ -12,10 +13,14 @@ Three corrections applied to the audit pipeline design after retrorevolution cas
## Failure evidence (required for grep / post-mortem) ## Failure evidence (required for grep / post-mortem)
- case: retrorevolution age-gate misread as 404 - case: retrorevolution age-gate misread as 404
- exact_url: NOT_CAPTURED_IN_THIS_ENTRY — operator must replace this line with the live URL that failed - exact_url: https://retrorevolution.com/stores/dallas-location/
- known_good_reference: https://retrorevolution.com/
- false_finding: BROKEN / Page not found (404) - false_finding: BROKEN / Page not found (404)
- actual_state: GATED — age verification wall ("Are You Over 18?" / CONFIRM-CANCEL) - actual_state: CONFLICT — do not publish until human verification past Cloudflare wall
- timestamp_failure: 2026-09-18 (skill created after this case) - 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..."
- timestamp_recorded: 2026-09-19T21:47:21Z - 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 - hash_rule: write evidence file first, then hash the written file; store hash separately
- tie_break_rule: compare response shape against a known-good reference URL on the same domain, not merely an alternate-IP HEAD - tie_break_rule: compare response shape against known-good reference URL on the same domain, not merely an alternate-IP HEAD