Skip to content

PMP-004 Product Integration Guide

PMP-004 is the authoritative PotatoLabs guide for product integration with the PotatoLabs Developer Platform.

It defines how an individual product enters the platform, uses the shared developer workflow, and moves from repository creation through deployment and monitoring.

Lifecycle relationship

PMP-004 applies the canonical lifecycle defined in PMP-003 to a product and its repository.

Responsibility model

  • Developer: owns implementation, local validation, and product decisions within approved scope
  • AI development agent: assists with inspection, implementation, validation, and reporting within approved scope
  • GitLab: source-of-truth repository, merge workflow, and CI coordination
  • code-server: developer environment used for editing and review
  • Git: version control workflow and branch history
  • GitLab CI/CD: automated validation, build, release, and deployment workflow
  • Build system: produces reproducible artifacts
  • Release process: promotes validated artifacts into candidate and release states
  • Deployment system: installs or activates the release in the target environment
  • Monitoring and operations: confirm post-deployment health and ongoing stability

Standards hierarchy

  • PMP-001 defines architecture boundaries
  • PMP-002 defines engineering standards
  • PMP-003 defines execution phases
  • PMP-004 defines product integration using the PMP-003 lifecycle
  • PDP.md is the product-specific implementation and integration document, but it does not replace PMP-001 through PMP-004

PDP.md role

PDP.md should live at the repository root: <product-repository>/PDP.md.

PDP.md should describe product-specific implementation details such as:

  • Repository-specific setup instructions
  • Product-specific build and test commands
  • Runtime configuration guidance
  • Service endpoints and ports, where relevant
  • Deployment notes and environment-specific steps
  • Operational contacts or ownership notes
  • Product-specific integration constraints
  • Product-specific AI agent instructions

PDP.md should not redefine the higher-level standards.

Never refer to PDP.md simply as PDP.

Product model

A product is an individual PotatoLabs deliverable that uses platform capabilities as needed.

The standard model is:

  • GitLab repository as the source of truth
  • /srv/potatolabs/projects/<product> as the developer workspace and checkout
  • code-server as the developer environment
  • CI/CD as the automated validation and delivery workflow
  • Production runtime as the deployed product, which may use different directories or technologies than the workspace

Product structure

A product repository should clearly separate:

  • Source code
  • Tests
  • Build scripts
  • Runtime configuration
  • Documentation
  • Deployment assets
  • Operational notes