PMP-003 Phase Execution Guide¶
PMP-003 is the authoritative PotatoLabs guide for how a product moves from an idea to a production-operated product.
It defines the execution phases, gates, handoffs, and artifacts used by the PotatoLabs delivery workflow.
Canonical lifecycle¶
PMP-003 defines the canonical phase sequence:
IDEA -> REQUIREMENTS -> ARCHITECTURE -> PROJECT INITIALIZATION -> DEVELOPMENT -> INTEGRATION -> TESTING -> RELEASE CANDIDATE -> RELEASE -> DEPLOYMENT -> OPERATIONS -> MAINTENANCE / ITERATION
Delivery mechanics¶
PMP-004 applies this lifecycle to an individual product.
The source-code mechanics are:
Developer branch -> Development -> Commit -> Push -> CI validation -> Review / Merge -> Integration into target branch -> Build -> Test / validation -> Release Candidate -> Release -> Deploy
Lifecycle distinctions¶
- Merge is a source-code integration event.
- Release is artifact promotion.
- Deployment is runtime promotion.
Relationship to other standards¶
- PMP-001 defines architectural decisions and boundaries
- PMP-002 defines engineering standards and implementation rules
- PMP-003 defines execution phases and phase gates
- PMP-004 defines product integration using this lifecycle
Covered phases¶
- Lifecycle
- Phase 0 - Idea
- Phase 1 - Requirements
- Phase 2 - Architecture
- Phase 3 - Project Initialization
- Phase 4 - Development
- Phase 5 - Integration
- Phase 6 - Testing
- Phase 7 - Release Candidate
- Phase 8 - Release
- Phase 9 - Deployment
- Phase 10 - Operations
Phase gates¶
A phase may not be exited until the required inputs, validation, approval, and handoff criteria for that phase are satisfied.
Final checklist¶
A developer or reviewer should confirm that:
- The phase purpose is understood
- Required inputs are complete
- Required artifacts exist
- Validation has passed
- The approval or gate has been satisfied
- The handoff to the next phase is explicit
- Any exceptions are documented