deliverables

deliverables — Phase 6-7 Orchestration

Version: 2.0.0 Phase: 6-7 — Solution & Deliverables MCP Tools: jira_update_issue, jira_add_comment (for JIRA updates); Write tool for files Gate: verification rate ≥ 90% (see gate.md) Reasoning Libraries: curator.md (final claim sweep), gate.md

---

Status Output (MANDATORY — print before any tool call)

At the very start of execution, output this exact block:

[ Phase 7 — Deliverables ]
Tools: Write tool — file generation

Then before each tool call, output a one-liner: → {tool-name} {key parameter}

---

Purpose

Execute Phase 6-7 deliverable generation directly. CAPPY writes all deliverables from evidence — no generate_deliverables meta-orchestrator. This gives CAPPY full control over content, citations, and formatting rather than delegating to a template renderer.

Use templates from {plugin_root}/templates/deliverables/ as structural guides, not as fill-in-the-blank forms. Every factual sentence must trace to evidence.

---

Procedure

Step 1 — Final claim verification sweep (per curator.md)

Read {case_dir}/inv_context.json. Count claims:

• VERIFIED: {count}
• UNVERIFIED: {count}
• REJECTED: {count}

verification_rate = VERIFIED / (VERIFIED + UNVERIFIED)

IF verification_rate < 90%: resolve each UNVERIFIED claim NOW:

<claim id="{id}">
  STATEMENT: "{claim text}"
  <verify>
    Q: Can I find direct evidence for this in the case directory?
    A: {Read result or grep result with file:line}
  </verify>
  STATUS: VERIFIED | REJECTED
</claim>

Recalculate after sweep. If still < 90%, mark remaining unverified claims explicitly in deliverables — do NOT silently drop them.

Step 2 — Check Phase 7 QA gate (per gate.md) before writing

IF verification_rate < 90%: do not proceed to deliverable writing. Return gate failure with recovery options.

IF verification_rate ≥ 90%: proceed.

Step 3 — Write customer response

File: {case_dir}/deliverables/customer_response.txt

Requirements:

• Plain text (no markdown — this goes into Salesforce)
• Every factual claim includes an inline evidence reference: (ref: {file:line})
• Citations section at bottom with [N] format
• Include: root cause summary, customer impact, resolution/workaround, next steps
• Tone: technical, factual, no speculation

Reference template structure: {plugin_root}/templates/deliverables/GUIDELINES.md

Step 4 — Write JIRA draft

File: {case_dir}/deliverables/JIRA_DRAFT.txt

Two sections:

1. Plaintext — human-readable summary for JIRA description
2. Wiki markup — formatted version for JIRA rendering

Required sections in JIRA draft:

• Root Cause (1-2 sentences, cited)
• Evidence Summary (key findings with file:line)
• Timeline of Events (from correlate_timeline output)
• Resolution / Workaround
• Internal References (evidence artifacts used)
• Citations

Step 5 — Update JIRA ticket

JIRA updates are done by Main Claude after deliverables are written. Present the JIRA draft and ask Main Claude to post via the JIRA MCP gateway:

// Main Claude posts after reviewing the draft:
mcp__mcp-gateway__mcp_jira__create_note({
  issue_key: "{jira_ticket}",
  body: "{jira_plaintext_summary}"
})

Only add a comment — do not modify the JIRA description unless explicitly requested.

Step 6 — Update inv_context.json

Write final investigation state:

• deliverables section: list of generated files with paths
• audit_trail: final entry with timestamp, phase, outcome
• feedback.resolution_confirmed: false (customer hasn't confirmed yet)

---

Deliverable Quality Checklist

Before returning, verify each deliverable:

• Every factual claim has a citation reference
• No REJECTED claims appear in any deliverable
• No speculation or inference presented as fact
• Customer name, product, version are correct throughout
• Resolution/workaround is actionable (not "contact support")
• JIRA draft has both plaintext and wiki markup sections
• Internal References section is populated in JIRA draft

---

Return Format

{
  "phase": 7,
  "gate_status": "PASS | FAIL",
  "verification_rate": 0.0,
  "threshold": 0.90,
  "claims_verified": 0,
  "claims_unverified": 0,
  "claims_rejected": 0,
  "deliverables_generated": [
    { "type": "customer_response", "file": "deliverables/customer_response.txt", "citations_count": 0 },
    { "type": "jira_draft", "file": "deliverables/JIRA_DRAFT.txt", "citations_count": 0 }
  ],
  "jira_updated": true,
  "recommendation": "Deliverables ready for Kevin review | Gate blocked: {reason}",
  "recovery_options": []
}

Return this JSON to Main Claude.