This checklist is for preserving the canonical production domain during any future hosting change without breaking the current reviewer surface.
Current canonical review URL:
https://privatedao.org/
- the root Next.js export is already the live surface
- the live frontend derives canonical and social URL metadata from the active origin
- self-links inside the app no longer hardcode only the review host
- copied evidence packets can reference the active frontend origin
- review artifacts now keep
https://privatedao.org/as the canonical review surface during active judging
- keep the canonical product domain serving the same root bundle and assets
- ensure HTTPS remains active and valid
- confirm any alternate host serves the same interface only if needed
- verify that reviewer links remain unchanged in public submissions
Validate the canonical domain manually:
https://privatedao.org/
Check the following at both URLs:
- Home page loads without console-breaking errors
/proof/?judge=1still opens the proof view/diagnostics/still opens diagnostics- top navigation works
Connect Walletremains visible and usable- live proof links open correctly
- copied judge / pilot / evidence packets use the active origin where appropriate
- Open Graph / canonical metadata reflects the active domain
Do not replace the canonical review links in:
README.md- submission answers
- reviewer packets
- generated attestations
until the mirror has been verified end-to-end.
Capture:
- screenshot of home page on
https://privatedao.org/ - screenshot of
/proof/?judge=1 - screenshot of
/diagnostics/ - browser metadata inspection showing canonical/OG URL on
https://privatedao.org/
The production domain is considered stable when:
- the canonical domain serves the same UI and asset set consistently
- query-based entrypoints still work
- metadata follows the active origin
- no reviewer-facing link is broken