Root docs
Repository viewer
Legacy docs parity surface
Back to repository viewer
Repository document
`.xyz` Mirror Cutover Checklist
xyz-mirror-cutover-checklist.md
Boundary
This route preserves legacy markdown access inside the Next.js surface. The raw repository file remains authoritative.
Open raw file`.xyz` Mirror Cutover Checklist
This checklist is for adding `app.privatedao.xyz` as a mirror of the current review surface without breaking the existing GitHub Pages entrypoint.
Current review URL:
- `https://x-pact.github.io/PrivateDAO/`
Planned mirror:
- `https://app.privatedao.xyz/`
What Is Already Ready In-Repo
- 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 still keep the GitHub Pages URL as the canonical review surface during active judging
External Steps Still Required
- Create the DNS record for `app.privatedao.xyz`
- Point the mirror domain at the same static bundle host used for the review surface
- Ensure HTTPS is active and valid
- Confirm the mirror serves the same root Next.js export bundle and assets
- Verify that reviewer links remain unchanged in public submissions until mirror validation is complete
Cutover Validation
Validate both URLs manually:
- `https://x-pact.github.io/PrivateDAO/`
- `https://app.privatedao.xyz/`
Check the following at both URLs:
- Home page loads without console-breaking errors
- `/proof/?judge=1` still opens the proof view
- `/diagnostics/` still opens diagnostics
- top navigation works
- `Connect Wallet` remains 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 Do This Yet
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.
Evidence To Capture
When the mirror is live, capture:
- screenshot of home page on `.xyz`
- screenshot of `/proof/?judge=1` on `.xyz`
- screenshot of `/diagnostics/` on `.xyz`
- browser metadata inspection showing canonical/OG URL on `.xyz`
- one note confirming GitHub Pages still serves the same surface
Success Condition
The mirror is considered ready when:
- both domains serve the same UI and same asset set
- query-based entrypoints still work
- metadata follows the active origin
- no reviewer-facing link is broken
- no production claims are changed by the mirror itself