# Shipping # Shipping The pipeline: repository operations, assessment, build, deployment, compliance and the orchestration that runs them in order. How does code get from a repository to a running service? Each stage is a product with its own API, and the sequence is a separate product that runs them. Keeping the stages independently callable is what lets one run alone — assessing a repository without deploying it is a normal operation rather than a special mode. ## Products In the order the value chain runs. 1. Assess has a recorded specification 1. Build has a recorded specification 1. Code has a recorded specification 1. Comply has a recorded specification 1. Deploy has a recorded specification 1. Health has a recorded specification 1. Pipeline has a recorded specification ## How the chain fits together The assessment stage carries one rule that shapes everything downstream: every endpoint declared in a deployment manifest had to appear in the API definition, checked on every build, blocking the build where it did not. A service's contract surface therefore lives at a canonical path in the repository rather than in a document beside it.