Professional architect sharing high‑quality architecture insights. Topics include high‑availability, high‑performance, high‑stability architectures, big data, machine learning, Java, system and distributed architecture, AI, and practical large‑scale architecture case studies. Open to ideas‑driven architects who enjoy sharing and learning.
The article walks through converting a chat‑based Hermes Agent into a maintainable, hand‑off‑ready system by building a control room, defining clear runtime and management files, applying security safeguards, and following a step‑by‑step production pipeline.
The article explains that effective use of Claude depends on establishing a stable personal work environment rather than merely crafting prompts, and it details 18 concrete actions organized into six layers—projects, personal instructions, fact sources, workflow cards, review loops, and boundaries—to create a reusable AI workbench.
The recent arXiv survey on Agent Skills maps the full lifecycle of skills—representation, acquisition, retrieval, and evolution—and warns that unchecked growth can turn a valuable process asset into technical debt, urging teams to enforce admission quality, robust routing, versioning, testing, and retirement mechanisms.
The article analyzes how Claude Code can operate reliably in monorepos and large codebases by reorganizing the repository into an agent‑friendly environment, detailing the seven‑step agentic loop, the role of CLAUDE.md, LSP navigation, Subagents, and a three‑layer architecture that balances context, execution, and governance.
From late April to mid‑May, OpenAI Codex, Claude Code, and Hermes each introduced an explicit /goal capability that transforms a one‑sentence prompt into a managed runtime object, enabling long‑running agents to maintain state, validation, budget, and pause/resume control within the Agent Harness.
The article dissects Codex’s /goal feature, showing how it adds persistent goal objects, a runtime lifecycle, completion auditing and budget handling, turning long‑running agents from a simple repeat‑loop into a robust, state‑driven engineering workflow.
The article dissects Agent Memory, explaining how past observations are written, managed, and read to affect future tasks, highlighting challenges such as relevance, decay, conflict, security, and offering practical design guidelines and architectural options for production‑grade AI agents.
The author reports a personal experiment where adding a concise CLAUDE.md file to 30 repositories reduced Claude Code's error rate from 41% to 3%, explains why such a tiny contract influences agent behavior, expands the original four Karpathy rules into twelve practical guidelines, and offers concrete advice on writing, structuring, and maintaining effective CLAUDE.md files.
The article analyzes the challenges of long‑running AI agents, showing that persistence alone is insufficient and that reliable hand‑over requires explicit specifications, external state files, drift mitigation, sub‑agents, and a verifiable evidence chain to keep the work understandable for the next model or human.
The article argues that AI programming is moving from asking whether models can write code to whether agents can autonomously locate, read, modify, execute, and verify context within real engineering environments, emphasizing the migration of context control from pre‑processing pipelines to agentic loops and the need for a robust harness.
