---
title: "Governance"
description: "2 posts about Governance, summarised, each linking to the original."
---

# Governance
> 2 posts about Governance, summarised, each linking to the original.

## Articles

### [Why your platform team shouldn't build an AI context layer (even though they probably could)](https://yomu.fyi/post/why-your-platform-team-shouldn-t-build-an-ai-context-layer-even-though.md)
- Company: [Stack Overflow](https://yomu.fyi/company/stack-overflow.md)
- Author: Eira May
- Published: Oct 15, 2026
- Type: Problem & solution

Many engineering teams mistakenly think building an internal AI knowledge context layer is as simple as standing up a vector database and wiring a RAG pipeline to documentation. In reality, a production-grade pipeline requires five continuously maintained stages—capture, deliver, govern, organize, and validate—where each stage’s long-term cost compounds as vendor APIs change and content ages. The critical innovation is the knowledge node, a living record carrying source, ownership, and an automatically computed trust score based on authorship, usage, recency, and conflicts. Trust decays over time, prompting owners for lightweight revalidation when confidence drops, and knowledge is automatically scoped to the correct audience without manual filing. For product companies not in the knowledge-infrastructure business, the compounding maintenance burden makes building this pipeline a distraction compared to leveraging existing platforms like Stack Internal.


### [What is agentic identity? Securing AI agents in 2026](https://yomu.fyi/post/what-is-agentic-identity-securing-ai-agents-in-2026.md)
- Company: [Twilio](https://yomu.fyi/company/twilio.md)
- Author: Ravleen Kaur
- Published: Oct 15, 2026
- Type: Explainer

AI agents are shifting from passive copilots to autonomous actors that book tickets, update calendars, and send messages without step-by-step human intervention. This shift introduces operational risks because traditional security controls designed for deterministic software cannot handle non-deterministic agent behavior, leading to over-permissioned agents, rogue behavior, and lack of real-time monitoring. Agentic identity is proposed as a governance layer built on three pillars: authentication (cryptographic keys), authorization (contextual permissions), and context (delegated link to end user). The framework includes short-lived session tokens, user context binding via token exchange, hard operational bounds on tool calls, human-in-the-loop gateways for high-risk actions, verified communication endpoints, and centralized logging with kill switches. By implementing these controls, organizations can deploy autonomous agents safely while maintaining visibility, containment, and auditability across all agent actions.