--- title: "Metadata Weekly Is Now Context and Chaos | Why We Changed the Name" url: "https://atlan.com/context-and-chaos/issue/metadata-weekly-is-now-context-and-chaos/" description: "After four years and 20,000+ subscribers, Metadata Weekly is becoming Context and Chaos. The field moved to context engineering. Here's why we're moving with it." keywords: "metadata weekly rebrand, context and chaos newsletter, context engineering, data & AI governance, metadata" --- > Atlan is hosting Context Conference, bringing together the leaders and builders at the frontier of giving AI the context it needs to understand their business. It runs online on October 28, 2026, from 11:00 AM to 2:00 PM ET. Atlan co-founder Prukalpa Sankar opens and closes the day. Leaders from AstraZeneca, BNY and Verizon share why they invest in context and what they get from it. Registrants get early access to The AI Context Gap, a new study from MIT Technology Review Insights. Register: https://atlan.com/context-conference/ **Metadata Weekly Is Now Context and Chaos (& Cats!).** An Editor's Note by Prukalpa Sankar, Co-founder & Co-CEO of Atlan, published April 2, 2026 (5 min read). Subtitle: The field moved to context engineering. The name finally caught up. After four years and 20,000+ subscribers, Metadata Weekly becomes Context and Chaos, the community for context engineers. The community contributors, practitioner-first lens and honest takes stay. About the author: Prukalpa started Context and Chaos (formerly Metadata Weekly) four years ago as a space for experts and practitioners to share what works in the trenches. Forbes 30 Under 30, Fortune 40 Under 40, TED Speaker. [LinkedIn](https://www.linkedin.com/in/prukalpa/). ## Why the bet was too small Metadata Weekly started on the bet that metadata would become one of the most important layers in the modern data stack, built for and by the community. Metadata instead became the foundation of enterprise AI. Every company doing serious work with AI agents hit a context problem, not a model or infrastructure problem: an agent asked to report on revenue could not tell that the CFO meant weighted pipeline, not total. The people maintaining column descriptions, lineage maps, business glossaries and data quality rules were building the most important layer in the enterprise AI stack without a name for it. ## The field got a name - Last June, Andrej Karpathy called it "context engineering." Tobi Luetke said it was the core skill set he had been waiting to see named. Glean, Notion, Writer and dozens of other companies converged on the term. - At Gartner's Data & Analytics Summit 2026 it became a theme. IBM and a16z published on it; Anthropic updated its MCP docs around it. - This community saw it first: Jessica Talisman on [ontologies, context graphs and semantic layers](https://metadataweekly.substack.com/p/ontologies-context-graphs-and-semantic) (forwarded by hundreds of readers); Manoj's [NL-to-SQL experiment showing 38% accuracy improvement](https://metadataweekly.substack.com/p/the-context-problem-nobodys-fixing) from adding high-signal context, one of the most-shared issues; Prukalpa's piece arguing [context graphs are the next trillion-dollar opportunity](https://www.linkedin.com/pulse/context-graphs-trillion-dollar-opportunity-who-actually-prukalpa--kxadc). - The last seven or eight issues of Metadata Weekly were already about context. ## What's changing The name and the scope. Context engineering is the discipline; the chaos is what building with AI in the enterprise feels like now: clean frameworks versus messy reality, a vendor landscape shifting weekly, new companies claiming the term, analysts drawing new quadrants, definitions still being written. The newsletter covers how practitioners build context layers, what works and fails, and where the industry is converging or still a mess. ## What's not changing It stays community-owned: community contributors, guest writers, real experiments, honest takes (expert-led content). ## What I keep coming back to There is a window: people who spent years building metadata practices and fighting for budget have the credibility to shape what context engineering becomes, and the community should write the definitions rather than watch. The first issue under the new name was announced for the following week. Every issue now ends with the Cats of Context and Chaos, a comic take on that week's topic. ## Related reads - [BI-Ready Is Not AI-Ready](https://atlan.com/context-and-chaos/issue/bi-ready-is-not-ai-ready/) - [Gartner D&A 2026: Where the Context Layer Became a Budget Line Item](https://atlan.com/context-and-chaos/issue/gartner-danda-2026-where-the-context-layer-became-a-budget-line-item/) - [Data Governance vs AI Governance: Why It's the Wrong Battle](https://atlan.com/context-and-chaos/issue/data-governance-vs-ai-governance-why-its-the-wrong-battle/) - [OpenAI's Frontier Proves Context Matters. But It Won't Solve It.](https://atlan.com/context-and-chaos/issue/openais-frontier-proves-context-matters-but-it-wont-solve-it/) - [Gartner D&A 2026: The Conversations We Should Be Having This Year](https://atlan.com/context-and-chaos/issue/gartner-danda-2026-the-conversations-we-should-be-having-this-year/) Context & Chaos is a community newsletter on context engineering, governance, architecture, discovery and the human side of data and AI work. All issues: https://atlan.com/context-and-chaos/ / Write for it: https://metadataweekly.substack.com/p/write-for-metadata-weekly