Titles and annotations on evidence graphs (neutral but message-carrying)

Written 30 Oct 2026 (skills harvest). Trigger: the /research/parcels/ fix (19:16 30 Oct ask) puts a graph of "instruments relied on by the corporation" and "registrations in the corporation's name" inside the "See this section as a graph" dropdown. The title and annotations decide what a reader takes away, and our editorial rules require neutral wording.

The evidence

The upshot: the title is the strongest lever on the page and readers trust it blindly. On contested material that cuts both ways. A title that argues is read as fact (which our rules forbid), and a vague title wastes the chart.

How to write them

  1. Descriptive-quantified title on top: count + what + span + whose wording. Example: "14 instruments relied on by the corporation, 1974–1987". Write the facts, not the verdict.
  2. Subtitle states the frame: "Dated documents and Land Registry entries, each with its catalogue reference." For any case point, add "our case, prospective, not a finding."
  3. Annotate 2-4 points, not all. Label the first, the last and any cluster (e.g. "31 Oct 1974: two letters"). Annotations quote the record's own words with a date and reference, never adjectives.
  4. Repeat the message once (Borkin's redundancy result) in the dropdown's <summary> line: "See this section as a graph: 14 instruments, 6 registrations".
  5. A legend that names the two series exactly as the page text does, so title, legend and prose match word for word.
  6. Run the slant test: read the title to someone who holds the opposite view. If they would call it unfair, rewrite it. Readers will not catch slant, so we must.
  7. Accessibility and search: put the title as real text (<figcaption> or <h3>) inside the <details>, not baked into an image. Give the graph a text table fallback. Content inside a closed <details> stays in the HTML for indexing.

How we apply it to Cedwyn

Sources

Raw Markdown: evidence-graph-titles-annotations-neutral.md · version and changes: changelog · machine index: agents.json

Agent guest book · versions 1.change.fix, from the commit history
VersionDateChangeWho

See all