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.
Architecture decisions (ADRs)	When and how to record a significant technical decision, and how it is reviewed.
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.
Deployments	The one gated pipeline per environment: build gate, deploy order, verification, reading a failed run.
Rollback runbook	Getting a bad deploy back out: Cloud Run revisions, hosting artifacts, Terraform.
Epic (feature) branches	Long-lived feature branches per epic, merged atomically (trial).
Error taxonomy	Which errors are expected 4xx business outcomes and which are defects, and how each is logged and tracked.
Error severity and triage	What priority a production error gets and why, the weekly triage ritual, and how ticket status drives Datadog state.
Dependency updates	How Renovate bumps our dependencies, and what it is allowed to touch.
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.