scope-check

A branch audit analyzes your current branch diff against main, classifies changed files into owned, shared, or foreign categories, and outputs a structured report for safe handoffs.

Append-only enforcement for shared files in a branch audit works by inspecting git diffs to ensure changes only add content without modifying existing lines, preventing unauthorized edits in shared ownership areas.

File ownership classification in code review categorizes changed files into owned, shared, or foreign groups by inferring the target Agent, ensuring changes respect ownership boundaries during branch handoffs.

Yes, performing an automated pre-commit boundary audit requires git to inspect branch diffs against main, infer the target Agent, and determine file ownership classifications for the audit report.

The best way to ensure safe branch handoffs is to run a pre-commit boundary audit that infers the target Agent, classifies changed files into owned, shared, or foreign categories, and enforces append-only rules.

Your branch audit report flags foreign files during a code review because the diff analysis detected changes to files outside the inferred target Agent's ownership, restricting modifications to owned and append-only shared files.