Skip to content

docs: plan scalable rebuild architecture for backup restores - #864

Draft
kphunter wants to merge 1 commit into
mainfrom
codex/issue-863-rebuild-architecture-plan
Draft

docs: plan scalable rebuild architecture for backup restores#864
kphunter wants to merge 1 commit into
mainfrom
codex/issue-863-rebuild-architecture-plan

Conversation

@kphunter

Copy link
Copy Markdown
Contributor

Summary

  • add a decomposition-ready architecture plan for scalable rebuild-tiles execution after restore
  • document the supervisor-plus-bounded-workers direction, with explicit state, leasing, cancellation, disk-space safeguards, and rollout phases
  • link the new plan from the existing backup/import docs so future implementation work starts from the operator-facing context

Validation

  • nix-shell -p nodejs --run 'cd /private/tmp/hriv-issue-863-plan && /Users/kyle/projects/github/hriv/frontend/node_modules/.bin/prettier --check docs/rebuild-tiles-architecture-plan.md docs/admin-import-export.md docs/backup-and-disaster-recovery.md --config .prettierrc.json'

Closes #863

@devin-ai-integration devin-ai-integration Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Devin Review found 1 potential issue.

Open in Devin Review

Comment on lines +145 to +147
For the staged plan to evolve this into a scalable supervisor-plus-workers
rebuild architecture, see
[rebuild-tiles-architecture-plan.md](rebuild-tiles-architecture-plan.md).

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

📝 Info: Missing blank line causes paragraph merge in backup doc

At docs/backup-and-disaster-recovery.md:144-145, the new text ("For the staged plan...") immediately follows the previous sentence ("for how missing vs stale is determined.") without a blank line separator. In Markdown, this causes both sentences to render as a single paragraph. The preceding paragraph at lines 142-144 discusses API references and provenance docs, while the new text at 145-147 introduces the architecture plan — these are logically separate topics. A blank line between them would improve readability and make the architecture plan link visually distinct. This is cosmetic and doesn't affect link functionality.

Open in Devin Review

Was this helpful? React with 👍 or 👎 to provide feedback.

@kphunter
kphunter marked this pull request as draft July 10, 2026 18:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

design: plan scalable rebuild architecture for backup restores

1 participant