TWP

Failure Log

The Foundation publishes its failures. This is an append-only feed documenting every known flaw, limitation, and error in the Protocol's methodology, security, and implementation. Entries are never deleted.

3 Recorded Entries

Documentation stack contradictions

MethodologyApr 10, 2026

Six major technology stack contradictions found across 14 pre-alpha documents (Firestore vs AlloyDB vs PostgreSQL, FastAPI vs Next.js, RabbitMQ vs Pub/Sub, etc.). Root cause: documents written at different points during rapid ideation without centralized reconciliation.

Remedy

All 14 documents audited and aligned to canonical stack: Next.js 16 + Supabase (PostgreSQL) + Vercel. Changes logged in CHANGELOG.md.

Discovered by: Platform Build Team

PII pipeline not yet implemented

SecurityApr 10, 2026

The Gate currently accepts essay submissions without PII de-identification. Submitted text is stored as-is in the database. No isolation between identity data and testimony content.

Remedy

PII detection + stripping pipeline scheduled for Phase 2 (Gate backend). Until then, no sensitive data should be submitted through the Gate.

Discovered by: Platform Build Team

Gate vetting is not operational

Gate SystemApr 10, 2026

The Gate UI exists but has no backend AI processing. Submissions are stored but not evaluated. The three-tier vetting pipeline (AI Sieve → AI Qualitative → Human Review) is not yet implemented.

Remedy

Full Gate backend scheduled for Phase 2. Gate page currently displays pre-alpha status warning.

Discovered by: Platform Build Team