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.