Perci Engineering Docs

The single source of truth for how the Perci engineering team works: how tickets move, who owns what, how we review and ship code, and how the platform is built.

These docs live in the monorepo (docs/). That is deliberate:

• Discoverable by tools. Coding agents grep the repo and read AGENTS.md/CLAUDE.md; in-repo docs are found by default. A wiki is not.
• Updated atomically. A behaviour change and its doc update land in the same PR, reviewed together, so docs cannot silently drift from the code.

This site is the rendered view; the markdown in docs/ is the source. Edit the markdown in a PR and the site rebuilds on merge.

Start here

• Product process (DPPD) — how an idea becomes shipped work: Discovery → Proposal → Plan → Delivery.
• Ticket lifecycle — how a PPL ticket moves from idea to done.
• Team ownership — who owns which area and who to ask.
• PR reviews — branch naming, review and merge policy.
• Branching & releases — develop → release → main, and hotfixes.
• Epic branches — long-lived feature branches per epic (trial).
• Running locally — get the apps and backend up.
• API reference — OpenAPI / Redoc pages for the BFFs and API.

Other docs

• Architecture — Medplum auth, Twilio voice, and platform internals.
• Frontend — the feature-based clean architecture guide.
• Operations — CI workflows, preview deployments, Cloud Run, observability.

Repository conventions

Day-to-day agent and contributor rules (commands, code style, MCP servers) live in AGENTS.md at the repo root. This site covers process and architecture; AGENTS.md covers mechanics. They cross-reference each other.