> For the complete documentation index, see [llms.txt](https://docs.wayfound.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.wayfound.ai/supervisor/potential-issues.md). # Potential Issues ## Potential Issues **Potential issues** are recurring behaviors or outcomes the Wayfound Supervisor notices that aren't yet covered by any of your guidelines. They're how the Supervisor surfaces "you might want a rule about this" without waiting for you to anticipate every case.
Each potential issue includes: * **A description** of the pattern. * **Severity** and the Supervisor's **confidence**. * **Supporting evidence** — the specific sessions where the pattern appeared. Click through to read the transcripts. ### Reviewing a potential issue For each potential issue, you can: * **Promote to a guideline** — turn the pattern into a guideline the Supervisor enforces going forward. Wayfound pre‑fills a draft guideline from the issue so you can refine and publish it. * **Confirm as expected** — tell the Supervisor the behavior is intended. It records this as an evaluation principle for the agent and stops flagging it. * **Acknowledge** — mark that you're investigating so the Supervisor doesn't keep re‑raising it while you decide. * **Dismiss** — mark it a false positive. The Supervisor won't re‑raise it unless the supporting evidence grows substantially. Every action teaches the Supervisor. Promoting, confirming, and dismissing all feed back into how it evaluates the agent — see [How the Supervisor Learns](/supervisor/how-the-supervisor-learns.md). --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.wayfound.ai/supervisor/potential-issues.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.