project-orchestrator:verification

To verify completion across multiple services in a monorepo, you need fresh test runs, correct git state, deployment confirmation, and living state doc updates. This approach enforces evidence-based verification across all affected branches and deployments before claiming completion.

Evidence-based verification for software deployment is the process of validating completion claims using concrete proof rather than assumptions. It coordinates multi-service tests, git state checks, and deployment verification to prevent drift and misalignment across affected services.

You can enforce fresh test runs and git state checks by applying strict verification rules across affected services and branches. This ensures no completion claims are accepted without fresh evidence, confirming deployment readiness and updating living state documents accordingly.

Yes, evidence-based verification is designed specifically for multi-service projects and monorepos where changes span services, branches, and deployments. It coordinates end-to-end verification to satisfy strict checks for tests, git state, and deployment status.

The best way to prevent drift and misalignment in CI workflows is to enforce an iron law requiring fresh verification evidence for any completion claim. This strictly validates tests, git state, and deployment status across affected services before merging.

You should avoid using automated deployment verification when you cannot run fresh tests or obtain concrete deployment confirmation across affected services. Without fresh evidence for git state and deployments, completion claims cannot be validated and may introduce drift.