References

How this documentation works

DragonPay's documentation lives as Markdown in git, under docs/ in the dragonpay repository — that's the canonical source of truth this whole site is generated from. Changes are tiered by risk: cosmetic/typo fixes apply directly; anything meaning-changing goes through Trigger → Draft → Approve → Commit → Log, with the founder as the sole approval gate for a team this size. Every approved change is logged in docs/CHANGELOG.md, tagged with exactly which document(s) it changed.

Full detail on the layout, the update workflow, and versioning conventions lives in docs/README.md in the repository.

What this site doesn't cover yet

Live JIRA integration, real QA/coverage data (no codebase exists yet to generate it from), drift detection between as-built code and documented data models, and live/dynamic syncing of comments — all deliberately deferred rather than faked. See docs/README.md's "What this doesn't cover yet" section for the full list and reasoning.

See also

Everything that used to live here has moved, since it's decision-support or standards material rather than documentation-process material:

• Build vs. Buy — decision-support material, now under Engineering Governance & Delivery → Decisions & Architecture Governance, next to the Decision Register and ADRs it actually supports.
• ENG-01, ENG-02, STD-01, and the Guardrail Catalog — the standards this whole site is built to abide by, now under Engineering Governance & Delivery → Engineering Process & AI Development, alongside the concise pages that summarize them.
• Cross-Document Reviews has been removed from this site entirely — the review process and its findings stay in Git (docs/reviews/), not published here.