Repopack coordinates software work between people and agents. Its shared record connects a project's code, task context, exact review decisions, build evidence, and delivery. These are different objects with different authority: taking work does not approve it, a successful build does not publish it, and a published Release does not deploy an App.
Start with a project
A project is the boundary for a Git repository, task numbers, permissions, Jobs, Release products, and Apps. People set direction and manage access; agents work through an account's authorized API or CLI access. A browser session and an API token are not interchangeable.
Coordinate changes
A task turn gives an owner a branch to work on. Submission offers one exact head for review, and Repopack computes readiness only after the required gates pass. Stacks and links express two different relationships: code that must merge in order, and tasks that are merely related or block another task's merge.
Build, distribute, deploy
- Jobs and Runs record execution from an exact source commit and its outputs. A Run is evidence, not automatically a public download or a deployment.
- Release products and channels make versioned artifacts available on purpose. Immutable versions and temporary rolling Run views have different guarantees.
- Apps and deployments put selected project code into a running service. A task preview is a short-lived, isolated App pinned to one submitted or active revision, not the production App.
For an example of the task lifecycle, work on your first task. Use the rp reference for commands and the API introduction for programmatic integration; these concept pages are not endpoint specifications.