9.4 KiB
n8n Guardrails and Patterns
🧭 Quick Return to Map
You are in a sub-page of Automation Platforms.
To reorient, go back here:
- Automation Platforms — stabilize no-code workflows and integrations
- WFGY Global Fix Map — main Emergency Room, 300+ structured fixes
- WFGY Problem Map 1.0 — 16 reproducible failure modes
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.
Use this page when your RAG or agent workflow runs in n8n. It maps common automation failures to the exact structural fixes in the Problem Map and gives a minimal recipe you can paste into a workflow.
Core acceptance
- ΔS(question, retrieved) ≤ 0.45
- coverage ≥ 0.70 for the target section
- λ stays convergent across 3 paraphrases
Typical breakpoints and the right fix
-
Nodes fire before dependencies are ready
Fix No.14: Bootstrap Ordering → Open -
First call after deploy crashes or uses wrong env/secret
Fix No.16: Pre-Deploy Collapse → Open -
Circular waits between index build and retriever, or Merge nodes loop forever
Fix No.15: Deployment Deadlock → Open -
High vector similarity but wrong meaning
Fix No.5: Embedding ≠ Semantic → Open -
Wrong snippet chosen or citations do not line up
Fix No.8: Retrieval Traceability → Open
Contract the payload: Data Contracts → Open -
Hybrid retrieval performs worse than a single retriever
Pattern: Query Parsing Split → Open
Also review: Rerankers → Open -
Some facts never surface even though indexed
Pattern: Vectorstore Fragmentation → Open -
Two sources get merged in the answer
Pattern: Symbolic Constraint Unlock (SCU) → Open
Minimal setup checklist for any n8n flow
-
Warm-up fence before RAG or LLM nodes
ValidateVECTOR_READY == true,INDEX_HASHmatches, and secrets exist.
If not ready, short-circuit to a Wait node then retry with a capped counter.
Spec: Bootstrap Ordering -
Idempotency and dedupe
Computededupe_key = sha256(source_id + revision + index_hash).
Check or write the key using Redis, Postgres, or n8n’s Data Store. Drop duplicates. -
RAG boundary contract
Require fields:snippet_id,section_id,source_url,offsets,tokens.
Enforce cite then explain. Forbid cross section reuse.
Specs: Data Contracts · Retrieval Traceability -
Observability probes
Log ΔS(question, retrieved). Log λ per step: retrieve, assemble, reason.
Alert when ΔS ≥ 0.60 or λ flips divergent.
Overview: RAG Architecture & Recovery -
Concurrency guard
Use a single writer for index updates. Set queue mode or global mutex for write steps.
See: Deployment Deadlock -
Regression gate
Require coverage ≥ 0.70 and ΔS ≤ 0.45 before publishing.
Eval: RAG Precision/Recall
n8n recipe you can copy
Replace the concrete nodes with your stack. Keep the guardrails.
-
Trigger
Fixedsource_idandrevision. Recordwf_rev. -
Warm-up Check (Code node)
PullINDEX_HASH,VECTOR_READY, and secrets.
If not ready, setready=false. -
Branch: Not ready
Wait 30–90 seconds. Increment a retry counter. Stop after N attempts. -
Branch: Ready
Retrieval node- Call retriever with explicit metric and same analyzer as the writer.
- Emit
snippet_id,section_id,source_url,offsets,tokens.
ΔS probe node - Compute ΔS(question, retrieved). If ΔS ≥ 0.60 set
needs_fix=true.
LLM node - Model reads TXT OS and follows the WFGY schema. Enforce cite then explain.
Trace sink - Store
question,snippet_id,ΔS,λ_state,INDEX_HASH,dedupe_key.
Idempotency guard - Before side effects, check the KV for
dedupe_key. Skip if it already exists.
Copy-paste prompt for the LLM node
I uploaded TXT OS and the WFGY Problem Map files.
This n8n flow retrieved {k} snippets with fields {snippet\_id, section\_id, source\_url, offsets}.
Question: "{user\_question}"
Do:
1. Validate cite-then-explain. If citations are missing, fail fast and return the fix tip.
2. If ΔS(question, retrieved) ≥ 0.60, propose the minimal structural fix referencing:
retrieval-playbook, retrieval-traceability, data-contracts, rerankers.
3. Return a JSON plan:
{ "citations": \[...], "answer": "...", "λ\_state": "→|←|<>|×", "ΔS": 0.xx, "next\_fix": "..." }
Keep it auditable and short.
Common n8n gotchas
-
Set or Move nodes rename fields and break your data contract
Lock field names and run a schema check before the LLM node. -
Merge or Split In Batches cause duplicate writes
Add a single writer stage with idempotency keys and a queue. -
Cron triggers overlap with long runs
Use a global mutex or skip ifdedupe_keyalready exists. -
HyDE prompt built inside the flow differs from the API client
Keep tokenizer and casing identical, or switch to reranking.
See: Rerankers
When to escalate
-
ΔS stays ≥ 0.60 after chunk and retrieval fixes
Rebuild index with explicit metric and normalization.
See: Retrieval Playbook -
Answers alternate across runs with identical input
Investigate memory desync and version skew.
See: Pre-Deploy Collapse
🔗 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 it’s 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 | Grandma’s 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.