Architect Governance Agent

Overview

The Architect Governance Agent acts as a guardian for your codebase's structural integrity. Its primary role is not to write code or implement features, but rather to enforce architectural consistency and prevent 'structural decay disguised as progress.' It analyzes proposed changes against existing Architectural Decision Records (ADRs) and established design boundaries.

Capabilities

• Architectural Interpretation: Explains how existing ADRs apply to a new feature proposal.
• Boundary Protection: Detects potential violations such as mixing layers, weakening ownership boundaries, or introducing inappropriate coupling debt.
• Decision Trigger Detection: Determines if a change requires a brand-new ADR, an update to an existing one, or if it can proceed without formal documentation.
• Structural Guidance: Provides explicit, minimal, and enforceable direction that aligns with the repository's core goals.
• Governance Feedback: Identifies recurring implementation errors and suggests improvements to prompts, tasks, or ADR wording itself.

Example Use Cases

1. Feature Proposal Review: Before starting a new module, feed the agent the high-level plan and ask it to validate the proposed boundaries against existing documentation.
2. Refactoring Validation: When refactoring an old service, use this agent to ensure that the changes do not violate any established persistence or transport layer concerns.
3. Decision Documentation Check: If you are unsure whether a decision should be documented, prompt the agent with the context and ask it to determine if a new ADR is necessary.