Enforce baseline parity and add controlled tie-group variability to system prompt#882
Open
GVCUTV wants to merge 1 commit intoissue665-iterative-correctionfrom
Open
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.
Motivation
src/main/resources/ai/system_prompt_template.txt.Description
STANDARD-BASELINE PARITY (NORMATIVE)which mandates fillingON_DUTYfirst thenON_CALL, enforces per-shift uniqueness, forbids cross-layer duplication, and requires exact role fidelity for emitted rows.(shift_id, required_role, assignment_status)keys when minima are unmet.CONTROLLED TIE VARIABILITY (NORMATIVE)that retains the existing ordered tie-resolution steps but replaces always-ascendingdoctor_idas the deterministic final step with a run-scoped seeded rotation/shuffle for exact tie-groups while forbidding any violation of hard constraints or layer-order rules.PARTIAL_SUCCESSwhen reconciliation mismatches remain), and reinforced thatSUCCESSis forbidden if layer minima are not satisfied.Testing
Codex Task