WebMCP Explained: How AI Works with a Live Web Page
A beginner-friendly explanation of why WebMCP was proposed, its two ways to describe page features, how it differs from adjacent technologies, and how to test it safely.
A beginner-friendly explanation of why WebMCP was proposed, its two ways to describe page features, how it differs from adjacent technologies, and how to test it safely.
A practical reading of AdCP Creative, Governance, and Trust specifications for connecting AI-generated ads to review, approval, and delivery.
A design for monitoring long-running agent behavior through minimal safety signals without centralizing conversations and documents.
A Verification-First design that links claims to evidence as they are produced and independently checks them before action.
An explanation of OpenMontage as a way to organize the stages, responsibilities, approvals, and records of AI video production rather than as a list of code features.
A guide to Palantir Ontology covering its origins, Objects, Links, Actions, Functions, permissions, applications, differences from knowledge graphs and RAG, and a practical PoC decision framework.
A research-based overview of Hermes Agent covering framework differences, use cases, extensions, and considerations for organizational use.
Google revealed how it builds, tests, and scales Agent Skills on August 4, 2026. This article explains the concrete practices and a practical SkillOps adoption path.
Using the Claude Code team's HTML workflow as a starting point, this article separates when to use Markdown, HTML, XML, and JSON for AI agent outputs.
A practical guide to coding-agent self-healing loops based on 2026 research and official implementations from OpenAI, Google, and GitHub, covering layered verification, stop conditions, permission boundaries, and human approval.
A plain-language guide to Dynamic Workflows in Claude Code: how multiple AI workers divide a job, which tasks fit, and how to plan outputs, limits, costs, and resumption.
How to record an AI workflow problem, cause, resolution, and prevention in lessons.md as a decision history that later work can verify.
A record of how a production build command ran while I was asking AI to make a separate change, and the approval-required rule I put in place afterward.
AI gives different answers to the same question, and it does not remember previous sessions. This article explains how I use the term Harness Engineering for this site's AI operation practices.
How harness drift separates shared rules from tool-specific configuration, and how synchronization checks detect the mismatch earlier.
A pre-delegation risk check for AI tasks, using reversibility, scope of impact, ease of verification, and the human decisions that should remain under human control.