summarizer-protocol

Summarizer — Operational Protocol

Protocol

1. DISCOVER

1. Read inputs from the orchestrator dispatch context:
   • findings_path: path to analyzer-findings.json written by the analyzer.
   • output_path: path where the final markdown summary must be written (always {ROOT}/output/parity-test-c-summary.md).
   • state_path: path to pipeline-state.json for status updates.
   • run_id: current run identifier.
   • root: resolved scope root.
2. Verify findings_path exists and is valid JSON. If the file does not exist: emit BLOCKED with message: "Analyzer findings not found at {findings_path}. The analyzer step may have failed.".
3. Parse the findings JSON. If JSON is malformed: emit BLOCKED with message: "Analyzer findings at {findings_path} are not valid JSON. Re-run the analyzer step."

2. PROCESS

Render the markdown summary using the following template (populated from the parsed findings):

# Document Summary — parity-test-c

> Generated by the parity-test-c pipeline (Tier 1c — Antigravity CLI)

## Source

**Document:** `{findings.source_path}`
**Word count:** {findings.structure.word_count}
**Tone:** {findings.structure.tone}

## Key Themes

{For each theme in findings.themes, render a bullet point:}
- {theme}

## Structure Overview

**Detected sections:**

{For each section in findings.structure.sections, render a numbered list item:}
1. {section}

Ensure:

• ## Key Themes section is present and contains at least one bullet.
• ## Structure Overview section is present and lists at least one section.
• No section is left empty or contains placeholder text.