# Mynd Feedback Loop Mynd Feedback Loop is the public-safe path for letting readers, teammates, and agents tell Joe what helped, confused, or should change in Joe's Mynd. ## Meaning The Mynd should learn from real use. The public feedback form lives here: https://josephniemchak.com/feedback The smallest useful feedback is: ```text This helped / did not help / confused me because... ``` If you are not sure what to send, use one sentence: - This helped because... - I got confused at... - I expected this path to... - This feels too private for public feedback, so I am not sharing details. Good public feedback names the page, word, path, or practice. Keep private details out: names, diagnoses, crisis details, client details, private relationship details, and anything meant for clinical care belongs somewhere more protected. If you are unsure, use the [[Public Private Boundary]] ten-second share check before sending anything. The only required public feedback choices are: 1. What kind of feedback is this? 2. Did it help? 3. Is it safe for Joe and Codex to review outside a private or clinical system? Use it when: - a [[Well-being Practice|well-being practice]] helped, did not help, or needs a clearer fit - a note created [[Clarity|clarity]] - a note created confusion - a word or definition does not match your meaning - a public path should be simpler, safer, or more useful - The Brotherhood source layer needs clearer language Keep feedback public-safe. Do not include private health details, client details, crisis details, private relationship details, or anything that belongs in a protected clinical or personal system. The loop is: ```text use the Mynd -> notice what happened -> send public-safe feedback -> review the signal -> revise the graph only when the result teaches something worth keeping ``` The aggregate report endpoint is: https://josephniemchak.com/api/mynd-feedback-report That report is for signal, not surveillance. It should help Joe and Codex see patterns such as: - which paths help - which notes confuse - which practices create useful results - which words need clearer shared meaning - where The Brotherhood language needs alignment The public revision rule is: ```text feedback signal -> smallest useful review target -> public-safe revision or no change ``` No-signal rule: ```text If the aggregate report has no review queue or practice signal, do not invent a pattern. Use [[Bounded Public Walkthrough]], a broken link, a verifier failure, or a real public-safe signal before changing the graph. No revision is a valid result. ``` Review in this order: 1. Start with `reviewSummary`. 2. Answer `decisionQuestion`: is there enough public-safe signal to make one small revision? 3. Use `topPriority` and `nextSmallRevision` to decide whether there is one small review target or no change. 4. Read aggregate signals before reading details. 5. Use `nextReviewQueue` for source, note, wording, path, and boundary revisions. 6. Use `practiceReviewQueue` for practice routing, fit-map, and result-language revisions. 7. Use `practiceSignals` when aggregate state/practice fit evidence would clarify a route. 8. Prioritize friction: did not help, more confused, fit felt wrong, or meaning difference. 9. Choose one review target: wording, link, practice fit, path order, source, boundary, or no change. 10. Preserve wording and links that created clarity or helpful action. 11. Keep private, clinical, crisis, or identifying details out of public notes. 12. If there is no signal, choose no change or run [[Bounded Public Walkthrough]]. 13. Revise only when the result teaches something worth keeping. ## Source Of Meaning This note comes from Joe wanting the Obsidian Publish site, JosephNiemchak.com, Codex, and the well-being system to live under one digital real estate and learn from real feedback. ## Relationship Over Time This loop should become more useful as people actually use the Mynd. If people share helpful feedback, Codex can summarize patterns and suggest revisions. If people share overly private information, the public boundary needs to become clearer. If nobody uses the form, the paths probably need better prompts, better placement, or more emotionally obvious questions. ## Links - [[Use Joe's Mynd]] - [[Practice Result Loop]] - [[Did This Help]] - [[Meaning Disagreement Flow]] - [[Shared Meaning Check]] - [[Practice Library]] - [[Start By How You Feel]] - [[Public Private Boundary]] - [[Bounded Public Walkthrough]] - [[For Agents]] - [[The Brotherhood Source Layer]] - [[The Brotherhood Care Path]] - [[Well-being]] - [[Action]] - [[Meaning]] ## Tensions The Mynd should learn from life without collecting more personal data than the public graph needs. The best feedback is small, honest, specific, and safe to review outside a private clinical or personal system. ## Question What did using the Mynd change, and what should the graph learn from that?