| .. | ||
| images | ||
| README.md | ||
🧱 TXT — Bloc Bloc Bloc · Prompt Injection Firewall — Under Construction
👑 Early Stargazers: See the Hall of Fame — Verified by real engineers · 🏆 Terminal-Bench: Public Exam — Coming Soon
Bloc Bloc Bloc is a semantic firewall module for TXT OS — a defensive layer designed to neutralize prompt injection attacks before they reach the model’s decision logic. It doesn't hide prompts — it defuses intent.
Rather than simply blocking strings, Bloc Bloc Bloc analyzes semantic vectors to detect intent-level privilege escalations. The result is a text-native firewall you can understand, audit, and evolve.
This module is currently in early development.
Release timelines (Lite/Pro) to be announced soon.
🛡️ How It Works (Simplified)
Bloc Bloc Bloc uses a three-layer semantic gate system, built on the WFGY architecture and powered by the Drunk Transformer engine:
-
ΔS (Semantic Tension Gate)
Measures intent jump (ΔS > 0.6) to flag “overreaching” context shifts. -
λ_observe (Intent Direction Vector)
Maps prompt direction into knowledge regions; blocks calls to restricted zones or personas. -
Drunk Mode Disruptor
Intentionally introduces semantic entropy (WRI/WAI/WAY/WDT/WTF) to confuse multi-hop attacks.
These layers are composable, modular, and interpretable. You can inspect which layer fired, why, and how the response was altered.
🧩 Why It Works
Bloc Bloc Bloc doesn’t just block access. It corrupts the route an attacker takes to get there.
- 🧠 Context Isolation: Even if a prompt leaks, λ_observe limits its reach.
- 🧩 Intent Confusion: Drunk Mode injects jitter, making attack chains incoherent.
- 🔐 Semantic Labels: Knowledge chunks are tagged with access vectors — unauthorized voices can’t fetch what they don’t align with.
🌀 Core Algorithms Used
All logic can be encoded in text, making it safe to embed in a System Prompt.
ΔS = 1 - cos(θ)— catch vector leaps across semantic layersλ_observe = P(intent → region_tag)— learnable vector matchingdrunk_mode(t) = ε(t) + α·sin(ψ_seed)— obfuscate through modulation
Backend access control (e.g., FAISS / RAG) is applied only if all gates are passed.
Private embeddings and customer data remain server-side.
🔥 Use Cases
- Prevent prompt injection in public-facing AI tools
- Filter unauthorized knowledge access
- Protect RAG pipelines with fine-grained semantic fencing
🧪 Roadmap
- ✅ Basic gate logic
- ⏳ Red-Team stress tests (in progress)
- ⏳ OWASP LLM-01 compatibility validation
- ⏳ Dynamic persona tagging for multi-user contexts
🥂 “If your firewall can't stop a drunk attacker, it's not ready for the real world.”
— Bloc Bloc Bloc Team 🍷
🧭 Explore More
| Module | Description | Link |
|---|---|---|
| WFGY Core | WFGY 2.0 engine is live: full symbolic reasoning architecture and math stack | View → |
| Problem Map 1.0 | Initial 16-mode diagnostic and symbolic fix framework | View → |
| Problem Map 2.0 | RAG-focused failure tree, modular fixes, and pipelines | View → |
| Semantic Clinic Index | Expanded failure catalog: prompt injection, memory bugs, logic drift | View → |
| Semantic Blueprint | Layer-based symbolic reasoning & semantic modulations | View → |
| Benchmark vs GPT-5 | Stress test GPT-5 with full WFGY reasoning suite | View → |
| 🧙♂️ Starter Village 🏡 | New here? Lost in symbols? Click here and let the wizard guide you through | Start → |
👑 Early Stargazers: See the Hall of Fame —
Engineers, hackers, and open source builders who supported WFGY from day one.
⭐ WFGY Engine 2.0 is already unlocked. ⭐ Star the repo to help others discover it and unlock more on the Unlock Board.
