Decision Register¶
Grouped by status — Open and Proposed first (what still needs resolving), Decided and Deferred after. Required By names what depends on a decision; it's contextual information, not an urgency ranking -- see Immediate Open Decisions for the near-term-urgency subset.
Summary: 27 item(s) — DEFERRED: 5, OPEN: 22
Open¶
| ID | Area | Question | Required By |
|---|---|---|---|
| DR-001 | Application Stack | What primary server-side language and runtime will DragonPay use? | ENG01-01 |
| DR-002 | Application Stack | What backend application framework will DragonPay use? | ENG01-23 |
| DR-003 | Architecture | What initial physical application topology will DragonPay use -- a modular application,… | ENG01-02 |
| DR-004 | API | What primary transport/API approach will expose DragonPay application interfaces? This is the… | ENG01-04 |
| DR-005 | Data | What primary transactional database technology will DragonPay use? | ENG01-04 |
| DR-006 | Data | What primary data-access and schema-migration approach will DragonPay use? May ultimately include… | ENG01-04 |
| DR-007 | Workflow | What technology or implementation approach will provide durable payment workflow/orchestration? | ENG01-06 |
| DR-008 | Platform | Which cloud provider will host DragonPay? | ENG01-08 |
| DR-009 | Platform | What runtime/deployment platform will host DragonPay application workloads -- managed containers,… | ENG01-21 |
| DR-010 | Infrastructure | What Infrastructure as Code approach and tooling will DragonPay use? | ENG01-08 |
| DR-011 | Platform / Security | How will application secrets and environment/runtime configuration be managed? This is the… | ENG01-22 |
| DR-012 | Observability | What primary observability approach and platform will DragonPay use for logs, metrics, traces,… | ENG01-09 |
| DR-013 | Source Control | Where will DragonPay engineering source code be hosted? | |
| DR-014 | Source Control | What initial code repository topology will DragonPay use? Should capture decisions such as monorepo… | ENG01-02 |
| DR-015 | Delivery | What CI/CD platform and initial automated deployment mechanism will DragonPay use? | ENG01-10 |
| DR-016 | Testing | What primary automated test tooling will DragonPay use for the selected application stack? | ENG01-11 |
| DR-017 | Security / Identity | How will authenticated caller identity enter DragonPay and be trusted by the application? This is… | PH01-02 |
| DR-018 | Security / Data | How will FI/tenant isolation be technically enforced in the implemented system? Should address the… | PH01-01 |
| DR-019 | Data / Events | What infrastructure, if any, will transport asynchronous messages/events outside durable workflow… | ENG01-05 |
| DR-022 | Frontend | What framework will DragonPay use for DragonPay-owned web experiences? | CX01-08 |
| DR-023 | SDK / Frontend | What build/package/runtime approach will be used for the DragonPay Digital Banking SDK? | CX01-01 |
| DR-024 | Networking | What edge/API ingress, gateway, and external traffic-control architecture will DragonPay use? May… | ENG01-21 |
Proposed¶
None currently.
Decided¶
None currently.
Deferred¶
| ID | Area | Question | Required By |
|---|---|---|---|
| DR-020 | Data | Is an application/distributed cache required, and if so what pattern or technology will provide it? | |
| DR-021 | Data / Storage | What object/document storage technology will DragonPay use when non-relational binary/document… | PH12-05 |
| DR-025 | Security | How will DragonPay runtime components authenticate to each other if multiple trusted runtime… | ENG01-21 |
| DR-026 | Data Platform | What storage/query technology will support analytics/reporting workloads beyond the operational… | PH13-04 |
| DR-027 | Resilience / Operations | What production availability, backup, disaster-recovery, and regional-resilience strategy will… |