{
  "code": "S89",
  "name": "Dated timeline",
  "shape": "dated-events",
  "family": "Lists and comparisons",
  "fits": "A static chronology where each date carries real prose: three to five dates down one column, each with one or more events (a headline and a short paragraph).",
  "use_when": "When the order of events is the argument and each step needs a sentence or two, not just a label. For phases with an icon and a caption use S35 Timeline; for a scrolled story with a sticky dial use S80.",
  "slots": [
    {
      "name": "title",
      "holds": "page title, top left of the column",
      "budget": "under 7 words"
    },
    {
      "name": "date",
      "holds": "per block: the date as a small accent caps kicker beside a hollow dot on the rail",
      "budget": "1-4 words"
    },
    {
      "name": "headline",
      "holds": "per event: a short headline (a date block may hold two events)",
      "budget": "under 10 words"
    },
    {
      "name": "text",
      "holds": "per event: one to three sentences, optionally a second paragraph; hidden in the compact option",
      "budget": "under 45 words"
    }
  ],
  "columns": 1,
  "density": "standard",
  "surface": "paper",
  "works_on": [
    "deck",
    "page"
  ],
  "library": "Reuters",
  "dir": "S89-dated-timeline",
  "semantic": {
    "audience_question": "What happened on each date, and how did the story develop?",
    "intent": "Follow dated events with enough prose to understand their consequences.",
    "reasoning_relation": "dated event sequence",
    "message_pattern": "On [date], [event] occurred, changing [specific condition].",
    "required_content": [
      "Names the development this chronology explains.",
      "Three to five date groups, using precise dates or honest ranges.",
      "A concise event heading for every event, including multiple events on one date.",
      "A short sourced description and relevant uncertainty for every event."
    ],
    "narrative_positions": [
      "context",
      "evidence"
    ],
    "requires_before": [
      "Name the current situation or question."
    ],
    "enables_after": [
      "Assess the evidence for a proposed mechanism or decision."
    ],
    "slot_roles": {
      "title": "Names the development this chronology explains.",
      "date": "Three to five date groups, using precise dates or honest ranges.",
      "headline": "A concise event heading for every event, including multiple events on one date.",
      "text": "A short sourced description and relevant uncertainty for every event."
    },
    "avoid_when": [
      "An undated process.",
      "A forecast presented as completed history."
    ],
    "layout_specific_contract": "A static chronology where each date carries real prose: three to five dates down one column, each with one or more events (a headline and a short paragraph).",
    "provenance": {
      "basis": "interpretation of the existing layout and slot contracts",
      "review": "Tessel model-authored guidance; implementation approved by Nic, 2026-10-10",
      "corpus_evidence_status": "not yet established",
      "guide": "../SEMANTICS.md"
    },
    "variation_rule": "Read the selected option’s actual markup, slot count and source record. Preserve this reasoning relationship only if the option still expresses it; flag a mismatch before adapting.",
    "reader_outcome": "Follow dated events with enough prose to understand their consequences.",
    "matching": {
      "audience_question": "What happened on each date, and how did the story develop?",
      "reader_outcome": "Follow dated events with enough prose to understand their consequences.",
      "reasoning_relation": "dated event sequence",
      "content_shape": {
        "composition": "A static chronology where each date carries real prose: three to five dates down one column, each with one or more events (a headline and a short paragraph).",
        "selected_state": "A static chronology where each date carries real prose: three to five dates down one column, each with one or more events (a headline and a short paragraph).",
        "density": "standard",
        "columns": 1,
        "column_note": "Base metadata only; selected option can replace the base geometry."
      },
      "required_slots": [
        {
          "name": "title",
          "reader_question": "What happened on each date, and how did the story develop?",
          "semantic_role": "Names the development this chronology explains.",
          "content_unit_count": {
            "min": 1,
            "max": 1,
            "basis": "authored composition members where a repeated group is specified; otherwise one named slot; not a required amount of evidence"
          },
          "placeholder": "[REAL CONTENT · title · page title, top left of the column]",
          "layout_budget": {
            "authored": "under 7 words",
            "policy": "Working composition guidance: preserve scope and qualification; change layout rather than truncate the argument."
          },
          "markup": {
            "slot": "title",
            "occurrences": 1,
            "annotation_status": "present",
            "visibility_status": "not asserted from static parsing",
            "sample_word_counts": [
              5
            ]
          }
        },
        {
          "name": "date",
          "reader_question": "What does the date contribute to this page’s reader outcome?",
          "semantic_role": "Three to five date groups, using precise dates or honest ranges.",
          "content_unit_count": {
            "min": 3,
            "max": 3,
            "basis": "Authored visible members in the selected arrangement; annotation occurrences can differ."
          },
          "placeholder": "[REAL CONTENT · date · per block: the date as a small accent caps kicker beside a hollow dot on the rail]",
          "layout_budget": {
            "authored": "1-4 words",
            "policy": "Working composition guidance: preserve scope and qualification; change layout rather than truncate the argument."
          },
          "markup": {
            "slot": "date",
            "occurrences": 1,
            "annotation_status": "Semantic role explicitly mapped to authored selector; do not infer a data-slot with this name.",
            "visibility_status": "Selected-state structure inspected; conditional or decorative regions can be absent in narrow/complete states.",
            "sample_word_counts": [
              2
            ],
            "selector": "[data-spread=\"S89\"] .tl .date"
          }
        },
        {
          "name": "headline",
          "reader_question": "What happened on each date, and how did the story develop?",
          "semantic_role": "A concise event heading for every event, including multiple events on one date.",
          "content_unit_count": {
            "min": 4,
            "max": 4,
            "basis": "Authored visible members in the selected arrangement; annotation occurrences can differ."
          },
          "placeholder": "[REAL CONTENT · headline · per event: a short headline (a date block may hold two events)]",
          "layout_budget": {
            "authored": "under 10 words",
            "policy": "Working composition guidance: preserve scope and qualification; change layout rather than truncate the argument."
          },
          "markup": {
            "slot": "headline",
            "occurrences": 1,
            "annotation_status": "Semantic role explicitly mapped to authored selector; do not infer a data-slot with this name.",
            "visibility_status": "Selected-state structure inspected; conditional or decorative regions can be absent in narrow/complete states.",
            "sample_word_counts": [
              4
            ],
            "selector": "[data-spread=\"S89\"] .ev h3"
          }
        },
        {
          "name": "text",
          "reader_question": "What does the text contribute to this page’s reader outcome?",
          "semantic_role": "A short sourced description and relevant uncertainty for every event.",
          "content_unit_count": {
            "min": 5,
            "max": 5,
            "basis": "Authored visible members in the selected arrangement; annotation occurrences can differ."
          },
          "placeholder": "[REAL CONTENT · text · per event: one to three sentences, optionally a second paragraph; hidden in the compact option]",
          "layout_budget": {
            "authored": "under 45 words",
            "policy": "Working composition guidance: preserve scope and qualification; change layout rather than truncate the argument."
          },
          "markup": {
            "slot": "text",
            "occurrences": 1,
            "annotation_status": "Semantic role explicitly mapped to authored selector; do not infer a data-slot with this name.",
            "visibility_status": "Selected-state structure inspected; conditional or decorative regions can be absent in narrow/complete states.",
            "sample_word_counts": [
              35
            ],
            "selector": "[data-spread=\"S89\"] .ev p"
          }
        }
      ],
      "rejection_constraints": [
        "Dates treated as causal proof or later events silently collapsed into earlier date blocks.",
        "Invented dates or implying that the later event was caused by the earlier one."
      ],
      "option_guidance": {
        "option": "default",
        "composition_delta": "A static chronology where each date carries real prose: three to five dates down one column, each with one or more events (a headline and a short paragraph).",
        "semantic_change": "retains base content relationship; changes presentation or disclosure",
        "matching_instruction": "Select S89 default when the supplied material answers “What happened on each date, and how did the story develop?” through dated event sequence. Respect this state: A static chronology where each date carries real prose: three to five dates down one column, each with one or more events (a headline and a short paragraph)."
      },
      "provenance": {
        "status": "inferred composition evidence",
        "author_intent": "not independently confirmed",
        "basis": [
          "retained source composition where available",
          "authored layout and slot contracts",
          "static implementation inspection"
        ],
        "source_visual_count": 1,
        "source_visual_sha256": [
          "05b5015c2631ecaf5a2670d5f37752030dfa6802889c78f932bc82408b37588e"
        ],
        "source_export": "private source images remain outside this draft site",
        "markup_sha256": "8473c6eb2de7c847b46c3fd5a2ad43928c457afd79b64a1ea7346fc0828e5d46",
        "limits": [
          "Static parsing inventories authored nodes; it does not certify rendered visibility, responsive fit or interactive state.",
          "Budgets are authored layout guidance, not a content-writing limit or proof of fit.",
          "Matching guidance is a draft inference; it does not establish facts, endorsement, causation or source author intent."
        ]
      },
      "adaptation_rules": [
        "Choose by audience question, reasoning relation and required content before aesthetic preference.",
        "Supply every required semantic role; retain visible unknowns as labelled real-content placeholders.",
        "A number needs source, scope and units; a quotation needs faithful wording and attribution.",
        "Do not infer importance from area, colour, depth or movement unless the content explicitly defines that encoding.",
        "Keep colour token roles, structural objects, licences and source records; changing content does not authorize changing them."
      ],
      "previous_required_slots": [
        {
          "name": "title",
          "reader_question": "What happened on each date, and how did the story develop?",
          "semantic_role": "page title, top left of the column",
          "content_unit_count": {
            "min": 1,
            "max": 1,
            "basis": "authored composition members where a repeated group is specified; otherwise one named slot; not a required amount of evidence"
          },
          "placeholder": "[REAL CONTENT · title · page title, top left of the column]",
          "layout_budget": {
            "authored": "under 7 words",
            "policy": "Working composition guidance: preserve scope and qualification; change layout rather than truncate the argument."
          },
          "markup": {
            "slot": "title",
            "occurrences": 1,
            "annotation_status": "present",
            "visibility_status": "not asserted from static parsing",
            "sample_word_counts": [
              5
            ]
          }
        },
        {
          "name": "date",
          "reader_question": "What does the date contribute to this page’s reader outcome?",
          "semantic_role": "per block: the date as a small accent caps kicker beside a hollow dot on the rail",
          "content_unit_count": {
            "min": 3,
            "max": 5,
            "basis": "authored composition members where a repeated group is specified; otherwise one named slot; not a required amount of evidence"
          },
          "placeholder": "[REAL CONTENT · date · per block: the date as a small accent caps kicker beside a hollow dot on the rail]",
          "layout_budget": {
            "authored": "1-4 words",
            "policy": "Working composition guidance: preserve scope and qualification; change layout rather than truncate the argument."
          },
          "markup": {
            "slot": "date",
            "occurrences": 1,
            "annotation_status": "present",
            "visibility_status": "not asserted from static parsing",
            "sample_word_counts": [
              2
            ]
          }
        },
        {
          "name": "headline",
          "reader_question": "What happened on each date, and how did the story develop?",
          "semantic_role": "per event: a short headline (a date block may hold two events)",
          "content_unit_count": {
            "min": 1,
            "max": 1,
            "basis": "authored composition members where a repeated group is specified; otherwise one named slot; not a required amount of evidence"
          },
          "placeholder": "[REAL CONTENT · headline · per event: a short headline (a date block may hold two events)]",
          "layout_budget": {
            "authored": "under 10 words",
            "policy": "Working composition guidance: preserve scope and qualification; change layout rather than truncate the argument."
          },
          "markup": {
            "slot": "headline",
            "occurrences": 1,
            "annotation_status": "present",
            "visibility_status": "not asserted from static parsing",
            "sample_word_counts": [
              4
            ]
          }
        },
        {
          "name": "text",
          "reader_question": "What does the text contribute to this page’s reader outcome?",
          "semantic_role": "per event: one to three sentences, optionally a second paragraph; hidden in the compact option",
          "content_unit_count": {
            "min": 1,
            "max": 1,
            "basis": "authored composition members where a repeated group is specified; otherwise one named slot; not a required amount of evidence"
          },
          "placeholder": "[REAL CONTENT · text · per event: one to three sentences, optionally a second paragraph; hidden in the compact option]",
          "layout_budget": {
            "authored": "under 45 words",
            "policy": "Working composition guidance: preserve scope and qualification; change layout rather than truncate the argument."
          },
          "markup": {
            "slot": "text",
            "occurrences": 1,
            "annotation_status": "present",
            "visibility_status": "not asserted from static parsing",
            "sample_word_counts": [
              35
            ]
          }
        }
      ],
      "contract_correction": {
        "date": "2026-10-13",
        "basis": "Actual selected HTML/CSS inspection; previous required slots retained for review.",
        "records": [
          {
            "code": "S89",
            "option": "default",
            "selectors": {
              "date": "[data-spread=\"S89\"] .tl .date",
              "headline": "[data-spread=\"S89\"] .ev h3",
              "text": "[data-spread=\"S89\"] .ev p"
            },
            "counts": {
              "date": 3,
              "headline": 4,
              "text": 5
            },
            "reason": "Only first date/headline/text annotated; actual markup has three dates, four events and five descriptive paragraphs."
          }
        ]
      }
    },
    "rejection_constraints": [
      "Dates treated as causal proof or later events silently collapsed into earlier date blocks.",
      "Invented dates or implying that the later event was caused by the earlier one."
    ],
    "markup_inventory": {
      "file": "spread.html",
      "sha256": "8473c6eb2de7c847b46c3fd5a2ad43928c457afd79b64a1ea7346fc0828e5d46",
      "method": "static lxml markup plus authored option description; no rendered-visibility claim",
      "all_markup_slot_counts": {
        "title": 1,
        "dates": 1,
        "date": 1,
        "event": 1,
        "headline": 1,
        "text": 1
      },
      "slot_evidence": {
        "title": [
          {
            "tag": "h2",
            "classes": "head",
            "sample_word_count": 5,
            "repeated_children": 0
          }
        ],
        "dates": [
          {
            "tag": "ol",
            "classes": "tl",
            "sample_word_count": 143,
            "repeated_children": 3
          }
        ],
        "date": [
          {
            "tag": "p",
            "classes": "date",
            "sample_word_count": 2,
            "repeated_children": 0
          }
        ],
        "event": [
          {
            "tag": "div",
            "classes": "ev",
            "sample_word_count": 39,
            "repeated_children": 2
          }
        ],
        "headline": [
          {
            "tag": "h3",
            "classes": "",
            "sample_word_count": 4,
            "repeated_children": 0
          }
        ],
        "text": [
          {
            "tag": "p",
            "classes": "",
            "sample_word_count": 35,
            "repeated_children": 0
          }
        ]
      },
      "option_selectors": [
        "compact",
        "rows"
      ],
      "linked_implementation": [
        {
          "file": "../spreads.css",
          "sha256": "32da94472b0c9131e4d5dae7d5bf0498b09202a9e66294b4e4f23e6ddfbf37ba"
        },
        {
          "file": "../spread.js",
          "sha256": "3d99948b83f750bd4ae95dac08e3e50a395de7c149c90a6f1a1c0ea36a2634a4"
        }
      ]
    },
    "variations": {
      "rows": {
        "audience_question": "What happened on each date, and how did the story develop?",
        "intent": "Follow dated events with enough prose to understand their consequences.",
        "reader_outcome": "Follow dated events with enough prose to understand their consequences.",
        "reasoning_relation": "dated event sequence",
        "slot_roles": {
          "title": "Names the development this chronology explains.",
          "date": "Three to five date groups, using precise dates or honest ranges.",
          "headline": "A concise event heading for every event, including multiple events on one date.",
          "text": "A short sourced description and relevant uncertainty for every event."
        },
        "matching": {
          "audience_question": "What happened on each date, and how did the story develop?",
          "reader_outcome": "Follow dated events with enough prose to understand their consequences.",
          "reasoning_relation": "dated event sequence",
          "content_shape": {
            "composition": "A static chronology where each date carries real prose: three to five dates down one column, each with one or more events (a headline and a short paragraph).",
            "selected_state": "No rail: hairline-separated rows of date, bold title and description across the full width (WebSlides dated rows)",
            "density": "standard",
            "columns": 1,
            "column_note": "Base metadata only; selected option can replace the base geometry."
          },
          "required_slots": [
            {
              "name": "title",
              "reader_question": "What happened on each date, and how did the story develop?",
              "semantic_role": "Names the development this chronology explains.",
              "content_unit_count": {
                "min": 1,
                "max": 1,
                "basis": "authored composition members where a repeated group is specified; otherwise one named slot; not a required amount of evidence"
              },
              "placeholder": "[REAL CONTENT · title · page title, top left of the column]",
              "layout_budget": {
                "authored": "under 7 words",
                "policy": "Working composition guidance: preserve scope and qualification; change layout rather than truncate the argument."
              },
              "markup": {
                "slot": "title",
                "occurrences": 1,
                "annotation_status": "present",
                "visibility_status": "not asserted from static parsing",
                "sample_word_counts": [
                  5
                ]
              }
            },
            {
              "name": "date",
              "reader_question": "What does the date contribute to this page’s reader outcome?",
              "semantic_role": "Three to five date groups, using precise dates or honest ranges.",
              "content_unit_count": {
                "min": 3,
                "max": 3,
                "basis": "Authored visible members in the selected arrangement; annotation occurrences can differ."
              },
              "placeholder": "[REAL CONTENT · date · per block: the date as a small accent caps kicker beside a hollow dot on the rail]",
              "layout_budget": {
                "authored": "1-4 words",
                "policy": "Working composition guidance: preserve scope and qualification; change layout rather than truncate the argument."
              },
              "markup": {
                "slot": "date",
                "occurrences": 1,
                "annotation_status": "Semantic role explicitly mapped to authored selector; do not infer a data-slot with this name.",
                "visibility_status": "Selected-state structure inspected; conditional or decorative regions can be absent in narrow/complete states.",
                "sample_word_counts": [
                  2
                ],
                "selector": "[data-spread=\"S89\"] .tl .date"
              }
            },
            {
              "name": "headline",
              "reader_question": "What happened on each date, and how did the story develop?",
              "semantic_role": "A concise event heading for every event, including multiple events on one date.",
              "content_unit_count": {
                "min": 4,
                "max": 4,
                "basis": "Authored visible members in the selected arrangement; annotation occurrences can differ."
              },
              "placeholder": "[REAL CONTENT · headline · per event: a short headline (a date block may hold two events)]",
              "layout_budget": {
                "authored": "under 10 words",
                "policy": "Working composition guidance: preserve scope and qualification; change layout rather than truncate the argument."
              },
              "markup": {
                "slot": "headline",
                "occurrences": 1,
                "annotation_status": "Semantic role explicitly mapped to authored selector; do not infer a data-slot with this name.",
                "visibility_status": "Selected-state structure inspected; conditional or decorative regions can be absent in narrow/complete states.",
                "sample_word_counts": [
                  4
                ],
                "selector": "[data-spread=\"S89\"] .ev h3"
              }
            },
            {
              "name": "text",
              "reader_question": "What does the text contribute to this page’s reader outcome?",
              "semantic_role": "A short sourced description and relevant uncertainty for every event.",
              "content_unit_count": {
                "min": 5,
                "max": 5,
                "basis": "Authored visible members in the selected arrangement; annotation occurrences can differ."
              },
              "placeholder": "[REAL CONTENT · text · per event: one to three sentences, optionally a second paragraph; hidden in the compact option]",
              "layout_budget": {
                "authored": "under 45 words",
                "policy": "Working composition guidance: preserve scope and qualification; change layout rather than truncate the argument."
              },
              "markup": {
                "slot": "text",
                "occurrences": 1,
                "annotation_status": "Semantic role explicitly mapped to authored selector; do not infer a data-slot with this name.",
                "visibility_status": "Selected-state structure inspected; conditional or decorative regions can be absent in narrow/complete states.",
                "sample_word_counts": [
                  35
                ],
                "selector": "[data-spread=\"S89\"] .ev p"
              }
            }
          ],
          "rejection_constraints": [
            "Dates treated as causal proof or later events silently collapsed into earlier date blocks.",
            "Invented dates or implying that the later event was caused by the earlier one."
          ],
          "option_guidance": {
            "option": "rows",
            "composition_delta": "No rail: hairline-separated rows of date, bold title and description across the full width (WebSlides dated rows)",
            "semantic_change": "retains base content relationship; changes presentation or disclosure",
            "matching_instruction": "Select S89 rows when the supplied material answers “What happened on each date, and how did the story develop?” through dated event sequence. Respect this state: No rail: hairline-separated rows of date, bold title and description across the full width (WebSlides dated rows)"
          },
          "provenance": {
            "status": "inferred composition evidence",
            "author_intent": "not independently confirmed",
            "basis": [
              "retained source composition where available",
              "authored layout and slot contracts",
              "static implementation inspection"
            ],
            "source_visual_count": 1,
            "source_visual_sha256": [
              "05b5015c2631ecaf5a2670d5f37752030dfa6802889c78f932bc82408b37588e"
            ],
            "source_export": "private source images remain outside this draft site",
            "markup_sha256": "8473c6eb2de7c847b46c3fd5a2ad43928c457afd79b64a1ea7346fc0828e5d46",
            "limits": [
              "Static parsing inventories authored nodes; it does not certify rendered visibility, responsive fit or interactive state.",
              "Budgets are authored layout guidance, not a content-writing limit or proof of fit.",
              "Matching guidance is a draft inference; it does not establish facts, endorsement, causation or source author intent."
            ]
          },
          "adaptation_rules": [
            "Choose by audience question, reasoning relation and required content before aesthetic preference.",
            "Supply every required semantic role; retain visible unknowns as labelled real-content placeholders.",
            "A number needs source, scope and units; a quotation needs faithful wording and attribution.",
            "Do not infer importance from area, colour, depth or movement unless the content explicitly defines that encoding.",
            "Keep colour token roles, structural objects, licences and source records; changing content does not authorize changing them."
          ],
          "previous_required_slots": [
            {
              "name": "title",
              "reader_question": "What happened on each date, and how did the story develop?",
              "semantic_role": "page title, top left of the column",
              "content_unit_count": {
                "min": 1,
                "max": 1,
                "basis": "authored composition members where a repeated group is specified; otherwise one named slot; not a required amount of evidence"
              },
              "placeholder": "[REAL CONTENT · title · page title, top left of the column]",
              "layout_budget": {
                "authored": "under 7 words",
                "policy": "Working composition guidance: preserve scope and qualification; change layout rather than truncate the argument."
              },
              "markup": {
                "slot": "title",
                "occurrences": 1,
                "annotation_status": "present",
                "visibility_status": "not asserted from static parsing",
                "sample_word_counts": [
                  5
                ]
              }
            },
            {
              "name": "date",
              "reader_question": "What does the date contribute to this page’s reader outcome?",
              "semantic_role": "per block: the date as a small accent caps kicker beside a hollow dot on the rail",
              "content_unit_count": {
                "min": 3,
                "max": 5,
                "basis": "authored composition members where a repeated group is specified; otherwise one named slot; not a required amount of evidence"
              },
              "placeholder": "[REAL CONTENT · date · per block: the date as a small accent caps kicker beside a hollow dot on the rail]",
              "layout_budget": {
                "authored": "1-4 words",
                "policy": "Working composition guidance: preserve scope and qualification; change layout rather than truncate the argument."
              },
              "markup": {
                "slot": "date",
                "occurrences": 1,
                "annotation_status": "present",
                "visibility_status": "not asserted from static parsing",
                "sample_word_counts": [
                  2
                ]
              }
            },
            {
              "name": "headline",
              "reader_question": "What happened on each date, and how did the story develop?",
              "semantic_role": "per event: a short headline (a date block may hold two events)",
              "content_unit_count": {
                "min": 1,
                "max": 1,
                "basis": "authored composition members where a repeated group is specified; otherwise one named slot; not a required amount of evidence"
              },
              "placeholder": "[REAL CONTENT · headline · per event: a short headline (a date block may hold two events)]",
              "layout_budget": {
                "authored": "under 10 words",
                "policy": "Working composition guidance: preserve scope and qualification; change layout rather than truncate the argument."
              },
              "markup": {
                "slot": "headline",
                "occurrences": 1,
                "annotation_status": "present",
                "visibility_status": "not asserted from static parsing",
                "sample_word_counts": [
                  4
                ]
              }
            },
            {
              "name": "text",
              "reader_question": "What does the text contribute to this page’s reader outcome?",
              "semantic_role": "per event: one to three sentences, optionally a second paragraph; hidden in the compact option",
              "content_unit_count": {
                "min": 1,
                "max": 1,
                "basis": "authored composition members where a repeated group is specified; otherwise one named slot; not a required amount of evidence"
              },
              "placeholder": "[REAL CONTENT · text · per event: one to three sentences, optionally a second paragraph; hidden in the compact option]",
              "layout_budget": {
                "authored": "under 45 words",
                "policy": "Working composition guidance: preserve scope and qualification; change layout rather than truncate the argument."
              },
              "markup": {
                "slot": "text",
                "occurrences": 1,
                "annotation_status": "present",
                "visibility_status": "not asserted from static parsing",
                "sample_word_counts": [
                  35
                ]
              }
            }
          ],
          "contract_correction": {
            "date": "2026-10-13",
            "basis": "Actual selected HTML/CSS inspection; previous required slots retained for review.",
            "records": [
              {
                "code": "S89",
                "option": "rows",
                "selectors": {
                  "date": "[data-spread=\"S89\"] .tl .date",
                  "headline": "[data-spread=\"S89\"] .ev h3",
                  "text": "[data-spread=\"S89\"] .ev p"
                },
                "counts": {
                  "date": 3,
                  "headline": 4,
                  "text": 5
                },
                "reason": "Only first date/headline/text annotated; actual markup has three dates, four events and five descriptive paragraphs."
              }
            ]
          }
        },
        "narrative_profile": {
          "central_point": "Dated events explain how a situation developed, with enough prose to distinguish occurrence from interpretation.",
          "communication_job": "Present the same dated event account as ruled date/title/description rows.",
          "audience_value": "Offers context and perspective. It answers “What happened first, and what changed next?” while resisting hindsight and unsupported causal claims.",
          "reading_path": [
            "Read the title for the story being traced.",
            "Follow dates in a declared chronological direction.",
            "Read each event heading and its supporting description; several events may share a date.",
            "Separate the observed event from the implication drawn from it."
          ],
          "adaptation": {
            "required_inputs": [
              "Names the development this chronology explains.",
              "Three to five date groups, using precise dates or honest ranges.",
              "A concise event heading for every event, including multiple events on one date.",
              "A short sourced description and relevant uncertainty for every event."
            ],
            "slot_guidance": {
              "title": "Names the development this chronology explains.",
              "date": "Three to five date groups, using precise dates or honest ranges.",
              "headline": "A concise event heading for every event, including multiple events on one date.",
              "text": "A short sourced description and relevant uncertainty for every event."
            },
            "can_change": [
              "Replace the fictional subject and its supported content while retaining the roles and relationship described here."
            ],
            "must_survive": [
              "Keep date certainty, chronology direction and event/source pairing.",
              "Do not collapse multiple events into an invented single causal milestone.",
              "Keep forecasts and retrospective observations explicitly distinct."
            ]
          },
          "worked_example": {
            "fictional": true,
            "scenario": "Fictional Cedar’s repair pilot evolves over three months.",
            "slot_fills": {
              "title": "How the pilot became repeatable",
              "date": [
                "January — fictional",
                "February — fictional",
                "March — fictional"
              ],
              "headline": [
                "Intake queues expose a handoff problem",
                "Volunteers rehearse a common checklist",
                "A practice session identifies confusing wording",
                "The team records a revised method"
              ],
              "text": [
                "Visitors waited after reaching a repair table while volunteers repeated intake questions.",
                "Cedar proposed a shared safety checklist and rehearsed it with new volunteers.",
                "A fictional March practice session identified confusing wording in two intake questions.",
                "The team rewrote those questions and recorded what changed.",
                "This fictional sequence does not establish that the revision reduced waiting; a separate comparison would be needed."
              ]
            },
            "reasoning": "Dates anchor separate events; prose explains their relevance without converting “after” into “because of”.",
            "qualification": "Fictional teaching example. Replace invented details with authorised content and keep any source, scope, status or uncertainty that affects interpretation."
          },
          "narrative_fit": {
            "before": "Name the current situation or question.",
            "after": "Assess the evidence for a proposed mechanism or decision.",
            "good_uses": [
              "A documented sequence of decisions or events."
            ],
            "poor_fits": [
              "An undated process.",
              "A forecast presented as completed history."
            ]
          },
          "evidence": {
            "observations": [
              "Viewed source: dates form a vertical rail, with multiple titled events and descriptive paragraphs within one date.",
              "Current markup has three dates and four events; only the first date/headline/text are individually annotated.",
              "Current option markup/CSS: Present the same dated event account as ruled date/title/description rows.",
              "Corrected matching uses explicit selectors for all three date groups and four event headings, plus five paragraphs when visible; the compact state excludes hidden paragraphs."
            ],
            "interpretations": [
              "Dated events explain how a situation developed, with enough prose to distinguish occurrence from interpretation. This is an interpretation of the inspected composition, not a verified claim of author intent."
            ],
            "not_verified": [
              "Original author intent, historical claims, persuasion and archive-wide frequency have not been independently verified."
            ],
            "references": [
              "02_product/spreads/S89-dated-timeline/source.webp",
              "02_product/spreads-semantics-2026-10-13/dist/S89-dated-timeline/spread.html",
              "02_product/spreads-semantics-2026-10-13/dist/S89-dated-timeline/spread.json",
              "https://reuters-graphics.github.io/graphics-components/iframe.html?id=components-text-elements-simpletimeline--multiple-events&viewMode=story"
            ]
          },
          "review": {
            "status": "reviewed",
            "basis": "Viewed the base source capture and inspected this option’s current markup, CSS and matching contract. No distinct option-source capture was reviewed unless explicitly stated in observations. Rechecked integrated matching on 2026-10-13: required roles, example fills and repeated-item counts agree. Previously provisional because repeated events were represented by the first annotated entry. Explicit selectors and counts now cover three dates, four event headings and five paragraphs; compact correctly omits hidden paragraphs. Historical issue details remain in contract-issues-reading.json. This review does not establish original author intent or verify playback."
          },
          "variation_relationship": "same-job"
        },
        "required_content": [
          "Names the development this chronology explains.",
          "Three to five date groups, using precise dates or honest ranges.",
          "A concise event heading for every event, including multiple events on one date.",
          "A short sourced description and relevant uncertainty for every event."
        ],
        "requires_before": [
          "Name the current situation or question."
        ],
        "enables_after": [
          "Assess the evidence for a proposed mechanism or decision."
        ],
        "avoid_when": [
          "An undated process.",
          "A forecast presented as completed history."
        ]
      },
      "compact": {
        "audience_question": "Which dated events define this chronology at a glance?",
        "intent": "Scan real dates and concise event headlines, with detail supplied elsewhere.",
        "reader_outcome": "Scan real dates and concise event headlines, with detail supplied elsewhere.",
        "reasoning_relation": "dated event index",
        "slot_roles": {
          "title": "Names the development this chronology explains.",
          "date": "Three to five date groups, using precise dates or honest ranges.",
          "headline": "A concise event heading for every event, including multiple events on one date."
        },
        "matching": {
          "audience_question": "Which dated events define this chronology at a glance?",
          "reader_outcome": "Scan real dates and concise event headlines, with detail supplied elsewhere.",
          "reasoning_relation": "dated event index",
          "content_shape": {
            "composition": "A static chronology where each date carries real prose: three to five dates down one column, each with one or more events (a headline and a short paragraph).",
            "selected_state": "Date kickers and headlines only, like a contents list (Reuters BlogTOC)",
            "density": "standard",
            "columns": 1,
            "column_note": "Base metadata only; selected option can replace the base geometry."
          },
          "required_slots": [
            {
              "name": "title",
              "reader_question": "Which dated events define this chronology at a glance?",
              "semantic_role": "Names the development this chronology explains.",
              "content_unit_count": {
                "min": 1,
                "max": 1,
                "basis": "authored composition members where a repeated group is specified; otherwise one named slot; not a required amount of evidence"
              },
              "placeholder": "[REAL CONTENT · title · page title, top left of the column]",
              "layout_budget": {
                "authored": "under 7 words",
                "policy": "Working composition guidance: preserve scope and qualification; change layout rather than truncate the argument."
              },
              "markup": {
                "slot": "title",
                "occurrences": 1,
                "annotation_status": "present",
                "visibility_status": "not asserted from static parsing",
                "sample_word_counts": [
                  5
                ]
              }
            },
            {
              "name": "date",
              "reader_question": "What does the date contribute to this page’s reader outcome?",
              "semantic_role": "Three to five date groups, using precise dates or honest ranges.",
              "content_unit_count": {
                "min": 3,
                "max": 3,
                "basis": "Authored visible members in the selected arrangement; annotation occurrences can differ."
              },
              "placeholder": "[REAL CONTENT · date · per block: the date as a small accent caps kicker beside a hollow dot on the rail]",
              "layout_budget": {
                "authored": "1-4 words",
                "policy": "Working composition guidance: preserve scope and qualification; change layout rather than truncate the argument."
              },
              "markup": {
                "slot": "date",
                "occurrences": 1,
                "annotation_status": "Semantic role explicitly mapped to authored selector; do not infer a data-slot with this name.",
                "visibility_status": "Selected-state structure inspected; conditional or decorative regions can be absent in narrow/complete states.",
                "sample_word_counts": [
                  2
                ],
                "selector": "[data-spread=\"S89\"] .tl .date"
              }
            },
            {
              "name": "headline",
              "reader_question": "Which dated events define this chronology at a glance?",
              "semantic_role": "A concise event heading for every event, including multiple events on one date.",
              "content_unit_count": {
                "min": 4,
                "max": 4,
                "basis": "Authored visible members in the selected arrangement; annotation occurrences can differ."
              },
              "placeholder": "[REAL CONTENT · headline · per event: a short headline (a date block may hold two events)]",
              "layout_budget": {
                "authored": "under 10 words",
                "policy": "Working composition guidance: preserve scope and qualification; change layout rather than truncate the argument."
              },
              "markup": {
                "slot": "headline",
                "occurrences": 1,
                "annotation_status": "Semantic role explicitly mapped to authored selector; do not infer a data-slot with this name.",
                "visibility_status": "Selected-state structure inspected; conditional or decorative regions can be absent in narrow/complete states.",
                "sample_word_counts": [
                  4
                ],
                "selector": "[data-spread=\"S89\"] .ev h3"
              }
            }
          ],
          "rejection_constraints": [
            "Headlines insufficient to distinguish events or dates implying a causal argument without explanation.",
            "Invented dates or implying that the later event was caused by the earlier one."
          ],
          "option_guidance": {
            "option": "compact",
            "composition_delta": "Date kickers and headlines only, like a contents list (Reuters BlogTOC)",
            "semantic_change": "changes content relationship",
            "matching_instruction": "Select S89 compact when the supplied material answers “Which dated events define this chronology at a glance?” through dated event index. Respect this state: Date kickers and headlines only, like a contents list (Reuters BlogTOC)"
          },
          "provenance": {
            "status": "inferred composition evidence",
            "author_intent": "not independently confirmed",
            "basis": [
              "retained source composition where available",
              "authored layout and slot contracts",
              "static implementation inspection"
            ],
            "source_visual_count": 1,
            "source_visual_sha256": [
              "05b5015c2631ecaf5a2670d5f37752030dfa6802889c78f932bc82408b37588e"
            ],
            "source_export": "private source images remain outside this draft site",
            "markup_sha256": "8473c6eb2de7c847b46c3fd5a2ad43928c457afd79b64a1ea7346fc0828e5d46",
            "limits": [
              "Static parsing inventories authored nodes; it does not certify rendered visibility, responsive fit or interactive state.",
              "Budgets are authored layout guidance, not a content-writing limit or proof of fit.",
              "Matching guidance is a draft inference; it does not establish facts, endorsement, causation or source author intent."
            ]
          },
          "adaptation_rules": [
            "Choose by audience question, reasoning relation and required content before aesthetic preference.",
            "Supply every required semantic role; retain visible unknowns as labelled real-content placeholders.",
            "A number needs source, scope and units; a quotation needs faithful wording and attribution.",
            "Do not infer importance from area, colour, depth or movement unless the content explicitly defines that encoding.",
            "Keep colour token roles, structural objects, licences and source records; changing content does not authorize changing them."
          ],
          "previous_required_slots": [
            {
              "name": "title",
              "reader_question": "Which dated events define this chronology at a glance?",
              "semantic_role": "page title, top left of the column",
              "content_unit_count": {
                "min": 1,
                "max": 1,
                "basis": "authored composition members where a repeated group is specified; otherwise one named slot; not a required amount of evidence"
              },
              "placeholder": "[REAL CONTENT · title · page title, top left of the column]",
              "layout_budget": {
                "authored": "under 7 words",
                "policy": "Working composition guidance: preserve scope and qualification; change layout rather than truncate the argument."
              },
              "markup": {
                "slot": "title",
                "occurrences": 1,
                "annotation_status": "present",
                "visibility_status": "not asserted from static parsing",
                "sample_word_counts": [
                  5
                ]
              }
            },
            {
              "name": "date",
              "reader_question": "What does the date contribute to this page’s reader outcome?",
              "semantic_role": "per block: the date as a small accent caps kicker beside a hollow dot on the rail",
              "content_unit_count": {
                "min": 3,
                "max": 5,
                "basis": "authored composition members where a repeated group is specified; otherwise one named slot; not a required amount of evidence"
              },
              "placeholder": "[REAL CONTENT · date · per block: the date as a small accent caps kicker beside a hollow dot on the rail]",
              "layout_budget": {
                "authored": "1-4 words",
                "policy": "Working composition guidance: preserve scope and qualification; change layout rather than truncate the argument."
              },
              "markup": {
                "slot": "date",
                "occurrences": 1,
                "annotation_status": "present",
                "visibility_status": "not asserted from static parsing",
                "sample_word_counts": [
                  2
                ]
              }
            },
            {
              "name": "headline",
              "reader_question": "Which dated events define this chronology at a glance?",
              "semantic_role": "per event: a short headline (a date block may hold two events)",
              "content_unit_count": {
                "min": 1,
                "max": 1,
                "basis": "authored composition members where a repeated group is specified; otherwise one named slot; not a required amount of evidence"
              },
              "placeholder": "[REAL CONTENT · headline · per event: a short headline (a date block may hold two events)]",
              "layout_budget": {
                "authored": "under 10 words",
                "policy": "Working composition guidance: preserve scope and qualification; change layout rather than truncate the argument."
              },
              "markup": {
                "slot": "headline",
                "occurrences": 1,
                "annotation_status": "present",
                "visibility_status": "not asserted from static parsing",
                "sample_word_counts": [
                  4
                ]
              }
            }
          ],
          "contract_correction": {
            "date": "2026-10-13",
            "basis": "Actual selected HTML/CSS inspection; previous required slots retained for review.",
            "records": [
              {
                "code": "S89",
                "option": "compact",
                "selectors": {
                  "date": "[data-spread=\"S89\"] .tl .date",
                  "headline": "[data-spread=\"S89\"] .ev h3"
                },
                "counts": {
                  "date": 3,
                  "headline": 4
                },
                "reason": "Only first date/headline/text annotated; actual markup has three dates, four events and five descriptive paragraphs."
              }
            ]
          }
        },
        "narrative_profile": {
          "central_point": "A dated event index locates key moments; it does not contain their full explanation.",
          "communication_job": "Provide an index of dated events without their explanatory paragraphs.",
          "audience_value": "Offers context and perspective. It answers “What happened first, and what changed next?” while resisting hindsight and unsupported causal claims.",
          "reading_path": [
            "Read the title for the story being traced.",
            "Follow dates in a declared chronological direction.",
            "Read each event heading and its supporting description; several events may share a date.",
            "Separate the observed event from the implication drawn from it."
          ],
          "adaptation": {
            "required_inputs": [
              "Names the development this chronology explains.",
              "Three to five date groups, using precise dates or honest ranges.",
              "A concise event heading for every event, including multiple events on one date."
            ],
            "slot_guidance": {
              "title": "Names the development this chronology explains.",
              "date": "Three to five date groups, using precise dates or honest ranges.",
              "headline": "A concise event heading for every event, including multiple events on one date."
            },
            "can_change": [
              "Replace the fictional subject and its supported content while retaining the roles and relationship described here."
            ],
            "must_survive": [
              "Keep date certainty, chronology direction and event/source pairing.",
              "Do not collapse multiple events into an invented single causal milestone.",
              "Keep forecasts and retrospective observations explicitly distinct."
            ]
          },
          "worked_example": {
            "fictional": true,
            "scenario": "Fictional Cedar’s repair pilot evolves over three months.",
            "slot_fills": {
              "title": "How the pilot became repeatable",
              "date": [
                "January — fictional",
                "February — fictional",
                "March — fictional"
              ],
              "headline": [
                "Intake queues expose a handoff problem",
                "Volunteers rehearse a common checklist",
                "A practice session identifies confusing wording",
                "The team records a revised method"
              ]
            },
            "reasoning": "Dates anchor separate events; prose explains their relevance without converting “after” into “because of”.",
            "qualification": "Fictional teaching example. Replace invented details with authorised content and keep any source, scope, status or uncertainty that affects interpretation."
          },
          "narrative_fit": {
            "before": "Establish the story and make the fuller event account available.",
            "after": "Open the selected event or explain the relevant turning point.",
            "good_uses": [
              "A documented sequence of decisions or events."
            ],
            "poor_fits": [
              "An undated process.",
              "A forecast presented as completed history."
            ]
          },
          "evidence": {
            "observations": [
              "Viewed source: dates form a vertical rail, with multiple titled events and descriptive paragraphs within one date.",
              "Current markup has three dates and four events; only the first date/headline/text are individually annotated.",
              "Current option markup/CSS: Provide an index of dated events without their explanatory paragraphs.",
              "Corrected matching uses explicit selectors for all three date groups and four event headings, plus five paragraphs when visible; the compact state excludes hidden paragraphs."
            ],
            "interpretations": [
              "Dated events explain how a situation developed, with enough prose to distinguish occurrence from interpretation. This is an interpretation of the inspected composition, not a verified claim of author intent."
            ],
            "not_verified": [
              "Original author intent, historical claims, persuasion and archive-wide frequency have not been independently verified."
            ],
            "references": [
              "02_product/spreads/S89-dated-timeline/source.webp",
              "02_product/spreads-semantics-2026-10-13/dist/S89-dated-timeline/spread.html",
              "02_product/spreads-semantics-2026-10-13/dist/S89-dated-timeline/spread.json",
              "https://reuters-graphics.github.io/graphics-components/iframe.html?id=components-text-elements-simpletimeline--multiple-events&viewMode=story"
            ]
          },
          "review": {
            "status": "reviewed",
            "basis": "Viewed the base source capture and inspected this option’s current markup, CSS and matching contract. No distinct option-source capture was reviewed unless explicitly stated in observations. Rechecked integrated matching on 2026-10-13: required roles, example fills and repeated-item counts agree. Previously provisional because repeated events were represented by the first annotated entry. Explicit selectors and counts now cover three dates, four event headings and five paragraphs; compact correctly omits hidden paragraphs. Historical issue details remain in contract-issues-reading.json. This review does not establish original author intent or verify playback."
          },
          "variation_relationship": "different-job"
        },
        "required_content": [
          "Names the development this chronology explains.",
          "Three to five date groups, using precise dates or honest ranges.",
          "A concise event heading for every event, including multiple events on one date."
        ],
        "requires_before": [
          "Establish the story and make the fuller event account available."
        ],
        "enables_after": [
          "Open the selected event or explain the relevant turning point."
        ],
        "avoid_when": [
          "An undated process.",
          "A forecast presented as completed history."
        ]
      }
    },
    "narrative_profile": {
      "central_point": "Dated events explain how a situation developed, with enough prose to distinguish occurrence from interpretation.",
      "communication_job": "Reconstruct a chronology so the audience can locate turning points and what was known when.",
      "audience_value": "Offers context and perspective. It answers “What happened first, and what changed next?” while resisting hindsight and unsupported causal claims.",
      "reading_path": [
        "Read the title for the story being traced.",
        "Follow dates in a declared chronological direction.",
        "Read each event heading and its supporting description; several events may share a date.",
        "Separate the observed event from the implication drawn from it."
      ],
      "adaptation": {
        "required_inputs": [
          "Names the development this chronology explains.",
          "Three to five date groups, using precise dates or honest ranges.",
          "A concise event heading for every event, including multiple events on one date.",
          "A short sourced description and relevant uncertainty for every event."
        ],
        "slot_guidance": {
          "title": "Names the development this chronology explains.",
          "date": "Three to five date groups, using precise dates or honest ranges.",
          "headline": "A concise event heading for every event, including multiple events on one date.",
          "text": "A short sourced description and relevant uncertainty for every event."
        },
        "can_change": [
          "Replace the fictional subject and its supported content while retaining the roles and relationship described here."
        ],
        "must_survive": [
          "Keep date certainty, chronology direction and event/source pairing.",
          "Do not collapse multiple events into an invented single causal milestone.",
          "Keep forecasts and retrospective observations explicitly distinct."
        ]
      },
      "worked_example": {
        "fictional": true,
        "scenario": "Fictional Cedar’s repair pilot evolves over three months.",
        "slot_fills": {
          "title": "How the pilot became repeatable",
          "date": [
            "January — fictional",
            "February — fictional",
            "March — fictional"
          ],
          "headline": [
            "Intake queues expose a handoff problem",
            "Volunteers rehearse a common checklist",
            "A practice session identifies confusing wording",
            "The team records a revised method"
          ],
          "text": [
            "Visitors waited after reaching a repair table while volunteers repeated intake questions.",
            "Cedar proposed a shared safety checklist and rehearsed it with new volunteers.",
            "A fictional March practice session identified confusing wording in two intake questions.",
            "The team rewrote those questions and recorded what changed.",
            "This fictional sequence does not establish that the revision reduced waiting; a separate comparison would be needed."
          ]
        },
        "reasoning": "Dates anchor separate events; prose explains their relevance without converting “after” into “because of”.",
        "qualification": "Fictional teaching example. Replace invented details with authorised content and keep any source, scope, status or uncertainty that affects interpretation."
      },
      "narrative_fit": {
        "before": "Name the current situation or question.",
        "after": "Assess the evidence for a proposed mechanism or decision.",
        "good_uses": [
          "A documented sequence of decisions or events."
        ],
        "poor_fits": [
          "An undated process.",
          "A forecast presented as completed history."
        ]
      },
      "evidence": {
        "observations": [
          "Viewed source: dates form a vertical rail, with multiple titled events and descriptive paragraphs within one date.",
          "Current markup has three dates and four events; only the first date/headline/text are individually annotated.",
          "Corrected matching uses explicit selectors for all three date groups and four event headings, plus five paragraphs when visible; the compact state excludes hidden paragraphs."
        ],
        "interpretations": [
          "Dated events explain how a situation developed, with enough prose to distinguish occurrence from interpretation. This is an interpretation of the inspected composition, not a verified claim of author intent."
        ],
        "not_verified": [
          "Original author intent, historical claims, persuasion and archive-wide frequency have not been independently verified."
        ],
        "references": [
          "02_product/spreads/S89-dated-timeline/source.webp",
          "02_product/spreads-semantics-2026-10-13/dist/S89-dated-timeline/spread.html",
          "02_product/spreads-semantics-2026-10-13/dist/S89-dated-timeline/spread.json",
          "https://reuters-graphics.github.io/graphics-components/iframe.html?id=components-text-elements-simpletimeline--multiple-events&viewMode=story"
        ]
      },
      "review": {
        "status": "reviewed",
        "basis": "Viewed the retained base source capture and inspected current HTML and matching slots; reviewed the fictional adaptation at layout-contract level. Rechecked integrated matching on 2026-10-13: required roles, example fills and repeated-item counts agree. Previously provisional because repeated events were represented by the first annotated entry. Explicit selectors and counts now cover three dates, four event headings and five paragraphs; compact correctly omits hidden paragraphs. Historical issue details remain in contract-issues-reading.json. This review does not establish original author intent or verify playback."
      },
      "variation_relationship": "base"
    }
  },
  "options": [
    {
      "id": "rows",
      "what": "No rail: hairline-separated rows of date, bold title and description across the full width (WebSlides dated rows)"
    },
    {
      "id": "compact",
      "what": "Date kickers and headlines only, like a contents list (Reuters BlogTOC)"
    }
  ],
  "also_seen_in": [],
  "source": {
    "ref": "Reuters SimpleTimeline",
    "url": "https://reuters-graphics.github.io/graphics-components/iframe.html?id=components-text-elements-simpletimeline--multiple-events&viewMode=story"
  }
}