<?xml version="1.0" encoding="UTF-8"?><urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9"><url><loc>https://openharness.net/blog/</loc><lastmod>2026-10-25</lastmod></url><url><loc>https://openharness.net/blog/2026/10/25/building-checkpoints-into-automated-workflows-before-errors-spread-downstream/</loc><lastmod>2026-10-25</lastmod></url><url><loc>https://openharness.net/blog/2026/10/24/designing-support-chat-handoffs-based-on-model-disagreement/</loc><lastmod>2026-10-24</lastmod></url><url><loc>https://openharness.net/blog/2026/10/23/checking-an-open-source-ai-stack-s-failure-modes-before-production-load/</loc><lastmod>2026-10-23</lastmod></url><url><loc>https://openharness.net/blog/2026/10/22/setting-up-a-team-decision-log-for-multi-model-ai-outputs/</loc><lastmod>2026-10-22</lastmod></url><url><loc>https://openharness.net/blog/2026/10/21/mapping-handoff-points-in-multi-step-ai-workflows-before-errors-compound/</loc><lastmod>2026-10-21</lastmod></url><url><loc>https://openharness.net/blog/2026/10/20/support-chat-escalation-rules-that-hold-up-under-pressure/</loc><lastmod>2026-10-20</lastmod></url><url><loc>https://openharness.net/blog/2026/10/19/auditing-the-parts-of-an-open-source-ai-stack-you-can-t-see-from-the-repo/</loc><lastmod>2026-10-19</lastmod></url><url><loc>https://openharness.net/blog/2026/10/18/running-team-prompts-through-several-models-before-you-trust-one-answer/</loc><lastmod>2026-10-18</lastmod></url><url><loc>https://openharness.net/blog/2026/10/17/building-a-review-gate-into-automated-ai-workflows-before-outputs-ship/</loc><lastmod>2026-10-17</lastmod></url><url><loc>https://openharness.net/blog/2026/10/16/vetting-support-chat-answers-before-they-reach-your-customers/</loc><lastmod>2026-10-16</lastmod></url><url><loc>https://openharness.net/blog/2026/10/15/evaluating-an-open-source-ai-stack-before-you-commit-to-it/</loc><lastmod>2026-10-15</lastmod></url><url><loc>https://openharness.net/blog/2026/08/15/stress-testing-support-chat-replies-across-several-models-before-customers-see-them/</loc><lastmod>2026-10-24</lastmod></url><url><loc>https://openharness.net/blog/2026/08/15/running-ownership-reviews-for-ai-outputs-before-your-team-acts-on-them/</loc><lastmod>2026-10-24</lastmod></url><url><loc>https://openharness.net/blog/2026/08/14/mapping-where-automated-ai-steps-can-silently-drift-before-you-scale-them/</loc><lastmod>2026-10-24</lastmod></url><url><loc>https://openharness.net/blog/2026/08/14/designing-workflow-automation-checkpoints-before-model-errors-spread-downstream/</loc><lastmod>2026-10-24</lastmod></url><url><loc>https://openharness.net/blog/2026/08/13/questions-to-ask-before-trusting-an-open-source-ai-stack-s-lock-in-exit-path/</loc><lastmod>2026-10-24</lastmod></url><url><loc>https://openharness.net/blog/2026/08/11/running-operator-briefings-through-parallel-models-before-your-team-acts/</loc><lastmod>2026-10-24</lastmod></url><url><loc>https://openharness.net/blog/2026/08/10/stress-testing-workflow-steps-for-silent-failures-before-they-scale/</loc><lastmod>2026-10-24</lastmod></url><url><loc>https://openharness.net/blog/2026/08/10/designing-support-chat-transcript-reviews-that-catch-quiet-errors-early/</loc><lastmod>2026-10-24</lastmod></url></urlset>