RGDS v1.3.0 — IND delivery alignment (webinar-grounded decision governance) - #3
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
This PR aligns RGDS with how IND programs actually operate under regulatory, timing,
and dependency constraints, based on real-world IND execution patterns discussed
in the Syner-G IND submission webinar.
The goal is not to add autonomy or automation, but to make critical delivery and
regulatory decisions explicit, auditable, and phase-appropriate.
What changed
Decision model enhancements
program_context.domainto explicitly supportind_submission.Governance and documentation
PMs, medical writing, regulatory strategy, CMC, ops, quality, and
the Principal AI Business Analyst role.
(dependencies, late data, escalation, and fallback planning).
Usability
What this does NOT do
RGDS remains explicitly human-governed, evidence-linked, and audit-ready.
Why this matters
These changes reduce late-stage decision surprise by forcing
risk acceptance, scope changes, and drafting-at-risk decisions to be made
explicitly and early—without compromising regulatory trust.
Validation
All existing example decision logs pass schema validation.