Repository navigation
docs: the SMDC step's runbook compacted to a state page, the run log left to git history (mig-runbook) - #473
Merged
Merged
Conversation
…rt proved and the current procedure, the run log left to git history (mig-runbook) Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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
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.
docs/foundation-smdc-step.mdbecomes a state page: what each of the thirteen parts proved, the current procedure, and the run log left to git history (git show 940e29b5:docs/foundation-smdc-step.md,git log -p). mig-runbook task 1 (planner brief, queue linemig-runbook).What and why
The page was a 9,076-line run log at
940e29b5; it is now 554 lines:## Part 1to## Part 13, one section each: what the part proved, its numbers, the PRs. Step numbers the code and rapid_docs cite (part 7 step 6, part 9 step 2, part 10 step 5, part 11 steps 1, 2, 7, part 12 steps 1, 3, part 13's named steps) stay findable.## Current procedure: the environment, bring-up of a freshpublicwith its grants and check, the image, a run (pointing to rapid_docs' loop page, Starting a night, for the verbatim recipe), the reference bounds of every dataset, the check, the gate, the exit codes, same-bytes comparisons and the instance-type caveat for packet equality, never prove on:85or:86, the settings in force. Every command checked against the tip's--help(run,job local|submit|run|wait,official change|undo,publish,loop).## Validation(made current:validate_run.py's checks at the tip, the catalog check in place of the chain, part 6's outcomes attributed to runs 9 and 10) and## If a step fails(made current:job submit --job, CloudWatch INFO lines,rp job localto reproduce a difference).## What remains: part 13's list, plus the earlier parts' items no later part closed, each named with its source.scripts/check-public-safety.sh: the allowlist entry keyed on this file (634500218910, a Batch job UUID fragment in part 6's old table) is gone with the table, so the entry is removed, and with it the script's own self-entry for the same string, which no file now holds (the script's comment: an entry allows one file's matching string; anything new blocks).Files
docs/foundation-smdc-step.mdscripts/check-public-safety.shPer part: kept, and superseded numbers dropped
opsuntouched), the grants (now Current procedure's bring-up, with part 6'srapid_readlines), the prototype rulingpghelper and the before/after row counts; the earlier draft's grant-count methoddatabase/2026-10-24-object-catalog.sqlcites part 3 for it)psfstage, 0.23 → 0.16, breadth totals; step 2's bound table (cited by rapid_docs' loop page and COMMON), F146's bound added as a row[gate]'s comment)star_sigma_pxas first stored (PR 352)Divergences
database/2026-10-24-object-catalog.sqlcites "part 3" for the default privileges, which were part 1 step 3; part 3's section names them, so the reference resolves and the dated file is not edited (implementation choice: no change to an applied schema file).catalog.py,memory.py,metrics.py,intake_openuniverse.py, the overlays,foundation-thin.toml's "Results of part 10"); each cited step is still named in its part's section, so none was edited (out of scope: code and settings).Measurements
940e29b5)## Part Nsectionsscripts/check-public-safety.shReferences at the tip, each resolving:
database/2026-10-24-object-catalog.sql:12(part 3),database/README.md:22(the dated files' rule, the file),scripts/validate_run.py:7(## Validation),scripts/check-public-safety.sh(entry removed with its string); rapid_docssystem/foundation.md:844,system/loop.md:70(part 9 step 2),system/datasets.md(part 12 step 3, part 13 steps): the rapid_docs PR fixes the sentences that described the page as a procedure of eleven parts and as holding full tables.Improvements seen
rebuildatefc03fc6" (rapid_docssystem/loop.md); a later behaviour change will need the stamp moved; seen, not applied.Session notes
loop.md:70,datasets.md:140,178,212,foundation.md:1207,1474,1510); agit grep -i runbookover both repos found them.What the next task must know
A new planner step's record is one row in part 13's table (what stands, runs, PRs), and in-place edits to Current procedure and What remains where the step changes them; no step sections, no results section.
Left
Caltech-IPAC/rapid_docs#132 (four sentences of
system/foundation.md). The plan's Operations facts line is the planner's.🤖 Generated with Claude Code