Immediate Open Decisions¶
Unresolved Decision Register items Engineering should actively address in the near term -- status is OPEN or PROPOSED and needed_imminently is true. Generated from the same canonical data on every build; never a separate record, backlog, approval process, or lifecycle state. An item leaving this state (DECIDED, DEFERRED, or needed_imminently set back to false) still remains visible, unchanged, in the full register.
| ID | Area | Question | Status | Required By | Proposed Direction | Resolution Authority |
|---|---|---|---|---|---|---|
| DR-001 | Application Stack | What primary server-side language and runtime will DragonPay use? | OPEN | ENG01-01 | FOUNDATION | |
| DR-002 | Application Stack | What backend application framework will DragonPay use? | OPEN | ENG01-23 | FOUNDATION | |
| DR-003 | Architecture | What initial physical application topology will DragonPay use -- a modular application,… | OPEN | ENG01-02 | FOUNDATION | |
| DR-004 | API | What primary transport/API approach will expose DragonPay application interfaces? This is the… | OPEN | ENG01-04 | FOUNDATION | |
| DR-005 | Data | What primary transactional database technology will DragonPay use? | OPEN | ENG01-04 | FOUNDATION | |
| DR-006 | Data | What primary data-access and schema-migration approach will DragonPay use? May ultimately include… | OPEN | ENG01-04 | FOUNDATION | |
| DR-007 | Workflow | What technology or implementation approach will provide durable payment workflow/orchestration? | OPEN | ENG01-06 | FOUNDATION | |
| DR-008 | Platform | Which cloud provider will host DragonPay? | OPEN | ENG01-08 | FOUNDATION | |
| DR-009 | Platform | What runtime/deployment platform will host DragonPay application workloads -- managed containers,… | OPEN | ENG01-21 | FOUNDATION | |
| DR-010 | Infrastructure | What Infrastructure as Code approach and tooling will DragonPay use? | OPEN | ENG01-08 | FOUNDATION | |
| DR-011 | Platform / Security | How will application secrets and environment/runtime configuration be managed? This is the… | OPEN | ENG01-22 | FOUNDATION | |
| DR-012 | Observability | What primary observability approach and platform will DragonPay use for logs, metrics, traces,… | OPEN | ENG01-09 | FOUNDATION | |
| DR-013 | Source Control | Where will DragonPay engineering source code be hosted? | OPEN | FOUNDATION | ||
| DR-014 | Source Control | What initial code repository topology will DragonPay use? Should capture decisions such as monorepo… | OPEN | ENG01-02 | FOUNDATION | |
| DR-015 | Delivery | What CI/CD platform and initial automated deployment mechanism will DragonPay use? | OPEN | ENG01-10 | FOUNDATION | |
| DR-016 | Testing | What primary automated test tooling will DragonPay use for the selected application stack? | OPEN | ENG01-11 | FOUNDATION | |
| DR-017 | Security / Identity | How will authenticated caller identity enter DragonPay and be trusted by the application? This is… | OPEN | PH01-02 | FOUNDATION | |
| DR-018 | Security / Data | How will FI/tenant isolation be technically enforced in the implemented system? Should address the… | OPEN | PH01-01 | FOUNDATION |