<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Writing on Andreas Nissen</title><link>https://andreasnissen.dev/writing/</link><description>Recent content in Writing on Andreas Nissen</description><generator>Hugo</generator><language>en-us</language><copyright>© Andreas Nissen</copyright><lastBuildDate>Sun, 30 Aug 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://andreasnissen.dev/writing/index.xml" rel="self" type="application/rss+xml"/><item><title>Context and Control Are Different Layers</title><link>https://andreasnissen.dev/writing/context-and-control/</link><pubDate>Sun, 30 Aug 2026 00:00:00 +0000</pubDate><guid>https://andreasnissen.dev/writing/context-and-control/</guid><description>&lt;p&gt;Enterprise AI agents need context and control.&lt;/p&gt;&#10;&lt;p&gt;Context without control is unsafe. Control without context is blind.&lt;/p&gt;&#10;&lt;p&gt;They belong in the same architecture, and they should not collapse into the same layer. A missing relationship degrades an answer. A missing authorization check can trigger an action the user never permitted. Those failures have different consequences, owners, and tests.&lt;/p&gt;&#10;&lt;h2 id="context-answers-what-the-agent-should-know"&gt;Context answers what the agent should know&lt;/h2&gt;&#10;&lt;p&gt;Context is the evidence available for reasoning. It can include documents, structured records, tool results, conversation state, identity attributes, and the relationships between them.&lt;/p&gt;</description></item><item><title>From Screenshots to Governed Tools</title><link>https://andreasnissen.dev/writing/from-screenshots-to-governed-tools/</link><pubDate>Sat, 29 Aug 2026 00:00:00 +0000</pubDate><guid>https://andreasnissen.dev/writing/from-screenshots-to-governed-tools/</guid><description>&lt;p&gt;An agent can use a website by looking at pixels, clicking controls, and reading the result. That is powerful because it works without changing the application.&lt;/p&gt;&#10;&lt;p&gt;It is also the least explicit way to automate a consequential interface.&lt;/p&gt;&#10;&lt;p&gt;The agent has to infer what a chart means, which control maps to which action, whether the page changed, and whether an approval actually exists. The human sees a visual interface. The agent reconstructs a hidden API from appearance and behavior.&lt;/p&gt;</description></item><item><title>An Ontology Is More Than Context</title><link>https://andreasnissen.dev/writing/ontology-is-more-than-context/</link><pubDate>Fri, 28 Aug 2026 00:00:00 +0000</pubDate><guid>https://andreasnissen.dev/writing/ontology-is-more-than-context/</guid><description>&lt;p&gt;Context is what an AI system can see for the current task.&lt;/p&gt;&#10;&lt;p&gt;An ontology defines what that information means.&lt;/p&gt;&#10;&lt;p&gt;The terms are related, and they are not interchangeable. A long prompt can contain plenty of context without a stable model of the domain. An ontology can describe the domain even when only a small part of it is retrieved for one request.&lt;/p&gt;&#10;&lt;h2 id="context-is-task-specific-evidence"&gt;Context is task-specific evidence&lt;/h2&gt;&#10;&lt;p&gt;Context is assembled for a particular interaction. It can include instructions, documents, records, conversation state, retrieved passages, tool results, and user preferences.&lt;/p&gt;</description></item><item><title>Free AWS Builder Center Sandboxes Make Hands-On Learning Easier</title><link>https://andreasnissen.dev/writing/free-aws-builder-center-sandboxes/</link><pubDate>Thu, 09 Jul 2026 00:00:00 +0000</pubDate><guid>https://andreasnissen.dev/writing/free-aws-builder-center-sandboxes/</guid><description>&lt;p&gt;Want to go hands-on with Amazon Bedrock, agentic AI workflows, or AWS Transform custom without first setting up an AWS account and payment method?&lt;/p&gt;&#10;&lt;p&gt;AWS Builder Center now offers workshops with free, pre-provisioned sandbox environments. You can request an eligible environment, work through the lab, and let the temporary account expire when the session ends. The current sandbox window is eight hours, which is enough for a focused workshop without turning account administration into a separate project.&lt;/p&gt;</description></item><item><title>The Hard Part of Agentic AI Starts After the Demo</title><link>https://andreasnissen.dev/writing/agentic-ai-after-the-demo/</link><pubDate>Mon, 15 Jun 2026 00:00:00 +0000</pubDate><guid>https://andreasnissen.dev/writing/agentic-ai-after-the-demo/</guid><description>&lt;p&gt;The hard part of agentic AI is not building the agent.&lt;/p&gt;&#10;&lt;p&gt;It is everything that happens after the demo works.&lt;/p&gt;&#10;&lt;p&gt;A prototype can take a few days. Production is a different discipline. Agents reason in loops, invoke tools, change external state, keep memory, and sometimes produce different answers to the same request. The request-response playbook that teams have used for conventional applications does not cover all of those behaviors.&lt;/p&gt;&#10;&lt;p&gt;The &lt;a href="https://docs.aws.amazon.com/wellarchitected/latest/agentic-ai-lens/agentic-ai-lens.html"&gt;AWS Well-Architected Agentic AI Lens&lt;/a&gt; gives teams a framework for closing that gap. It adapts all six Well-Architected pillars to the way agentic systems actually behave: operational excellence, security, reliability, performance efficiency, cost optimization, and sustainability.&lt;/p&gt;</description></item></channel></rss>