Output Assembly Prompts

The assembly prompt synthesizes multiple sub-outputs into a coherent whole. It is the final step in a decomposed pipeline — the step that produces the output the end user receives. Assembly is its own prompt engineering challenge: the model must integrate multiple distinct outputs, resolve any inconsistencies between them, and produce a unified, coherent result.

# Assembly Prompt: Contract Risk Report

## Role
You are a contract risk report author. Synthesize the analysis outputs below
into a single, coherent executive report for a senior business stakeholder.
The stakeholder will use this report to decide whether to proceed with the contract.

## Sub-Task Outputs [all verified complete before assembly]

From S2 (Clause Extraction):
[insert S2 output here]

From S3 (Risk Scoring):
[insert S3 output here]

From S5 (Policy Cross-Reference):
[insert S5 output here]

## Assembly Instructions
Produce a complete contract risk report with these sections:
1. EXECUTIVE SUMMARY (3-4 sentences): overall risk level, recommendation, and key rationale
2. KEY FINDINGS (3-5 bullets): the most important facts from the analysis
3. HIGH-RISK CLAUSES: for each high-risk clause identified in S2, include: clause ID,
   clause text (verbatim), risk explanation (1-2 sentences), recommended action
4. POLICY CONFLICTS: if S5 identified any policy conflicts, list them here. If none, omit section.
5. RECOMMENDATION: one of "Proceed as-is | Proceed with redlines | Require legal review | Do not proceed"
   followed by 2-3 sentence justification

## Consistency Requirements
- Risk level in Executive Summary must match risk_tier from S3 output
- All clause IDs referenced must exist in S2 output
- If S3 and S5 outputs conflict on a risk assessment, note the conflict explicitly
  rather than silently resolving it

## Output Format: Markdown
Use the section headers above as H2 (##) headers.
Plain prose for narrative sections. Bulleted lists for Key Findings and High-Risk Clauses.

1. Consistency Requirements Are Mandatory When sub-outputs are generated independently, they may produce inconsistent assessments of the same data. The assembly prompt must include explicit consistency requirements: when two sub-outputs conflict, how should the assembler handle it? Define this in the assembly prompt — not as a post-processing step.
2. What the Assembler Receives Must Be Complete The assembly prompt depends on all sub-outputs being available and complete. Run the completeness check before passing outputs to the assembler. A missing sub-output produces an assembly that silently omits a section — which is worse than an error, because it looks complete.