steward

Enforce module boundaries by validating changed files against the nearest AGENT.md, mapping changes per module, and checking ownership, dependencies, and interface contracts. This produces a stewardship report flagging critical violations and providing actionable remediation guidance.

A module change map groups changed files by their nearest AGENT.md module definition to verify interface contracts and ownership. It prevents cross-module breakages by detecting unauthorized dependency usage, enforcing required patterns, and validating code quality standards.

Perform cross-module impact analysis by mapping changed files and validating dependency rules against AGENT.md. This surfaces ripple effects in dependent modules, updates the Change History with stewardship entries, and returns a formal verdict guiding remediation to prevent downstream breakages.

Code review with AGENT.md supports automated quality standards enforcement by validating max file size, function complexity, and required or forbidden patterns. It automatically updates the Change History and returns a formal stewardship verdict with actionable guidance for violations.

Module boundary checks can target specific commits by validating their changed files against the nearest AGENT.md. The process constructs a module-change map for the targeted commits, performs ownership and interface contract checks, and generates a formal stewardship report.

You need AGENT.md to guard module contracts because it defines the ownership boundaries, dependency rules, and interface contracts required for validation. Without it, the steward cannot map changed files, perform quality checks, or generate a formal stewardship report.