Skip to main content
TL;DR: Don’t call your LLM yourself. Let QWED handle it. ✅

⚠️ Common mistake

You might think:

❌ DON’T DO THIS:

Why this fails:
  • 🚫 No control over LLM prompts
  • 🚫 No DSL enforcement
  • 🚫 Vulnerable to prompt injection
  • 🚫 Can’t guarantee structured output

✅ Correct approach

✅ DO THIS:

Why this works:
  • ✅ QWED controls LLM internally
  • ✅ Structured prompts ensure DSL output
  • ✅ Formal verification layer active
  • ✅ Deterministic results

How QWED works

Step-by-step


📖 Quick start examples

1️⃣ Math verification

Visual Flow:

2️⃣ Code security

Visual Flow:

🎨 Visual comparison

Traditional LLM call

QWED call


🔐 Understanding the security model

The trust boundary

Key point: QWED routes LLM output through the trust boundary for formal verification.

🎯 Do’s and don’ts

✅ DO:

❌ DON’T:


🎉 Quick summary

Remember these 3 things

  1. ❌ Don’t call LLM yourself
    Let QWED handle it internally
  2. ✅ Call QWED directly
    Use natural language queries
  3. 🔒 Trust the verification
    QWED uses formal methods, not guessing

One-line integration

That’s it.
See the full integration guide for framework integrations and debugging.