Layer 1: Local Gates
Pre-integration validation runs on the developer's machine or in CI. Includes linting, type-checking, unit tests, and formatting checks. Catches issues early before they enter the merge pipeline.
Concept
What is Merge Pyramid?
Merge Pyramid is a layered validation strategy that ensures content and code quality through progressive gates before integration.
The strategy works because Lex 2.0.0 provides stable contracts and AX guarantees (Frames, policy, lex.yaml) that runners can depend on without breaking.
The Three Layers
Layer 2: Integration Gates
Post-merge validation ensures compatibility when combining multiple branches. Runs integration tests, builds full artifacts, and validates cross-component interactions. Prevents conflicts in the combined codebase.
Layer 3: Deployment Gates
Final validation before production deployment. Executes smoke tests, security scans, performance benchmarks, and deployment readiness checks. Ensures the pyramid is stable at the apex.
Why Pyramid?
Progressive Quality Assurance
The pyramid structure reflects increasing confidence and scope at each layer. Fast, focused checks at the base catch most issues early. Slower, comprehensive checks at higher layers validate integration and deployment readiness. This approach minimizes feedback loops while maximizing quality.
Visual Overview
📊 Diagram placeholder: Merge Pyramid visualization
A visual representation of the three-layer validation strategy will be added here.
Ready to build your pyramid?
Start with Lex contracts, then let LexRunner handle the merge logic.