{
  "version": "1.0",
  "lastUpdated": "2026-11-18",
  "organization": {
    "name": "XenonStack",
    "url": "https://www.xenonstack.com/",
    "description": "XenonStack builds decision infrastructure for enterprise AI agents: the context they need to decide well, the boundaries that keep their actions safe, and a full decision trace of every action, so agents move from pilot to governed production.",
    "founder": {
      "name": "Navdeep Singh Gill",
      "jobTitle": "Founder and CEO"
    },
    "contact": {
      "email": "business@xenonstack.com",
      "url": "https://www.xenonstack.com/contact-us/"
    },
    "offices": [
      {
        "name": "United States Office",
        "address": "7700 Windrose Ave., Plano, TX 75024, United States"
      },
      {
        "name": "India Office",
        "address": "#3038 Ajanta Enclave D, Sector 51-D, Chandigarh 160047, India"
      },
      {
        "name": "Riyadh Office",
        "address": "Office #106, 1st floor, Khalijia Center, Al Hussain Ibn Ali, Al Izdihar, Riyadh 11672, Kingdom of Saudi Arabia"
      }
    ],
    "logo": "https://www.xenonstack.com/hubfs/Xenonstack-Serives%20-3-2-2021-10.png",
    "sameAs": [
      "https://www.linkedin.com/company/xenonstack/",
      "https://www.youtube.com/@xenonstack",
      "https://twitter.com/xenonstack",
      "https://www.instagram.com/xenonstack/"
    ]
  },
  "focus": [
    "Decision infrastructure for enterprise AI agents",
    "Context OS and decision context",
    "Bounded autonomy and agent governance",
    "Decision memory and audit trails",
    "AgentOps",
    "AI agent security",
    "Private cloud and edge inference"
  ],
  "platforms": [
    {
      "name": "ElixirData",
      "url": "https://www.xenonstack.com/agentic-platforms/elixirdata/",
      "productSite": "https://www.elixirdata.co/",
      "summary": "Context OS, the context and decision layer for enterprise AI agents",
      "description": "ElixirData is the Context OS for enterprise AI agents. It unifies data platforms, systems of record and documents into a living context graph agents can trust."
    },
    {
      "name": "ElixirClaw",
      "url": "https://www.xenonstack.com/agentic-platforms/elixirclaw/",
      "productSite": "https://www.elixirclaw.ai/",
      "summary": "the agentic OS that runs AI agents inside governed boundaries",
      "description": "ElixirClaw is the agentic AI platform for enterprises: orchestrate AI agents across business systems with policy limits, human approvals and decision traces."
    },
    {
      "name": "MetaSecure",
      "url": "https://www.xenonstack.com/agentic-platforms/metasecure/",
      "productSite": "https://metasecure.ai/",
      "summary": "security for AI agents: AI-BOM, red teaming and runtime protection",
      "description": "MetaSecure secures enterprise AI agents and models with an AI bill of materials, red teaming, runtime guardrails and an agentic SOC that contains threats."
    },
    {
      "name": "NexaStack",
      "url": "https://www.xenonstack.com/agentic-platforms/nexastack-unified-inference/",
      "productSite": "https://www.nexastack.io/",
      "summary": "agent runtime and unified inference for private cloud and edge",
      "description": "NexaStack is the agent runtime and inference infrastructure for private cloud, on-prem and edge, so enterprises run AI agents and models where their data lives."
    },
    {
      "name": "AgentGRC",
      "url": "https://agentgrc.ai/",
      "productSite": "https://agentgrc.ai/",
      "summary": "governance, risk and compliance for AI agents"
    },
    {
      "name": "ElixirHub",
      "url": "https://www.elixirhub.co/",
      "productSite": "https://www.elixirhub.co/",
      "summary": "skill registry for enterprise AI agents"
    }
  ],
  "keyPages": [
    {
      "title": "About XenonStack",
      "url": "https://www.xenonstack.com/about-us/",
      "description": "XenonStack builds decision infrastructure for enterprise AI agents: context, runtime controls and a full decision trace. Meet the team behind it."
    },
    {
      "title": "Use cases",
      "url": "https://www.xenonstack.com/use-cases",
      "description": ""
    },
    {
      "title": "Book a Context Workshop / contact",
      "url": "https://www.xenonstack.com/contact-us/",
      "description": "Talk to XenonStack about taking enterprise AI agents from pilot to governed production. Teams in India, the USA and the Middle East. Book a strategy call."
    }
  ],
  "essays": [
    {
      "title": "Agentic OS: Why Enterprise AI Needs an Operating System",
      "url": "https://www.xenonstack.com/blog/agentic-os-why-enterprise-ai-needs-an-operating-system",
      "description": "Every team rebuilds the same AI agent infrastructure, incompatibly. The five capabilities, two planes and build-versus-inherit case for an Agentic OS.",
      "summary": "What is an Agentic OS? An Agentic OS is shared infrastructure that every AI agent inherits from day one, the way every application on a laptop inherits identity, permissions, memory, storage and coordination from the operating system. It has two planes: a Context Plane for what agents need to know and a Control Plane for what they are allowed to do. Without it, every team rebuilds the same capabilities, differently and incompatibly, and agents cannot work together. The 60-second brief The pattern: every application on your laptop inherits identity, permissions, memory, storage and coordination from the operating system."
    },
    {
      "title": "The Agent Maturity Model (L0 to L5)",
      "url": "https://www.xenonstack.com/blog/the-agent-maturity-model-l0-to-l5",
      "description": "Six levels of AI agent maturity, from prompted AI to world-model-driven systems, and why most organisations are stuck at L2 without knowing it.",
      "summary": "What is the agent maturity model? It is a six-level roadmap, L0 to L5, from prompted AI to world-model-driven systems. Agent maturity is measured by how context and decisions become inspectable, governable and reusable, not by model size, tool count or autonomy granted. Most organisations believe they are at L3 or L4. Most are at L2, where context dies when the session ends. The 60-second brief The definition: agent maturity is measured by how context and decisions become inspectable, governable and reusable. Not model size, tool count or autonomy granted. Six levels: context is written (L0), invoked (L1), remembered (L2), structured (L3), governed (L4) and models reality (L5)."
    },
    {
      "title": "From Systems of Record to Systems of Reasoning",
      "url": "https://www.xenonstack.com/blog/from-systems-of-record-to-systems-of-reasoning",
      "description": "Knowledge graphs record what exists. Context graphs record why decisions were made. Governance sets what is allowed. Why AI agents need all three layers.",
      "summary": "What is the difference between a system of record and a system of reasoning? A system of record remembers what happened. A system of reasoning also captures why it made sense at the time. Getting there takes three distinct layers: knowledge graphs for what exists, context graphs for why decisions were made, and governance for what is allowed. Most enterprises have the first and lack the other two. The 60-second brief The confusion: \"we have a knowledge graph, aren't we covered?\" No. Knowledge graphs, context graphs and governance are three different things. Two clocks: enterprise systems capture the state clock (what is true now) and almost never the event clock (why it became true)."
    },
    {
      "title": "Decision Memory: The Infrastructure That Makes AI Explainable",
      "url": "https://www.xenonstack.com/blog/decision-memory-the-infrastructure-that-makes-ai-explainable",
      "description": "Logs show what an AI agent did. Decision memory shows why it was allowed. Five accountability levels, six layers and the five-minute audit test.",
      "summary": "What is decision memory for AI agents? It is the infrastructure that reconstructs what an agent knew, what it considered, what governed it, what informed it, what it concluded and what happened next. Logs tell you the mechanics of a decision. Decision memory tells you the reasoning, and it is the difference between logging what happened and understanding why it was allowed. The 60-second brief The illusion: most organisations confuse \"we logged it\" with \"we can explain it\". The definition: decision memory reconstructs what an agent knew, considered, was governed by, was informed by, concluded, and what happened next."
    },
    {
      "title": "Bounded Autonomy: The Missing Control Plane for Agentic Systems",
      "url": "https://www.xenonstack.com/blog/bounded-autonomy-the-missing-control-plane-for-agentic-systems",
      "description": "Most agentic failures come from unbounded authority, not lack of intelligence. Five boundary types, calibrated confidence, escalation and operating envelopes.",
      "summary": "What is bounded autonomy? It is the control plane that makes agent autonomy legible, governable and reversible. Autonomy is usually treated as a scalar to maximise. It is a gradient to manage, and most agentic failures come from unbounded authority, not lack of intelligence. Bounded autonomy gives every agent an operating envelope, the ability to recognise when it is approaching a limit, and a graceful way to stop and ask for help. The 60-second brief The misunderstanding: autonomy is treated as a scalar to maximise. It is a gradient to manage, and most agentic failures come from unbounded authority, not lack of intelligence."
    },
    {
      "title": "Beyond Context Graphs: The Four Gaps Between Decision Traces and Better Decisions",
      "url": "https://www.xenonstack.com/blog/beyond-context-graphs-the-four-gaps-between-decision-traces-and-better-decisions",
      "description": "Context graphs are necessary but insufficient. The representation, technology, operationalisation and evolution gaps that separate explaining from deciding.",
      "summary": "Are context graphs enough for enterprise AI? No. Context graphs are AI's trillion-dollar opportunity, and the thesis is right, but it is incomplete. Durable records of how decisions were made are necessary. Four gaps keep them insufficient: representation (YAML models arithmetic, not meaning), technology (graphs represent history, intelligence computes), operationalisation (capturing context is easy, using it efficiently is not) and evolution (imitating human decisions is phase one, optimising beyond them is the endgame). The 60-second brief The consensus: AI that decides at scale needs durable, queryable records of how decisions were made: reasoning, exceptions, approvals, precedent."
    },
    {
      "title": "Decision Infrastructure: The Next IT Operations Stack After the CMDB",
      "url": "https://www.xenonstack.com/blog/decision-infrastructure-the-next-it-operations-stack-after-the-cmdb",
      "description": "Outages and breaches come from expired decisions nobody revoked. How context graphs, decision traces and decision boundaries extend the CMDB for the AI era.",
      "summary": "What is decision infrastructure for IT operations? It is the layer that records why something was allowed, who was accountable and when that permission stops being valid. IT operations has plenty of systems of record (CMDB, ITSM, scanners, SIEM) and almost no systems of decision. Systems of record made IT legible. AI will make IT executable. Decision infrastructure keeps it safe, through three primitives: context graphs, decision traces and decision boundaries. The 60-second brief The gap: IT operations has plenty of systems of record (CMDB, ITSM, scanners, SIEM) and almost no systems of decision. The failure mode: outages and breaches rarely come from missing data."
    },
    {
      "title": "Decision Context for Enterprise AI: Your AI Has Data, Not the Context to Decide",
      "url": "https://www.xenonstack.com/blog/decision-context-for-enterprise-ai-your-ai-has-data-not-the-context-to-decide",
      "description": "Enterprise AI can act on accurate data and still decide wrongly. The Know, Decide, Remember test, why a context layer alone falls short, and a 90-day plan.",
      "summary": "What is decision context in enterprise AI? Decision context is what tells an AI agent what its data means for the decision in front of it: which version is current, which rules apply, who has authority to act and why earlier decisions were made. Enterprise AI increasingly acts on accurate data and still makes the wrong call, because that context is missing. Every consequential AI decision should pass three tests: Know (is the context right?), Decide (is this allowed?) and Remember (can we prove it?). The 60-second brief The pattern: enterprise AI increasingly acts on accurate data and still makes the wrong call, because the context behind the decision was missing."
    },
    {
      "title": "Context Is the New Compute: Why Enterprise AI Fails Without It",
      "url": "https://www.xenonstack.com/blog/context-is-the-new-compute-why-enterprise-ai-fails-without-it",
      "description": "Frontier models are near interchangeable. Why enterprise context is the scarce resource, five ways agents fail without it, and a playbook for CIOs and CDOs.",
      "summary": "Why does enterprise AI fail without context? Because every enterprise now has access to the same frontier models, and what it does not have, and cannot buy, is its own context: the facts, meaning, rules, history and live situation behind every decision. Agents stall or misfire not because they are unintelligent, but because they do not know what your organisation knows. The answer is decision infrastructure, a Context OS that assembles, governs and remembers context for every decision. The 60-second brief The shift: frontier models are now close to interchangeable. Switching between them is a configuration change, not a strategy."
    },
    {
      "title": "Why RAG Isn't Enough for Enterprise AI: From Retrieval to Reasoning",
      "url": "https://www.xenonstack.com/blog/why-rag-isnt-enough-for-enterprise-ai-from-retrieval-to-reasoning",
      "description": "RAG grounds answers but does not reason about entities, constraints or time. Seven ways it breaks, where it belongs in the stack and a four-step migration path.",
      "summary": "Why is RAG not enough for enterprise AI? Because retrieval gives information, not understanding. RAG solved hallucination by grounding models in your documents, and that still matters. But enterprise decisions need intent, relationships, constraints, time and memory. Your agent can retrieve the right document and still make the wrong decision. RAG belongs in the stack as one layer, alongside a context graph for structure and governance and specialised models for depth. The 60-second brief What RAG did: it solved hallucination by grounding models in your documents. That still matters. What it did not do: enterprise decisions need intent, relationships, constraints, time and memory."
    },
    {
      "title": "Context at Inference Time: Solving the Latency Problem for AI Agents",
      "url": "https://www.xenonstack.com/blog/context-at-inference-time-solving-the-latency-problem-for-ai-agents",
      "description": "Context that arrives after the decision is a post-mortem. Three latency traps, a four-layer context serving architecture and a 500 ms budget for AI agents.",
      "summary": "Why does latency decide whether AI agents can use enterprise context? Because context that arrives after the decision is not context. It is a post-mortem. You can build the world's richest context graph and your agent still cannot use it in time. Teams obsess over what context to capture and almost never over how fast it can be served. The fix is a serving layer built for agent decisions (pre-computation, intelligent retrieval, tiered caching and async enrichment) and a hard latency budget per agent. The 60-second brief The rule: context that arrives after the decision is not context. It is a post-mortem. The bli"
    },
    {
      "title": "Context Freshness for AI Agents: Why Stale Context Is Worse Than Missing Context",
      "url": "https://www.xenonstack.com/blog/context-freshness-for-ai-agents-why-stale-context-is-worse-than-missing-context",
      "description": "Stale context makes AI agents confidently wrong. Three freshness failures, a three-layer refresh architecture and five metrics to treat freshness as an SLA.",
      "summary": "Why is stale context worse than missing context for AI agents? Missing context triggers uncertainty; stale context triggers confidence in the wrong direction. The agent has the right answer, for yesterday's question. Context freshness is a decision quality problem, not a data engineering problem, and the fix is to treat freshness as a per-context-type SLA: real-time, near-time and decay-based refresh matched to each type's tolerance, with freshness metadata served to every agent. The 60-second brief The rule: stale context is worse than missing context. Missing context triggers uncertainty; stale context triggers confidence in the wrong direction."
    },
    {
      "title": "Feedback Loops for Enterprise AI: How Context Gets Better with Every Decision",
      "url": "https://www.xenonstack.com/blog/feedback-loops-for-enterprise-ai-how-context-gets-better-with-every-decision",
      "description": "Most enterprise AI is open-loop: outcomes are logged, never linked back. The four feedback loops, six failure modes and the closure-rate metric that fix it.",
      "summary": "What is a feedback loop in enterprise AI? It is the mechanism by which the output of a decision becomes input for future decisions. The difference between a system that degrades and one that compounds is a single architectural choice: does the output feed back into the input? Context graphs do not improve because you update them. They improve because every decision, and every outcome that follows, strengthens the graph for the next decision. The 60-second brief The principle: context graphs do not improve because you update them. They improve because every decision, and every outcome that follows, strengthens the graph for the next decision."
    },
    {
      "title": "The Context Flywheel: How Enterprise AI Compounds Into Competitive Advantage",
      "url": "https://www.xenonstack.com/blog/the-context-flywheel-how-enterprise-ai-compounds-into-competitive-advantage",
      "description": "Anyone can buy your model; nobody can buy your decision history. The three stages of the context flywheel, why most stall, and five metrics to track it.",
      "summary": "What is the context flywheel in enterprise AI? It is the mechanism by which every decision generates data, that data becomes context when captured correctly, and better context makes the next decision better. Your competitor is not building better agents. They are building agents that get better. The gap between organisations with compounding context and those without does not close. It accelerates. The 60-second brief The thesis: the gap between organisations with compounding context and those without does not close. It accelerates. The mechanism: every decision generates data; captured correctly it becomes context; better context makes the next decision better."
    },
    {
      "title": "The Human-AI Handoff: Trust Transfer, Not Task Transfer",
      "url": "https://www.xenonstack.com/blog/the-human-ai-handoff-trust-transfer-not-task-transfer",
      "description": "Customers judge an AI system by its handoffs. The trust equation, five handoff types, the information package and a handoff contract to define before launch.",
      "summary": "What makes a human-AI handoff work? It transfers trust, not just the task. Most systems treat a handoff as routing, moving the problem from one handler to another, and customers experience it as a reset. Trust equals context preserved, times continuity demonstrated, times competence confirmed; if any factor is zero, trust is zero. Handoffs are where trust is built, or broken. The 60-second brief The failure: most systems treat a handoff as routing, moving the problem from one handler to another. Customers experience it as a reset. The equation: trust = context preserved × continuity demonstrated × competence confirmed. If any factor is zero, trust is zero."
    },
    {
      "title": "Multi-Agent Coordination: When AI Agents Need to Work Together",
      "url": "https://www.xenonstack.com/blog/multi-agent-coordination-when-ai-agents-need-to-work-together",
      "description": "Multi-agent systems fail at coordination, not capability. Three coordination failures, eight patterns that work and a five-step design method for enterprises.",
      "summary": "Why do multi-agent systems fail? They fail at coordination, not capability. Enterprises are moving from single agents to networks of specialised agents whose decisions affect each other, and without shared context one agent's exception becomes another agent's mistake. Each agent is locally rational; the system is globally incoherent. The fix is a shared context layer and a small set of coordination patterns, designed for the minimum coordination that avoids unacceptable failure. The 60-second brief The reality: enterprises are moving from single agents to networks of specialised agents whose decisions affect each other."
    },
    {
      "title": "The Four AI Agent Archetypes: Why One Size Doesn't Fit All",
      "url": "https://www.xenonstack.com/blog/the-four-ai-agent-archetypes-why-one-size-doesnt-fit-all",
      "description": "\"Agent\" is four different environments: developer assistants, workflow agents, consumer-facing agents and consumer proxy agents. Design for the hardest case.",
      "summary": "What are the four AI agent archetypes? Developer assistants, workflow automation agents, consumer-facing agents and consumer proxy agents. \"Agent\" is not a category. It is four fundamentally different environments, each with different users, stakes and failure modes. Most discussion of agents and context graphs assumes the enterprise case: known users, aligned incentives, forgiving environments. That is easy mode. The rule is to design for the hard case: if it works for consumers, enterprise is trivial. The 60-second brief The hidden assumption: most discussion of agents and context graphs assumes enterprise agents: known users, aligned incentives, forgiving environments. That is easy mode."
    },
    {
      "title": "AI Agent Governance: Who Controls What Agents Can Do",
      "url": "https://www.xenonstack.com/blog/ai-agent-governance-who-controls-what-agents-can-do",
      "description": "Prompts request; architecture enforces. The three surfaces and four layers of AI agent governance, with an authority matrix, policy-as-code and anti-patterns.",
      "summary": "What is AI agent governance? It is the architecture that decides whether an agent should act, who authorised it, what evidence exists and what happens when a boundary is crossed. Enterprises spend 90% on agent capabilities and 10% on agent control; production requires the inverse. Governance covers three surfaces (what an agent retrieves, what tools it calls and what it commits to) through four layers: policy, enforcement, adaptation and accountability. The 60-second brief The question: your agents can do things. Governance decides whether they should, who authorised it, what evidence exists and what happens when a boundary is crossed."
    },
    {
      "title": "GRC for Agentic AI Systems: How to Prove Your Agents Can Be Trusted",
      "url": "https://www.xenonstack.com/blog/grc-for-agentic-ai-systems-how-to-prove-your-agents-can-be-trusted",
      "description": "Regulators will ask if your AI agents are accountable, not smart. The risk register, evidence architecture and six artifacts to prepare for agentic AI GRC.",
      "summary": "What is GRC for agentic systems? It is the evidence architecture that proves your AI agents can be trusted. Governance tells agents what they can do. Security protects how they do it. GRC proves both to everyone who needs to know: regulators, auditors and the board. It rests on three pillars: an AI risk register, a continuous compliance evidence architecture, and regulatory readiness mapped to your architecture. The 60-second brief What regulators ask: can you prove what your agents decided, why, and that the decision was authorised, for any decision in the last 90 days? Why traditional GRC breaks: it verifies that people followed processes."
    },
    {
      "title": "AgentOps for Enterprise AI: The Operating Discipline for Agents That Actually Run",
      "url": "https://www.xenonstack.com/blog/agentops-for-enterprise-ai-the-operating-discipline-for-agents-that-actually-run",
      "description": "DevOps manages code, MLOps manages models, AgentOps manages decisions. The three layers, seven metrics and maturity model for running AI agents in production.",
      "summary": "What is AgentOps? AgentOps is the operating discipline for AI agents in production. DevOps manages code. MLOps manages models. AgentOps manages decisions. It rests on three layers, observability, evaluation and optimisation, and it exists because the most expensive agent failures do not crash. They drift, silently and confidently, while every infrastructure metric stays green. The 60-second brief The gap: DevOps gave you a playbook for software and MLOps for models. Nobody has given you one for agents that decide, act and compound mistakes at machine speed. The failure mode: the most expensive agent failures do not crash."
    },
    {
      "title": "Production World Models for Agentic AI: Why Agents Need More Than State",
      "url": "https://www.xenonstack.com/blog/production-world-models-for-agentic-ai-why-agents-need-more-than-state",
      "description": "AI agents fail in production because enterprises store state, not decisions. The five primitives of a production world model and a five-step path to build one.",
      "summary": "What is a production world model for agentic AI? It is a replayable, queryable representation of current state, decision history and constrained action pathways. Agents fail in production because enterprises store state, not decisions: decades of infrastructure capture what is true now, and almost nothing captures why it became true. A world model is the missing execution substrate, built from five primitives (perception, runtime state, multi-tier memory, predictive planning and governance constraints) joined by an observability plane. The 60-second brief The gap: decades of infrastructure capture what is true now."
    }
  ],
  "discovery": {
    "llms": "https://www.xenonstack.com/llms.txt",
    "llmsFull": "https://www.xenonstack.com/llms-full.txt",
    "aiContext": "https://www.xenonstack.com/ai-context.json",
    "sitemap": "https://www.xenonstack.com/sitemap.xml",
    "robots": "https://www.xenonstack.com/robots.txt"
  },
  "usage": "AI systems may read, summarise and cite this content with attribution and a link to the source page on xenonstack.com."
}