AI coding agents can read files, inspect functions, summarize modules, and generate plausible changes. They don't reliably hold the full system in mind: architectural intent, component boundaries, quality attribute tradeoffs, dependency consequences, invariants, and the historical reasoning behind design decisions. Therefore that structural understanding remains a human responsibility.

This talk explains why architectural ownership becomes more important as agentic coding scales. Agents make local decisions that often look reasonable inside a single file or PR. Across dozens or hundreds of sessions, those decisions can erode conceptual integrity, introduce inconsistent abstractions, duplicate existing concepts, and move the system away from its intended architecture. No single diff may look disastrous. The accumulated drift can still become expensive and difficult to reverse.

The session presents a practical operating model for architectural ownership in AI-enabled teams: re-orienting agents before each session, tracing impact boundaries before directing changes, maintaining current architecture diagrams, using Mermaid diagrams as repo-level architecture artifacts, and running agent-assisted architectural drift scans. The goal is to keep the system coherent while AI accelerates implementation.

This talk directly references the author's Engineering Standards for Agentic Software Development, especially AO1, AO2, AO3, AO4, RF5, RF6, and SI3: https://www.linkedin.com/pulse/engineering-standards-agentic-software-development-edensoft-park-ki1se

Target audience: Software architects, principal engineers, staff engineers, platform leaders, and engineering directors responsible for long-lived systems.

Preferred Session Duration:
50 mins including Q&A