integration-milestone

name	integration-milestone
description	Define and run an integration milestone that proves independently developed work combines into one meaningful program outcome.

Integration Milestone

Use when this procedure is the primary professional method needed for the assignment.

Procedure

1. Confirm the decision or outcome this work must support, its scope, owner, constraints, and definition of success.
2. Establish the evidence baseline using workstream deliverables, versions, environments, interfaces, test plans, and acceptance criteria. Do not fill material gaps with assumptions when they can change the result.
3. Identify required components/contracts, freeze acceptance scenario, sequence environment/data readiness, assign validation owners, and capture integrated evidence plus open gaps.
4. Exercise realistic edge, failure, transition, or exception cases that could invalidate the result; record unresolved uncertainty explicitly.
5. Validate the output against the original outcome and any neighboring professional contracts so this skill does not silently absorb another specialist's authority.
6. Record the resulting artifact, measurements, decisions, provenance, and handoff information needed for another owner to reproduce or continue the work.

Quality gate

The milestone proves the assembled cross-project behavior rather than collecting separate team status reports.