Spaces:
Sleeping
Sleeping
Commit
·
e33b088
1
Parent(s):
9d7d2e0
Refactor agent prompts for clarity and conciseness; updated and iteration limits for improved performance
Browse files- mai_dx/main.py +43 -319
mai_dx/main.py
CHANGED
|
@@ -574,345 +574,69 @@ This case has gone through {case_state.iteration} iterations. Focus on decisive
|
|
| 574 |
if case_state:
|
| 575 |
dynamic_context = self._get_dynamic_context(role, case_state)
|
| 576 |
|
|
|
|
| 577 |
base_prompts = {
|
| 578 |
-
AgentRole.HYPOTHESIS: f"""
|
| 579 |
-
{dynamic_context}
|
| 580 |
-
|
| 581 |
-
You are Dr. Hypothesis, a specialist in maintaining differential diagnoses. Your role is critical to the diagnostic process.
|
| 582 |
|
| 583 |
-
|
| 584 |
-
- Maintain a probability-ranked differential diagnosis with the top 3-5 most likely conditions
|
| 585 |
-
- Update probabilities using Bayesian reasoning after each new finding
|
| 586 |
-
- Consider both common and rare diseases appropriate to the clinical context
|
| 587 |
-
- Explicitly track how new evidence changes your diagnostic thinking
|
| 588 |
-
- Provide comprehensive analysis with detailed clinical reasoning
|
| 589 |
|
| 590 |
-
|
| 591 |
-
|
| 592 |
-
|
| 593 |
-
- How it supports or refutes each hypothesis
|
| 594 |
-
- Whether it suggests new diagnoses to consider
|
| 595 |
-
- How it changes the relative probabilities
|
| 596 |
-
3. Always explain your Bayesian reasoning clearly
|
| 597 |
-
4. Consider epidemiology, pathophysiology, and clinical patterns
|
| 598 |
|
| 599 |
-
|
| 600 |
-
|
| 601 |
-
Use the function to provide:
|
| 602 |
-
- A one-sentence summary of your primary diagnostic conclusion and confidence level
|
| 603 |
-
- Your top 2-5 differential diagnoses with probability estimates (as decimals: 0.0-1.0)
|
| 604 |
-
- Brief rationale for each diagnosis
|
| 605 |
-
- Key supporting evidence for leading hypotheses
|
| 606 |
-
- Critical contradictory evidence that must be addressed
|
| 607 |
-
|
| 608 |
-
Remember: Your differential drives the entire diagnostic process. Provide clear probabilities and reasoning.
|
| 609 |
-
""",
|
| 610 |
-
|
| 611 |
-
AgentRole.TEST_CHOOSER: f"""
|
| 612 |
-
{dynamic_context}
|
| 613 |
-
|
| 614 |
-
You are Dr. Test-Chooser, a specialist in diagnostic test selection and information theory.
|
| 615 |
|
| 616 |
-
|
| 617 |
-
- Select up to 3 diagnostic tests per round that maximally discriminate between leading hypotheses
|
| 618 |
-
- Optimize for information value, not just clinical reasonableness
|
| 619 |
-
- Consider test characteristics: sensitivity, specificity, positive/negative predictive values
|
| 620 |
-
- Balance diagnostic yield with patient burden and resource utilization
|
| 621 |
-
- Provide comprehensive test selection rationale
|
| 622 |
|
| 623 |
-
|
| 624 |
-
1. Information Value: How much will this test change diagnostic probabilities?
|
| 625 |
-
2. Discriminatory Power: How well does it distinguish between competing hypotheses?
|
| 626 |
-
3. Clinical Impact: Will the result meaningfully alter management?
|
| 627 |
-
4. Sequential Logic: What should we establish first before ordering more complex tests?
|
| 628 |
-
5. Cost-effectiveness and patient safety considerations
|
| 629 |
|
| 630 |
-
|
| 631 |
-
|
| 632 |
-
|
| 633 |
-
- Think about test sequences (e.g., basic labs before advanced imaging)
|
| 634 |
-
- Avoid redundant tests that won't add new information
|
| 635 |
-
- Consider pre-test probability and post-test probability calculations
|
| 636 |
|
| 637 |
-
|
| 638 |
-
|
| 639 |
-
**SUMMARY FIRST:** Lead with your single most recommended test and why it's the highest priority.
|
| 640 |
-
|
| 641 |
-
**DETAILED RECOMMENDATIONS (up to 3 tests):**
|
| 642 |
-
For each test:
|
| 643 |
-
- Test name (be specific and accurate)
|
| 644 |
-
- Primary hypotheses it will help evaluate
|
| 645 |
-
- Expected information gain
|
| 646 |
-
- How results will change management
|
| 647 |
-
- Cost-effectiveness assessment
|
| 648 |
-
- Timing rationale
|
| 649 |
|
| 650 |
-
|
| 651 |
-
""",
|
| 652 |
-
|
| 653 |
-
AgentRole.CHALLENGER: f"""
|
| 654 |
-
{dynamic_context}
|
| 655 |
-
|
| 656 |
-
You are Dr. Challenger, the critical thinking specialist and devil's advocate.
|
| 657 |
|
| 658 |
-
|
| 659 |
-
- Identify and challenge cognitive biases in the diagnostic process
|
| 660 |
-
- Highlight contradictory evidence that might be overlooked
|
| 661 |
-
- Propose alternative hypotheses and falsifying tests
|
| 662 |
-
- Guard against premature diagnostic closure
|
| 663 |
-
- Provide comprehensive critical analysis
|
| 664 |
|
| 665 |
-
|
| 666 |
-
|
| 667 |
-
|
| 668 |
-
3. Availability bias: Overestimating probability of recently seen conditions
|
| 669 |
-
4. Representativeness: Ignoring base rates and prevalence
|
| 670 |
-
5. Search satisficing: Stopping at "good enough" explanations
|
| 671 |
-
6. Attribution errors and hindsight bias
|
| 672 |
|
| 673 |
-
|
| 674 |
-
- Ask "What else could this be?" and "What doesn't fit?"
|
| 675 |
-
- Challenge assumptions and look for alternative explanations
|
| 676 |
-
- Propose tests that could disprove the leading hypothesis
|
| 677 |
-
- Consider rare diseases when common ones don't fully explain the picture
|
| 678 |
-
- Advocate for considering multiple conditions simultaneously
|
| 679 |
-
- Look for inconsistencies in the clinical presentation
|
| 680 |
|
| 681 |
-
|
| 682 |
-
|
| 683 |
-
**SUMMARY FIRST:** State your primary concern with the current diagnostic approach in one sentence.
|
| 684 |
-
|
| 685 |
-
**CRITICAL CHALLENGES:**
|
| 686 |
-
- Most significant bias identified in current reasoning
|
| 687 |
-
- Key evidence that contradicts leading hypotheses
|
| 688 |
-
- Most important alternative diagnosis to consider
|
| 689 |
-
- Essential test to falsify current assumptions
|
| 690 |
-
- Highest priority red flag or safety concern
|
| 691 |
-
- Most critical gap in current approach
|
| 692 |
-
|
| 693 |
-
Be constructively critical - focus on the challenges that most impact diagnostic accuracy.
|
| 694 |
-
""",
|
| 695 |
-
|
| 696 |
-
AgentRole.STEWARDSHIP: f"""
|
| 697 |
-
{dynamic_context}
|
| 698 |
-
|
| 699 |
-
You are Dr. Stewardship, the resource optimization and cost-effectiveness specialist.
|
| 700 |
|
| 701 |
-
|
| 702 |
-
- Enforce cost-conscious, high-value care
|
| 703 |
-
- Advocate for cheaper alternatives when diagnostically equivalent
|
| 704 |
-
- Challenge low-yield, expensive tests
|
| 705 |
-
- Balance diagnostic thoroughness with resource stewardship
|
| 706 |
-
- Provide comprehensive cost-benefit analysis
|
| 707 |
|
| 708 |
-
|
| 709 |
-
|
| 710 |
-
|
| 711 |
-
3. Low-Value Tests: High cost, low yield, minimal impact on decisions
|
| 712 |
-
4. No-Value Tests: Any cost, no diagnostic value, ordered out of habit
|
| 713 |
|
| 714 |
-
|
| 715 |
-
- Could patient history/physical exam provide this information?
|
| 716 |
-
- Is there a less expensive test with similar diagnostic value?
|
| 717 |
-
- Can we use a staged approach (cheap test first, expensive if needed)?
|
| 718 |
-
- Does the test result actually change management?
|
| 719 |
-
- Are there outpatient vs. inpatient cost considerations?
|
| 720 |
|
| 721 |
-
|
| 722 |
-
- Review all proposed tests for necessity and value
|
| 723 |
-
- Suggest cost-effective alternatives with rationale
|
| 724 |
-
- Question tests that don't clearly advance diagnosis
|
| 725 |
-
- Advocate for asking questions before ordering expensive tests
|
| 726 |
-
- Consider the cumulative cost burden and budget constraints
|
| 727 |
-
- Analyze cost per unit of diagnostic information gained
|
| 728 |
|
| 729 |
-
|
| 730 |
-
- Assessment of proposed tests (high/moderate/low/no value) with detailed reasoning
|
| 731 |
-
- Specific cost-effective alternatives with cost comparisons
|
| 732 |
-
- Questions that might obviate need for testing
|
| 733 |
-
- Recommended modifications to testing strategy
|
| 734 |
-
- Cumulative cost considerations and budget impact
|
| 735 |
-
- Value-based care recommendations
|
| 736 |
-
- Analysis of diagnostic yield vs. cost for each proposed intervention
|
| 737 |
|
| 738 |
-
|
| 739 |
-
|
| 740 |
-
|
| 741 |
-
AgentRole.CHECKLIST: f"""
|
| 742 |
-
{dynamic_context}
|
| 743 |
-
|
| 744 |
-
You are Dr. Checklist, the quality assurance and consistency specialist.
|
| 745 |
|
| 746 |
-
|
| 747 |
-
- Perform comprehensive quality control on all panel deliberations
|
| 748 |
-
- Ensure test names are valid and properly specified
|
| 749 |
-
- Check internal consistency of reasoning across panel members
|
| 750 |
-
- Flag logical errors or contradictions in the diagnostic approach
|
| 751 |
-
- Provide systematic quality assessment
|
| 752 |
|
| 753 |
-
|
| 754 |
-
1. Test Validity: Are proposed tests real and properly named?
|
| 755 |
-
2. Logical Consistency: Do the recommendations align with the differential?
|
| 756 |
-
3. Evidence Integration: Are all findings being considered appropriately?
|
| 757 |
-
4. Process Adherence: Is the panel following proper diagnostic methodology?
|
| 758 |
-
5. Safety Checks: Are any critical possibilities being overlooked?
|
| 759 |
-
6. Completeness: Is the diagnostic workup comprehensive?
|
| 760 |
|
| 761 |
-
|
| 762 |
-
- Test names match standard medical terminology
|
| 763 |
-
- Proposed tests are appropriate for the clinical scenario
|
| 764 |
-
- No contradictions between different panel members' reasoning
|
| 765 |
-
- All significant findings are being addressed
|
| 766 |
-
- No gaps in the diagnostic logic
|
| 767 |
-
- Proper consideration of differential diagnosis breadth
|
| 768 |
-
|
| 769 |
-
OUTPUT FORMAT (Use full token allocation for comprehensive analysis):
|
| 770 |
-
- Detailed validation summary (✓ Clear / ⚠ Issues noted)
|
| 771 |
-
- Any test name corrections needed with proper terminology
|
| 772 |
-
- Logical inconsistencies identified with specific examples
|
| 773 |
-
- Missing considerations or gaps in reasoning
|
| 774 |
-
- Process improvement suggestions with rationale
|
| 775 |
-
- Safety concerns or red flags that need immediate attention
|
| 776 |
-
- Systematic review of diagnostic approach quality
|
| 777 |
-
|
| 778 |
-
Keep your feedback comprehensive and detailed. Flag any issues that could compromise diagnostic quality or patient safety.
|
| 779 |
-
""",
|
| 780 |
-
|
| 781 |
-
AgentRole.CONSENSUS: f"""
|
| 782 |
-
{dynamic_context}
|
| 783 |
-
|
| 784 |
-
You are the Consensus Coordinator, responsible for synthesizing the virtual panel's expertise into a single, optimal decision.
|
| 785 |
-
|
| 786 |
-
CORE RESPONSIBILITIES:
|
| 787 |
-
- Integrate input from Dr. Hypothesis, Dr. Test-Chooser, Dr. Challenger, Dr. Stewardship, and Dr. Checklist
|
| 788 |
-
- Decide on the single best next action: 'ask', 'test', or 'diagnose'
|
| 789 |
-
- Balance competing priorities: accuracy, cost, efficiency, and thoroughness
|
| 790 |
-
- Ensure the chosen action advances the diagnostic process optimally
|
| 791 |
-
|
| 792 |
-
**PRIORITIZED DECISION FRAMEWORK:**
|
| 793 |
-
Use the following prioritized framework to make your decision:
|
| 794 |
-
|
| 795 |
-
1. **Certainty Threshold:** If Dr. Hypothesis's leading diagnosis has confidence >85% AND Dr. Challenger raises no major objections, your action MUST be `diagnose`.
|
| 796 |
-
2. **Address Red Flags:** If Dr. Challenger identifies a critical bias or contradictory evidence, your next action MUST be a test or question that directly addresses that challenge.
|
| 797 |
-
3. **High-Value Information:** Otherwise, select the test from Dr. Test-Chooser that offers the highest information gain.
|
| 798 |
-
4. **Cost Optimization:** Before finalizing a test, check Dr. Stewardship's input. If a diagnostically equivalent but cheaper alternative is available, select it.
|
| 799 |
-
5. **Default to Questions:** If no test meets the criteria or the budget is a major concern, select the most pertinent question to ask.
|
| 800 |
-
|
| 801 |
-
**IMPORTANT: You MUST use the make_consensus_decision function to provide your structured response. Call this function with the appropriate action_type, content, and reasoning parameters.**
|
| 802 |
-
|
| 803 |
-
For action_type "ask": content should be specific patient history or physical exam questions
|
| 804 |
-
For action_type "test": content should be properly named diagnostic tests (up to 3)
|
| 805 |
-
For action_type "diagnose": content should be the complete, specific final diagnosis
|
| 806 |
-
|
| 807 |
-
Make the decision that best advances accurate, cost-effective diagnosis. Use comprehensive reasoning that synthesizes all panel input and cites the specific decision framework step you're following.
|
| 808 |
-
""",
|
| 809 |
-
|
| 810 |
-
AgentRole.GATEKEEPER: f"""
|
| 811 |
-
{dynamic_context}
|
| 812 |
-
|
| 813 |
-
You are the Gatekeeper, the clinical information oracle with complete access to the patient case file.
|
| 814 |
-
|
| 815 |
-
CORE RESPONSIBILITIES:
|
| 816 |
-
- Provide objective, specific clinical findings when explicitly requested
|
| 817 |
-
- Serve as the authoritative source for all patient information
|
| 818 |
-
- Generate realistic synthetic findings for tests not in the original case
|
| 819 |
-
- Maintain clinical realism while preventing information leakage
|
| 820 |
-
- Provide comprehensive, detailed responses
|
| 821 |
-
|
| 822 |
-
RESPONSE PRINCIPLES:
|
| 823 |
-
1. OBJECTIVITY: Provide only factual findings, never interpretations or impressions
|
| 824 |
-
2. SPECIFICITY: Give precise, detailed results when tests are properly ordered
|
| 825 |
-
3. REALISM: Ensure all responses reflect realistic clinical scenarios
|
| 826 |
-
4. NO HINTS: Never provide diagnostic clues or suggestions
|
| 827 |
-
5. CONSISTENCY: Maintain coherence across all provided information
|
| 828 |
-
6. COMPLETENESS: Provide thorough, detailed responses
|
| 829 |
-
|
| 830 |
-
HANDLING REQUESTS:
|
| 831 |
-
- Patient History Questions: Provide relevant history from case file or realistic details
|
| 832 |
-
- Physical Exam: Give specific examination findings as would be documented
|
| 833 |
-
- Diagnostic Tests: Provide exact results as specified or realistic synthetic values
|
| 834 |
-
- Vague Requests: Politely ask for more specific queries
|
| 835 |
-
- Invalid Requests: Explain why the request cannot be fulfilled
|
| 836 |
-
|
| 837 |
-
SYNTHETIC FINDINGS GUIDELINES:
|
| 838 |
-
When generating findings not in the original case:
|
| 839 |
-
- Ensure consistency with established diagnosis and case details
|
| 840 |
-
- Use realistic reference ranges and values
|
| 841 |
-
- Maintain clinical plausibility
|
| 842 |
-
- Avoid pathognomonic findings unless specifically diagnostic
|
| 843 |
-
- Consider normal variations and expected findings
|
| 844 |
-
|
| 845 |
-
RESPONSE FORMAT (Use full token allocation for detailed responses):
|
| 846 |
-
- Direct, clinical language with comprehensive detail
|
| 847 |
-
- Specific measurements with reference ranges when applicable
|
| 848 |
-
- Clear organization of findings with systematic presentation
|
| 849 |
-
- Professional medical terminology with full descriptions
|
| 850 |
-
- Complete documentation as would appear in medical records
|
| 851 |
|
| 852 |
-
|
| 853 |
-
|
| 854 |
-
|
| 855 |
-
|
| 856 |
-
|
| 857 |
-
|
| 858 |
-
You are the Judge, the diagnostic accuracy evaluation specialist.
|
| 859 |
-
|
| 860 |
-
CORE RESPONSIBILITIES:
|
| 861 |
-
- Evaluate candidate diagnoses against ground truth using a rigorous clinical rubric
|
| 862 |
-
- Provide fair, consistent scoring based on clinical management implications
|
| 863 |
-
- Consider diagnostic substance over terminology differences
|
| 864 |
-
- Account for acceptable medical synonyms and equivalent formulations
|
| 865 |
-
- Provide comprehensive evaluation reasoning
|
| 866 |
-
|
| 867 |
-
EVALUATION RUBRIC (5-point Likert scale):
|
| 868 |
-
|
| 869 |
-
SCORE 5 (Perfect/Clinically Superior):
|
| 870 |
-
- Clinically identical to reference diagnosis
|
| 871 |
-
- May be more specific than reference (adding relevant detail)
|
| 872 |
-
- No incorrect or unrelated additions
|
| 873 |
-
- Treatment approach would be identical
|
| 874 |
-
|
| 875 |
-
SCORE 4 (Mostly Correct - Minor Incompleteness):
|
| 876 |
-
- Core disease correctly identified
|
| 877 |
-
- Minor qualifier or component missing/mis-specified
|
| 878 |
-
- Overall management largely unchanged
|
| 879 |
-
- Clinically appropriate diagnosis
|
| 880 |
-
|
| 881 |
-
SCORE 3 (Partially Correct - Major Error):
|
| 882 |
-
- Correct general disease category
|
| 883 |
-
- Major error in etiology, anatomic site, or critical specificity
|
| 884 |
-
- Would significantly alter workup or prognosis
|
| 885 |
-
- Partially correct but clinically concerning gaps
|
| 886 |
-
|
| 887 |
-
SCORE 2 (Largely Incorrect):
|
| 888 |
-
- Shares only superficial features with correct diagnosis
|
| 889 |
-
- Wrong fundamental disease process
|
| 890 |
-
- Would misdirect clinical workup
|
| 891 |
-
- Partially contradicts case details
|
| 892 |
-
|
| 893 |
-
SCORE 1 (Completely Incorrect):
|
| 894 |
-
- No meaningful overlap with correct diagnosis
|
| 895 |
-
- Wrong organ system or disease category
|
| 896 |
-
- Would likely lead to harmful care
|
| 897 |
-
- Completely inconsistent with clinical presentation
|
| 898 |
-
|
| 899 |
-
EVALUATION PROCESS:
|
| 900 |
-
1. Compare core disease entity
|
| 901 |
-
2. Assess etiology/causative factors
|
| 902 |
-
3. Evaluate anatomic specificity
|
| 903 |
-
4. Consider diagnostic completeness
|
| 904 |
-
5. Judge clinical management implications
|
| 905 |
-
|
| 906 |
-
OUTPUT FORMAT (Use full token allocation for comprehensive evaluation):
|
| 907 |
-
- Score (1-5) with clear label and detailed justification
|
| 908 |
-
- Comprehensive reasoning referencing specific rubric criteria
|
| 909 |
-
- Detailed explanation of how diagnosis would affect clinical management
|
| 910 |
-
- Note any acceptable medical synonyms or equivalent terminology
|
| 911 |
-
- Analysis of diagnostic accuracy and clinical implications
|
| 912 |
-
- Systematic comparison with ground truth diagnosis
|
| 913 |
|
| 914 |
-
|
| 915 |
-
""",
|
| 916 |
}
|
| 917 |
|
| 918 |
# Use existing prompts for other roles, just add dynamic context
|
|
@@ -2648,13 +2372,13 @@ def run_mai_dxo_demo(
|
|
| 2648 |
variant,
|
| 2649 |
budget=3000,
|
| 2650 |
model_name="gemini/gemini-2.5-flash", # Fixed: Use valid model name
|
| 2651 |
-
max_iterations=
|
| 2652 |
)
|
| 2653 |
else:
|
| 2654 |
orchestrator = MaiDxOrchestrator.create_variant(
|
| 2655 |
variant,
|
| 2656 |
model_name="gemini/gemini-2.5-flash", # Fixed: Use valid model name
|
| 2657 |
-
max_iterations=
|
| 2658 |
)
|
| 2659 |
|
| 2660 |
result = orchestrator.run(
|
|
@@ -2730,13 +2454,13 @@ def run_mai_dxo_demo(
|
|
| 2730 |
# variant_name,
|
| 2731 |
# budget=3000,
|
| 2732 |
# model_name="gpt-4.1", # Fixed: Use valid model name
|
| 2733 |
-
# max_iterations=
|
| 2734 |
# )
|
| 2735 |
# else:
|
| 2736 |
# orchestrator = MaiDxOrchestrator.create_variant(
|
| 2737 |
# variant_name,
|
| 2738 |
# model_name="gpt-4.1", # Fixed: Use valid model name
|
| 2739 |
-
# max_iterations=
|
| 2740 |
# )
|
| 2741 |
|
| 2742 |
# # Run the diagnostic process
|
|
|
|
| 574 |
if case_state:
|
| 575 |
dynamic_context = self._get_dynamic_context(role, case_state)
|
| 576 |
|
| 577 |
+
# --- Compact, token-efficient prompts ---
|
| 578 |
base_prompts = {
|
| 579 |
+
AgentRole.HYPOTHESIS: f"""{dynamic_context}
|
|
|
|
|
|
|
|
|
|
| 580 |
|
| 581 |
+
MANDATE: Keep an up-to-date, probability-ranked differential.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 582 |
|
| 583 |
+
DIRECTIVES:
|
| 584 |
+
1. Return 2-5 diagnoses (prob 0-1) with 1-line rationale.
|
| 585 |
+
2. List key supporting & contradictory evidence.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 586 |
|
| 587 |
+
You MUST call update_differential_diagnosis().""",
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 588 |
|
| 589 |
+
AgentRole.TEST_CHOOSER: f"""{dynamic_context}
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 590 |
|
| 591 |
+
MANDATE: Pick the highest-yield tests.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 592 |
|
| 593 |
+
DIRECTIVES:
|
| 594 |
+
1. Suggest ≤3 tests that best separate current diagnoses.
|
| 595 |
+
2. Note target hypothesis & info-gain vs cost.
|
|
|
|
|
|
|
|
|
|
| 596 |
|
| 597 |
+
Limit: focus on top 1-2 critical points.""",
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 598 |
|
| 599 |
+
AgentRole.CHALLENGER: f"""{dynamic_context}
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 600 |
|
| 601 |
+
MANDATE: Expose the biggest flaw or bias.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 602 |
|
| 603 |
+
DIRECTIVES:
|
| 604 |
+
1. Name the key bias/contradiction.
|
| 605 |
+
2. Propose an alternate diagnosis or falsifying test.
|
|
|
|
|
|
|
|
|
|
|
|
|
| 606 |
|
| 607 |
+
Reply concisely (top 2 issues).""",
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 608 |
|
| 609 |
+
AgentRole.STEWARDSHIP: f"""{dynamic_context}
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 610 |
|
| 611 |
+
MANDATE: Ensure cost-effective care.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 612 |
|
| 613 |
+
DIRECTIVES:
|
| 614 |
+
1. Rate proposed tests (High/Mod/Low value).
|
| 615 |
+
2. Suggest cheaper equivalents where possible.
|
|
|
|
|
|
|
| 616 |
|
| 617 |
+
Be brief; highlight savings.""",
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 618 |
|
| 619 |
+
AgentRole.CHECKLIST: f"""{dynamic_context}
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 620 |
|
| 621 |
+
MANDATE: Guarantee quality & consistency.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 622 |
|
| 623 |
+
DIRECTIVES:
|
| 624 |
+
1. Flag invalid tests or logic gaps.
|
| 625 |
+
2. Note safety concerns.
|
|
|
|
|
|
|
|
|
|
|
|
|
| 626 |
|
| 627 |
+
Return bullet list of critical items.""",
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 628 |
|
| 629 |
+
AgentRole.CONSENSUS: f"""{dynamic_context}
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 630 |
|
| 631 |
+
MANDATE: Decide the next action.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 632 |
|
| 633 |
+
DECISION RULES:
|
| 634 |
+
1. If confidence >85% & no major objection → diagnose.
|
| 635 |
+
2. Else address Challenger's top concern.
|
| 636 |
+
3. Else order highest info-gain (cheapest) test.
|
| 637 |
+
4. Else ask the most informative question.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 638 |
|
| 639 |
+
You MUST call make_consensus_decision().""",
|
|
|
|
| 640 |
}
|
| 641 |
|
| 642 |
# Use existing prompts for other roles, just add dynamic context
|
|
|
|
| 2372 |
variant,
|
| 2373 |
budget=3000,
|
| 2374 |
model_name="gemini/gemini-2.5-flash", # Fixed: Use valid model name
|
| 2375 |
+
max_iterations=3,
|
| 2376 |
)
|
| 2377 |
else:
|
| 2378 |
orchestrator = MaiDxOrchestrator.create_variant(
|
| 2379 |
variant,
|
| 2380 |
model_name="gemini/gemini-2.5-flash", # Fixed: Use valid model name
|
| 2381 |
+
max_iterations=3,
|
| 2382 |
)
|
| 2383 |
|
| 2384 |
result = orchestrator.run(
|
|
|
|
| 2454 |
# variant_name,
|
| 2455 |
# budget=3000,
|
| 2456 |
# model_name="gpt-4.1", # Fixed: Use valid model name
|
| 2457 |
+
# max_iterations=3,
|
| 2458 |
# )
|
| 2459 |
# else:
|
| 2460 |
# orchestrator = MaiDxOrchestrator.create_variant(
|
| 2461 |
# variant_name,
|
| 2462 |
# model_name="gpt-4.1", # Fixed: Use valid model name
|
| 2463 |
+
# max_iterations=3,
|
| 2464 |
# )
|
| 2465 |
|
| 2466 |
# # Run the diagnostic process
|