check-cross-layer

To ensure code, docs, and tests stay in sync, you validate consistency across runtime code, modeling documentation, validation scripts, and tests. This checks that contract fields, error propagation, and guardrails remain synchronized between layers.

Cross-layer validation verifies consistency across runtime code, modeling documentation, validation scripts, and tests. It ensures contract fields, error propagation, and guardrails are synchronized, preventing integration issues and drift between project layers.

To identify the scope of changes for a pull request, run git status and git diff --name-only. This identifies all affected files and layers, allowing you to search for usage sites of changed values to prevent drift across the codebase.

To prevent code drift and redundant patterns when refactoring, search for usage sites of changed values or patterns. This finds existing patterns, ensuring changes are consistently reflected and preventing redundant code across layers.

Yes, cross-layer validation works for financial data processing modifications. You can verify changes are correctly updated in runtime code, artifacts/modelling documentation, and relevant test cases before merging a pull request.