Engineering

How the Perci engineering team works, end to end. Each page is the canonical description of one process. If reality and a page disagree, fix the page in the same PR that changes reality.

Page	Answers
Product process (DPPD)	How an idea becomes shipped work: Discovery → Proposal → Plan → Delivery.
Delivery	The Delivery stage in detail: Jira statuses, transitions, automations and the backlog.
Team ownership	Which team owns which part of the platform, and who to ask.
PR reviews	Branch/PR naming, how reviews work, what blocks a merge.
Branching & releases	The develop → release → main flow and hotfixes.
Releasing	The exact release runbook: cut-release, versioning, hotfixes, DORA metrics, troubleshooting.
Epic (feature) branches	Long-lived feature branches per epic, merged atomically (trial).
Running locally	Getting the Flutter apps and backend running on your machine.

Keeping these honest

Every change to the platform that alters one of these processes should update the relevant page in the same PR. Reviewers: treat a missing doc update like a missing test.

Placeholders need confirming

Pages below contain CONFIRM admonitions where exact status names, team names, or ownership need to be filled in by the team. Search the repo for CONFIRM and resolve them before treating this as authoritative.