Repository navigation
docs: prepare HST MGE pilot collection choices - #59
Merged
Merged
Conversation
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.
Summary
The shipped HST/MGE runner leaves production collection choices unresolved. Add a Pulse decision document with verified candidate FITS identities and plan-only resource bounds, and separate them from proposed hardware, software, input, load and correctness choices.
Link the document from the existing pilot task and update the campaign/next step. Keep the independently owned project correctness audit #417 with its current session. No new campaign, compute, witness execution or scientific decision.
Closes #58.
API Changes
None. Pulse prose, campaign next steps and generated board only. Existing last_checkin and measurement snapshots/timestamps are unchanged.
Scripts Changed
None.
Validation checklist (--auto run)
The 32-process / 16 CPU-hour overall resource ceiling remains a proposal; the shipped runner covers 31 workers / 15.5 hours and no independent correctness process. Data origin, production suitability, selected hardware/stack, full resolved settings, background-load method and correctness tolerances remain unresolved. No improvement/regression claim is made.
Tier: judge — human /prm. Generated by the PyAutoLabs agent workflow.