Massive Report Writing

Overview

Use evidence ledgering to compress large research corpora into structured, quotable material. For very large corpora, harness iteration handles multi-pass synthesis automatically.

When to Use

Workflow: Evidence Ledger Mode

1. Build Evidence Ledger

Call build_evidence_ledger(session_dir, topic, task_name) after finalize_research.

The tool extracts from each source:

• Direct quotes with attribution
• Specific numbers (percentages, counts, costs)
• Key dates and timelines
• Claims and findings

Output: tasks/{task_name}/evidence_ledger.md with EVID-XXX entries.

2. Read Only the Ledger

After ledger is built:

• ✅ Read evidence_ledger.md for synthesis
• ❌ Do NOT re-read raw corpus files
• ❌ Do NOT use read_research_files again

This is how you avoid context exhaustion.

3. Write Report from Ledger

Use EVID-XXX references when citing:

According to ISW (EVID-003), Russian forces gained 74 square miles...

Harness Integration

When corpus exceeds safe limits AND harness mode is active:

1. Iteration 1: finalize → build ledger → ledger saved to disk → context exhaustion
2. Harness restart: Context cleared, handoff.json injected
3. Iteration 2: Read ledger from disk → write report

The harness handles multi-pass automatically. You don't need map-reduce orchestration.

Chunked Write Sequence

Use when single Write calls fail or output is >30KB:

1) Write header + CSS + title block
2) Append executive summary
3) Append Section 1 (cite EVID-XXX)
4) Append Section 2
... repeat ...
N) Append references

Use append_to_file for sections 2-N.

Templates

See references/massive_report_templates.md for:

• Evidence ledger entry format
• Section outline template
• Chunked write sequence

Anti-Summary-of-Summary Rule

• Every claim in the final report must trace to an EVID-XXX
• If a point cannot be traced to a ledger item, drop it or re-read the source
• Batch summaries (if used) are navigation only, not source material