Shared Product and Engineering Platform¶
This site is DragonPay's single source of truth for product requirements, engineering architecture, quality, security, operations, decisions, and reference material. It's generated directly from the same Markdown files that are reviewed, approved, and version-controlled in this repository — nothing here is written separately from what actually gets committed.
How to navigate¶
- Product — what DragonPay does and why. Start with Product Overview and Vision and Glossary under Business if you're new here; Path to First Customer explains the current build sequencing. Hub Platform Epics (PH-01 through PH-13) are the shared payment-hub capabilities; Product and Experience Epics (PP-01, CX-01, OX-01, CI-01) are the specific P2P product, its channel experience, the operations console, and the first credit union integration.
- Engineering Governance & Delivery — how DragonPay engineering
decisions are made and how development is conducted. 0→1 Engineering
Setup is the concise startup control surface — Startup Overview for a
combined at-a-glance dashboard (counts and links, not a repeat of the
detail) and Setup Tasks & Checklists for practical 0→1 work.
Decisions & Architecture Governance holds the Decision Register (the
one place decisions are listed in full, Open/Proposed grouped ahead of
Decided/Deferred), ADRs, and Build vs. Buy. Engineering Process & AI
Development covers how engineering actually works, how Claude's
PM/ENG/Admin modes fit into that, the testing/Definition-of-Done bar,
and the full text of the Guardrail Catalog,
STD-01,ENG-01, andENG-02— the standards this whole site is built to abide by. - Engineering Architecture — how DragonPay is actually being built: security, identity/access, application patterns, data architecture, event-driven orchestration, infrastructure, observability, integrations, operations, multi-tenancy, and notifications. Every page says in plain language whether something is built, approved/planned, or still unresolved — DragonPay is pre-code, so most of this is a specification, not a description of a running system.
- References — the documentation process itself: how changes get proposed, approved, and logged.
A note on what's here vs. what's built¶
DragonPay has not started its engineering build yet. Everything in Product and most of Engineering Architecture is a specification for what will be built, not a description of a running system. Where a topic has no real content yet, the page says so explicitly rather than describing something that doesn't exist.