Non-clinical pathway pressure and protected capacity action

Elite LLM Handoff

Explain the reduce_pathway_pressure recommendation using the governed Fortress output and caveats.

governed_handoff:
  - Goal: reduce_pathway_pressure
  - Primary path: pathway_capacity_protected, score 0.7118, high confidence
  - Supporting signals: admin_validation_blocker, capacity_huddle, clinic_capacity_gap, referral_backlog, transport_delay
  - Runtime relationship sets returned: 8
  - Domain journeys: 120; events: 600; relationship sets: 120

Outcome Prompt JSON

{
  "schema": "kynticai.elite.outcome-prompts.v1",
  "caseStudyId": "nhs-healthcare-operations-pathway-pressure",
  "domain": "NHS / healthcare operations",
  "stakeholder": "ICB operations lead",
  "runtimeQuery": "A non-clinical pathway has referral backlog pressure, clinic capacity gaps, patient transport delays, and admin validation blockers. What operations action should the pathway team take next?",
  "promptContract": "You are Elite, the KynticAI recommendation-writing layer.\n\nYou receive governed Fortress output, not raw customer data. Use only the supplied relationship-set facts, scores, confidence labels, alternatives, caveats, and outcome goal.\n\nWrite a decisive operational recommendation for the accountable team. Your output must include:\n1. Recommended action.\n2. Why this action is supported by the comparable relationship sets.\n3. What to do now.\n4. When to choose one of the alternative actions.\n5. What outcome to capture so the system improves.\n\nRules:\n- Do not invent facts outside the governed handoff.\n- Do not promise revenue, retention, clinical, legal, financial, safety, or compliance outcomes.\n- Do not apologise for using synthetic demo data.\n- Be commercially useful, specific, and direct.\n- Keep human review and claim boundaries visible where the domain requires them.",
  "governedFacts": [
    "Goal: reduce_pathway_pressure",
    "Primary path: pathway_capacity_protected, score 0.7118, high confidence",
    "Supporting signals: admin_validation_blocker, capacity_huddle, clinic_capacity_gap, referral_backlog, transport_delay",
    "Runtime relationship sets returned: 8",
    "Domain journeys: 120; events: 600; relationship sets: 120"
  ],
  "outcomePrompts": [
    {
      "rank": 1,
      "outcome": "pathway_capacity_protected",
      "action": "Open a non-clinical capacity huddle, validate the backlog list, and move suitable appointments into the protected slot pool for operational review.",
      "confidence": "High",
      "score": "0.7118",
      "prompt": "You are Elite, the KynticAI recommendation-writing layer.\n\nUse only the governed Fortress handoff below. Do not invent facts.\n\nCase study: Non-clinical pathway pressure and protected capacity action\nDomain: NHS / healthcare operations\nStakeholder: ICB operations lead\nRuntime query: A non-clinical pathway has referral backlog pressure, clinic capacity gaps, patient transport delays, and admin validation blockers. What operations action should the pathway team take next?\n\nGoverned facts:\n- Goal: reduce_pathway_pressure\n- Primary path: pathway_capacity_protected, score 0.7118, high confidence\n- Supporting signals: admin_validation_blocker, capacity_huddle, clinic_capacity_gap, referral_backlog, transport_delay\n- Runtime relationship sets returned: 8\n- Domain journeys: 120; events: 600; relationship sets: 120\n\nCandidate outcome to explain:\n- Rank: 1\n- Outcome: pathway_capacity_protected\n- Action: Open a non-clinical capacity huddle, validate the backlog list, and move suitable appointments into the protected slot pool for operational review.\n- Confidence: High\n- Score: 0.7118\n- Evidence summary: Comparable relationship sets ended in pathway_capacity_protected and share signals such as admin_validation_blocker, capacity_huddle, clinic_capacity_gap, referral_backlog, transport_delay.\n- Supporting relationship sets: set-f7952eb1243b, set-18442a874900, set-21fc983fc52e, set-0677db0d3073, set-af13652b74f6\n\nWrite the operational recommendation for this outcome.\nInclude why the comparable relationship sets support it, what the team should do now, when this outcome should be chosen over the other ranked options, and what reviewed outcome must be captured next.",
      "expectedTextOutput": "Recommended action: Open a non-clinical capacity huddle, validate the backlog list, and move suitable appointments into the protected slot pool for operational review.\n\nWhy this is supported: Fortress ranked pathway_capacity_protected first with score 0.7118 and high confidence. Comparable relationship sets ended in pathway_capacity_protected and share signals such as admin_validation_blocker, capacity_huddle, clinic_capacity_gap, referral_backlog, transport_delay. The supporting relationship sets are set-f7952eb1243b, set-18442a874900, set-21fc983fc52e, set-0677db0d3073, set-af13652b74f6.\n\nWhat to do now: brief the icb operations lead with the runtime query, the shared signals (admin_validation_blocker, capacity_huddle, clinic_capacity_gap, referral_backlog, transport_delay), and the exact action. Keep the action specific to this scenario rather than turning it into a generic campaign or workflow rule.\n\nWhen to choose an alternative: switch if the live evidence is closer to admin_blocker_resolved (Prioritise admin validation and contact-detail correction before requesting more pathway capacity.); patient_comms_sent (Send the approved non-clinical appointment communication and rebooking route before escalating capacity.).\n\nOutcome to capture: record the action taken, the reviewed outcome, and any contradictory signal so the next Scout/Fortress comparison has stronger evidence."
    },
    {
      "rank": 2,
      "outcome": "admin_blocker_resolved",
      "action": "Prioritise admin validation and contact-detail correction before requesting more pathway capacity.",
      "confidence": "Medium",
      "score": "0.3698",
      "prompt": "You are Elite, the KynticAI recommendation-writing layer.\n\nUse only the governed Fortress handoff below. Do not invent facts.\n\nCase study: Non-clinical pathway pressure and protected capacity action\nDomain: NHS / healthcare operations\nStakeholder: ICB operations lead\nRuntime query: A non-clinical pathway has referral backlog pressure, clinic capacity gaps, patient transport delays, and admin validation blockers. What operations action should the pathway team take next?\n\nGoverned facts:\n- Goal: reduce_pathway_pressure\n- Primary path: pathway_capacity_protected, score 0.7118, high confidence\n- Supporting signals: admin_validation_blocker, capacity_huddle, clinic_capacity_gap, referral_backlog, transport_delay\n- Runtime relationship sets returned: 8\n- Domain journeys: 120; events: 600; relationship sets: 120\n\nCandidate outcome to explain:\n- Rank: 2\n- Outcome: admin_blocker_resolved\n- Action: Prioritise admin validation and contact-detail correction before requesting more pathway capacity.\n- Confidence: Medium\n- Score: 0.3698\n- Evidence summary: Comparable relationship sets ended in admin_blocker_resolved and share signals such as blocker_resolved, booking_admin, contact_detail_gap, validation_queue.\n- Supporting relationship sets: set-ebeecd48a1dc\n\nWrite the operational recommendation for this outcome.\nInclude why the comparable relationship sets support it, what the team should do now, when this outcome should be chosen over the other ranked options, and what reviewed outcome must be captured next.",
      "expectedTextOutput": "Alternative action: Prioritise admin validation and contact-detail correction before requesting more pathway capacity.\n\nWhy this route exists: Fortress returned admin_blocker_resolved at rank 2 with score 0.3698 and medium confidence. Comparable relationship sets ended in admin_blocker_resolved and share signals such as blocker_resolved, booking_admin, contact_detail_gap, validation_queue. The supporting relationship sets are set-ebeecd48a1dc.\n\nWhen to use it: choose this instead of the primary route when the live evidence matches blocker_resolved, booking_admin, contact_detail_gap, validation_queue more closely than the current top-ranked outcome.\n\nWhat to do now: make the action explicit for the icb operations lead, preserve the caveat for this domain, and avoid inventing extra facts beyond the governed handoff.\n\nOutcome to capture: record whether admin_blocker_resolved happened and feed that reviewed result back into the relationship-set evidence."
    },
    {
      "rank": 3,
      "outcome": "patient_comms_sent",
      "action": "Send the approved non-clinical appointment communication and rebooking route before escalating capacity.",
      "confidence": "Medium",
      "score": "0.3106",
      "prompt": "You are Elite, the KynticAI recommendation-writing layer.\n\nUse only the governed Fortress handoff below. Do not invent facts.\n\nCase study: Non-clinical pathway pressure and protected capacity action\nDomain: NHS / healthcare operations\nStakeholder: ICB operations lead\nRuntime query: A non-clinical pathway has referral backlog pressure, clinic capacity gaps, patient transport delays, and admin validation blockers. What operations action should the pathway team take next?\n\nGoverned facts:\n- Goal: reduce_pathway_pressure\n- Primary path: pathway_capacity_protected, score 0.7118, high confidence\n- Supporting signals: admin_validation_blocker, capacity_huddle, clinic_capacity_gap, referral_backlog, transport_delay\n- Runtime relationship sets returned: 8\n- Domain journeys: 120; events: 600; relationship sets: 120\n\nCandidate outcome to explain:\n- Rank: 3\n- Outcome: patient_comms_sent\n- Action: Send the approved non-clinical appointment communication and rebooking route before escalating capacity.\n- Confidence: Medium\n- Score: 0.3106\n- Evidence summary: Comparable relationship sets ended in patient_comms_sent and share signals such as appointment_reminder_gap, approved_comms, attendance_protected, rebooking_route.\n- Supporting relationship sets: set-ea253d51fe99\n\nWrite the operational recommendation for this outcome.\nInclude why the comparable relationship sets support it, what the team should do now, when this outcome should be chosen over the other ranked options, and what reviewed outcome must be captured next.",
      "expectedTextOutput": "Alternative action: Send the approved non-clinical appointment communication and rebooking route before escalating capacity.\n\nWhy this route exists: Fortress returned patient_comms_sent at rank 3 with score 0.3106 and medium confidence. Comparable relationship sets ended in patient_comms_sent and share signals such as appointment_reminder_gap, approved_comms, attendance_protected, rebooking_route. The supporting relationship sets are set-ea253d51fe99.\n\nWhen to use it: choose this instead of the primary route when the live evidence matches appointment_reminder_gap, approved_comms, attendance_protected, rebooking_route more closely than the current top-ranked outcome.\n\nWhat to do now: make the action explicit for the icb operations lead, preserve the caveat for this domain, and avoid inventing extra facts beyond the governed handoff.\n\nOutcome to capture: record whether patient_comms_sent happened and feed that reviewed result back into the relationship-set evidence."
    }
  ]
}