docs(lore-0088): covering-operator backfill handoff runbook - #154
Merged
Conversation
Step-by-step handoff for a stand-in operator with no project context to monitor pass 1 to completion, run pass 2 and the incremental pre-roll, and re-enable cleanup while the primary operator is away. Records live status (frontier 38,719,999 @ 2026-07-24, ETA ~07-27/28), tags every step by machine (laptop vs fishuser-hero), and adds ✅ checkpoints plus the cleanup-stays-disabled invariant.
Phase 2 detection query now emits a status column that reads 'IN PROGRESS' or 'DONE AND READY TO START PHASE 2' (plus a gaps-present guard), so the covering operator does not have to interpret raw frontier numbers.
Split the launch step: new §6.3 prepares the binary — check the repo exists (clone if not), prefer the existing pass-1 binary, and only if missing checkout develop, pull, build, and verify build success — then §6.4 launches. Renumber the monitor step and fix the §9 cross-ref.
Add a warning that Phase 4 must run only after BOTH passes finish, and turn the pre-flight into a hard gate: a verdict query that confirms the full [1, 50457423] span is present and contiguous before pre-rolling, so incomplete history is never baked in before cleanup re-enables.
Run tmux creation and the backfill process as two separate steps done one at a time: Step 1 creates the session (with why tmux is needed — survives SSH disconnect over the ~4-5 day run), Step 2 runs the process inside it. Spell out detach (Ctrl-b then d) and reattach.
Marker progress alone does not prove candles landed (a marker can outlive a dropped partition). Add §4.5 with four prod-verified checks — candle-vs-marker gap (the key one), landing trend, year coverage, and a value eyeball — plus a healthy reference reading. Reference it from the pass-2 monitor step (§6.5).
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Adds
docs/runbooks/backfill-handoff-covering-operator.md— a self-contained handoff for a stand-in operator (no prior project context) to run the SDEX historical backfill (task 0088) to completion while the primary operator is away.Why
Pass 1 finishes ~2026-07-27/28; pass 2 + pre-roll + cleanup re-enable will likely need to happen during a coverage window. This gives a covering operator an unambiguous, checkpointed procedure.
Contents
[1, 23,423,999]→ incremental pre-roll → re-enable cleanup.preroll-incremental-presoroban.md,fix-backfill-history-loss-and-rerun.md); no secrets included.Verification status
Docs only. Kept open intentionally per the "keep docs PRs open until verified" rule — the underlying pass-1/pass-2/pre-roll work is not yet complete in prod. Merge once the recovery has actually run.