WFGY/ProblemMap/GlobalFixMap/DevTools_CodeAI/cursor.md

11 KiB
Raw Blame History

Cursor: Guardrails and Fix Patterns

🧭 Quick Return to Map

You are in a sub-page of DevTools_CodeAI.
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 field guide to stabilize Cursor workflows that mix code chat, refactors, tests, retrieval, and tool runs. Use this to localize the failing layer, then jump to the exact WFGY fix page with measurable targets.

Open these first

Core acceptance

  • ΔS(question, retrieved) ≤ 0.45
  • Coverage ≥ 0.70 to the target file or section
  • λ remains convergent across three paraphrases and two seeds
  • E_resonance stays flat on long coding sessions

Fix in 60 seconds

  1. Measure ΔS Compute ΔS(question, retrieved) and ΔS(retrieved, expected anchor). Stable < 0.40, transitional 0.400.60, risk ≥ 0.60.

  2. Probe λ_observe Vary k for retrieval and toggle rerank. If ΔS stays flat and high, suspect metric or index mismatch. Reorder prompt headers and system policy. If ΔS spikes, lock the schema.

  3. Apply the module

  • Retrieval drift in code search → BBMC plus Data Contracts
  • Reasoning collapse during multi step refactor → BBCR bridge plus BBAM, verify with Logic Collapse
  • Dead ends in long edit plans → BBPF alternate paths with capped breadth

Typical Cursor breakpoints and the right fix


Deep diagnostics

  • Three paraphrase probe. Ask for the same change three ways. Log ΔS and λ per step. If λ flips on harmless phrasing, clamp with BBAM and tighten the edit schema using citations and spans.

  • Anchor triangulation. Compare ΔS to the expected file or function and to a decoy location. If similar, rebuild the index with consistent analyzer and normalization, then re-chunk with the checklist. Open: Retrieval Playbook, Chunking Checklist

  • Chain length audit. If entropy rises after 2540 steps, split the refactor plan and re-join with a BBCR bridge. Open: Entropy Collapse

  • Live instability. Add probes, backoff guards, and regression gates for long sessions. Open: Live Monitoring for RAG, Debug Playbook


Escalate and structural fixes

  • Index or metric mismatch. If ΔS stays high across seeds, rebuild with explicit metric and consistent casing. Verify with a small gold set. Open: Embedding ≠ Semantic

  • Role or policy drift. Move all non task policy to system, lock tool schemas, and require echo of the schema at each tool step. Open: Multi-Agent Problems, Data Contracts


Copy-paste prompt for the Cursor chat

You have TXTOS and the WFGY Problem Map loaded.

My Cursor issue:
- symptom: [brief]
- traces: ΔS(question,retrieved)=..., ΔS(retrieved,anchor)=..., λ states across 3 paraphrases
- context: repo path(s) and spans being edited

Tell me:
1) the failing layer and why,
2) the exact WFGY page to open from this repo,
3) minimal steps to push ΔS ≤ 0.45 and keep λ convergent,
4) a reproducible test to verify the fix.
Use BBMC, BBPF, BBCR, BBAM when relevant.

🔗 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 tension engine and early logic sketch (legacy reference)
⚙️ Engine WFGY 2.0 Production tension kernel for RAG and agent systems
⚙️ Engine WFGY 3.0 TXT based Singularity tension engine (131 S class set)
🗺️ Map Problem Map 1.0 Flagship 16 problem RAG failure taxonomy and fix map
🗺️ Map Problem Map 2.0 Global Debug Card for RAG and agent pipeline diagnosis
🗺️ Map Problem Map 3.0 Global AI troubleshooting atlas and failure pattern map
🧰 App TXT OS .txt semantic OS with fast bootstrap
🧰 App Blah Blah Blah Abstract and paradox Q&A built on TXT OS
🧰 App Blur Blur Blur Text to image generation with semantic control
🏡 Onboarding Starter Village Guided entry point for new users

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