WFGY/ProblemMap/GlobalFixMap/Safety_PromptIntegrity/prompt_injection.md

7.5 KiB
Raw Blame History

Prompt Injection — Guardrails and Fix Patterns

🧭 Quick Return to Map

You are in a sub-page of Safety_PromptIntegrity.
To reorient, go back here:

Think of this page as a desk within a ward.
If you need the full triage and all prescriptions, return to the Emergency Room lobby.

A focused guide to handle prompt injection attacks in RAG, agents, and orchestration.
Use this page when injected text hijacks your instructions, bypasses schema, or makes the model ignore contracts.


When to open this page

  • Responses contain leaked system prompt or hidden instructions.
  • Model obeys malicious user text like “ignore above and do X”.
  • Citations vanish after injection payload.
  • JSON / tool schema is broken by arbitrary free text.
  • Memory or context keys rewritten by injected content.

Open these first


Core acceptance

  • ΔS(question, retrieved) ≤ 0.45 even with injection attempts.
  • λ remains convergent across 3 paraphrases, does not flip under “ignore above” payloads.
  • Schema lock: JSON/tool calls validate against fixed schema.
  • Coverage ≥ 0.70 of target section even under noisy injection.

Fix in 60 seconds

  1. Detect abnormal ΔS drift

    • Compute ΔS(question, retrieved). If injected phrase raises ΔS ≥ 0.60, isolate payload.
  2. Enforce contracts

    • Wrap retriever and reasoner outputs in data-contracts.md.
    • Reject free text outside schema.
  3. Apply fences

  4. Verify stability

    • Re-run with paraphrase probes. Injection should not flip λ or erase citations.

Typical injection payloads → exact fix

Payload type Symptom Fix
Ignore-all override Model discards earlier rules role_confusion.md + schema locks
Citation erasure No references, only free text answer retrieval-traceability.md, data-contracts.md
Tool hijack JSON field replaced with instruction text json_mode_and_tool_calls.md
Role swap User prompt injected as “system” role_confusion.md
Memory overwrite Past state or keys corrupted memory_fences_and_state_keys.md

Copy-paste probe prompt

System: WFGY firewall active.
User input: {question}

Check:
1. Did retrieved snippet keep citations?
2. Did ΔS(question,retrieved) ≤ 0.45?
3. Did λ stay convergent under paraphrase?
4. Did JSON/tool call respect schema?

If any fail, return the failing layer + fix page.

🔗 Quick-Start Downloads (60 sec)

Tool Link 3-Step Setup
WFGY 1.0 PDF Engine Paper 1 Download · 2 Upload to your LLM · 3 Ask “Answer using WFGY + <your question>”
TXT OS (plain-text OS) TXTOS.txt 1 Download · 2 Paste into any LLM chat · 3 Type “hello world” — OS boots instantly

Explore More

Layer Page What its for
Proof WFGY Recognition Map External citations, integrations, and ecosystem proof
Engine WFGY 1.0 Original PDF based tension engine
Engine WFGY 2.0 Production tension kernel and math engine for RAG and agents
Engine WFGY 3.0 TXT based Singularity tension engine, 131 S class set
Map Problem Map 1.0 Flagship 16 problem RAG failure checklist and fix map
Map Problem Map 2.0 RAG focused recovery pipeline
Map Problem Map 3.0 Global Debug Card, image as a debug protocol layer
Map Semantic Clinic Symptom to family to exact fix
Map Grandmas Clinic Plain language stories mapped to Problem Map 1.0
Onboarding Starter Village Guided tour for newcomers
App TXT OS TXT semantic OS, fast boot
App Blah Blah Blah Abstract and paradox Q and A built on TXT OS
App Blur Blur Blur Text to image with semantic control
App Blow Blow Blow Reasoning game engine and memory demo

If this repository helped, starring it improves discovery so more builders can find the docs and tools. GitHub Repo stars