Operations

This page is an overview, linking to where each operational concern is actually specified rather than duplicating it.

Running payments day to day

OX-01 is the shared operations experience DragonPay and CU staff use to search payments, review a payment's lifecycle/timeline, work exception Cases, and review reconciliation results. PH-10 (Reconciliation) verifies DragonPay's records against the CU's real evidence; PH-11 (Case Management) is where a human resolves what automated workflow, risk, or reconciliation couldn't. PH-13 (Operations and Reporting) is the read-side capability search/detail/ reporting is built on.

Standing up the environment

ENG01-14 (account/access bootstrap): the initial founder-level root access to Azure, GitHub, Temporal Cloud, Datadog, and Auth0, and the stated trigger for moving off it to Terraform/CI-governed, least- privilege access as the team grows.

ENG01-15 (cost/budget governance): Azure budget/alert thresholds on Terraform-provisioned resources — visibility, not an approval workflow, appropriate to team size.

ENG01-16 (backup/disaster recovery): a lean, stage-appropriate backup/restore policy for the ledger via the confirmed managed PostgreSQL service's own managed backup capability (engine current lean: PostgreSQL, DR-005, open; service current lean: Azure Database for PostgreSQL — open, ENG-01 §4/Decision Register ENG02-25), with a stated RPO/RTO and at least one documented test restore before any customer-facing environment goes live.

What's not built yet

Everything above is a specification, not a running operation — DragonPay is pre-code. There is no live environment to operate today.