AI NOW · EMERGING TECH NEXT
Platform engineering, agent infrastructure, and production systems built to scale and govern.
Browse all 8 articlesEditorial selection
A review of 19 employer descriptions shows how FDE responsibilities vary, where adjacent roles overlap, and what to clarify before hiring or applying.
Purposive employer-description review, retrieved 6 October 2026. Advertised expectations, not observed work or labour-market prevalence.
Follow your question
Browse automation engineering articles, or narrow the list to the question you have in mind.
Showing 8 of 8 articles.
Featured story included
A review of 19 employer descriptions shows how FDE responsibilities vary, where adjacent roles overlap, and what to clarify before hiring or applying.
Until x402, autonomous agents hit a hard ceiling at the moment they needed to pay for something. The model could decide; the agent couldn't transact. x402 closes that gap. The protocol, the implementations, the governance question, and what it means for the autonomous agent category.
Inaugural Build Log for GovPort. Why I extracted it from GoldenPath, the three architectural problems that forced the standalone direction, the Next.js + Vercel + Postgres + GitHub OAuth stack, and the cross-product framing where one tool watches both Scaletific and Automation Switch.
An agent harness is the runtime that turns an LLM into something that can act. How harnesses differ from frameworks, why the distinction matters, and what to look for in production.
CLAUDE.md and AGENTS.md often get treated as alternatives. They are complementary layers. CLAUDE.md is the Claude-specific overlay; AGENTS.md is the cross-platform base. Most repos benefit from both.
memory.md and 'Claude memory' get used loosely. Four mechanically distinct things hide behind the word across Claude Code, Claude.ai, ChatGPT, and Cursor. The taxonomy.
CLAUDE.md is the Claude Code instruction file. Loaded every session, scoped four ways, importable from AGENTS.md. The standalone explainer of what to put in it, where it lives, and how it stacks with the agent-config family.
AGENTS.md is the platform-neutral contract every AI agent in your repo reads. It works across Claude, Cursor, Copilot, Codex, and Gemini. The five-section anatomy and how to write one.
About this topic
Automation engineering is the discipline of building automation that survives contact with production. This pillar focuses on the infrastructure layer: platform engineering for automation teams, agent governance and compliance, CI/CD for workflow deployments, and the operational patterns that keep automated systems running reliably at scale. Articles here are written for engineering leads and platform teams who need to design systems that are auditable, maintainable, and resilient, with architectural context and governance considerations to inform implementation decisions.