adinsights-scope-gatekeeper

Assess scope risk by evaluating proposed changes against governance rules to detect cross-folder modifications and architecture-sensitive edits. The gatekeeper analyzes git-changed files and explicit paths to produce a structured advisory packet with escalation routing and rationale.

Prevent cross-folder changes by applying a gatekeeper to requests spanning multiple top-level folders. It reads scope rules from YAML configuration, evaluates touched directories, and returns a structured packet with required reviewers and recommended actions.

Escalate API and data contract changes when a gatekeeper detects contract risk during scope evaluation. It automatically routes the advisory packet to contract guard or release readiness workflows while maintaining decision rationale for governance tracking.

Yes, you can govern project scope by defining rules in a YAML file. The gatekeeper reads these scope rules to identify touched folders, determine scope ownership signals, and generate advisory packets with tests and documentation updates.

Generate an advisory packet by running the gatekeeper on a prompt with optional path hints. It gathers evidence from git-changed files, produces rationale, tests, and recommended actions, and routes the structured packet to the appropriate reviewers.

Yes, pyyaml supports reading custom governance rules for scope evaluation. The gatekeeper relies on it to parse scope-rules.yaml, applying those rules to evaluate architecture-sensitive edits and return structured escalation routing packets.