Anchor Sheet (evidence → write hooks) [NO PROSE]

Purpose: make “what to actually say” explicit:

• - select quantitative snippets (numbers/percentages)
• select evaluation anchors (benchmarks/datasets/metrics)
• select limitations/failure hooks

This prevents the writer from producing paragraph-shaped but content-poor prose.

Inputs

• - INLINECODE0
• INLINECODE1

Outputs

• - INLINECODE2

Output format (outline/anchor_sheet.jsonl)

JSONL (one object per H3 subsection).

Required fields:

• - sub_id, INLINECODE5
• INLINECODE6 (list; each anchor has hook_type, text, citations, and optional paper_id/evidence_id/pointer)

Workflow

1. 1. Read outline/evidence_drafts.jsonl.
2. Prefer anchors that contain:

1. 3. Filter anchors to only citation keys present in citations/ref.bib.
2. Write outline/anchor_sheet.jsonl.

Quality checklist

• - [ ] Every H3 has >=10 cite-backed anchors (A150++ hard target).
• [ ] At least 1 anchor contains digits when the evidence pack contains digits.
• [ ] No placeholders (TODO/…/(placeholder)).

Consumption policy (for C5 writers)

Anchors are intended to prevent “long but empty” prose. Treat them as must-use hooks, not optional ideas.

Recommended minimums per H3 (A150++):

• - >=3 protocol anchors (benchmark/dataset/metric/budget/tool access)
• >=3 limitation/failure hooks (concrete, not generic “future work”)
• If digits exist in the evidence pack: include >=1 cited numeric anchor (digit + citation in the same paragraph)

Note:

• - Anchor text is trimmed for readability and does not include ellipsis markers (to reduce accidental leakage into prose).

Script

Quick Start

• - INLINECODE17
• INLINECODE18

All Options

• - INLINECODE19
• INLINECODE20
• INLINECODE21
• INLINECODE22
• INLINECODE23

Examples

• - Default IO:

• - Explicit IO:

Refinement marker (recommended; prevents churn)

When you are satisfied with anchor facts (and they are actually subsection-specific), create:

• - INLINECODE26

This is an explicit "I reviewed/refined this" signal:

• - prevents scripts from regenerating and undoing your work
• (in strict runs) can be used as a completion signal before writing