<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Governance on Fred</title><link>https://site.fredlab.dev/tags/governance/</link><description>Recent content in Governance on Fred</description><generator>Hugo</generator><language>en</language><copyright>Copyright (c) 2020-2024 Thulite</copyright><lastBuildDate>Thu, 09 Jul 2026 10:00:00 +0200</lastBuildDate><atom:link href="https://site.fredlab.dev/tags/governance/index.xml" rel="self" type="application/rss+xml"/><item><title>Continuous Evaluation, Made Visible: fred-agent-evaluator in Action</title><link>https://site.fredlab.dev/blog/continuous-evaluation-made-visible-fred-agent-evaluator-in-action/</link><pubDate>Thu, 09 Jul 2026 10:00:00 +0200</pubDate><guid>https://site.fredlab.dev/blog/continuous-evaluation-made-visible-fred-agent-evaluator-in-action/</guid><description>The Admin of a Fred team is accountable for how its agents behave — but accountability without visibility is just exposure. fred-agent-evaluator is what gives that accountability something to stand on, including custom, business-specific checks an Analyst can define just by describing them.</description></item><item><title>AI as an Engineering Partner — and How We Stay in Control</title><link>https://site.fredlab.dev/blog/ai-as-an-engineering-partner-and-how-we-stay-in-control/</link><pubDate>Wed, 08 Jul 2026 00:00:00 +0200</pubDate><guid>https://site.fredlab.dev/blog/ai-as-an-engineering-partner-and-how-we-stay-in-control/</guid><description>Fred is a full cloud-native agentic platform: speed and batch layers, Temporal workflows, identity propagation, ReBAC authorization, observability. We use AI assistants — for code, but also for backlogs, RFCs, and PMO tracking. This post is an honest account of the guardrails we built into the repository so that the humans, not the assistants, stay in control of a robust, industrial, maintainable application.</description></item><item><title>Beyond Agent Framework Wars: Fred and the Infrastructure Layer</title><link>https://site.fredlab.dev/blog/beyond-agent-framework-wars-fred-and-the-infrastructure-layer/</link><pubDate>Sat, 21 Feb 2026 10:00:00 +0200</pubDate><guid>https://site.fredlab.dev/blog/beyond-agent-framework-wars-fred-and-the-infrastructure-layer/</guid><description>Fred does not compete in the agent framework wars; it focuses on the production infrastructure layer for governed agent execution.</description></item><item><title>MCP vs REST for RAG in Fred: Why We Run Both</title><link>https://site.fredlab.dev/blog/mcp-vs-rest-for-rag-in-fred-why-we-run-both/</link><pubDate>Sun, 17 Aug 2025 10:00:00 +0200</pubDate><guid>https://site.fredlab.dev/blog/mcp-vs-rest-for-rag-in-fred-why-we-run-both/</guid><description>Fred uses REST for graph-driven RAG (Rico, Rico Pro) and MCP for tool-driven RAG (Dominic). Running both lets us measure latency, reliability, governance, and developer ergonomics—without changing our UI or schemas.</description></item></channel></rss>