Semantic HTML.
Compare what tools preserve.

Values must match exactly in the same row. An XML caption is not a column header; a Markdown table does not prove the input’s HTML semantics. Test scope.

<table><caption>Synthetic measurements</caption><thead><tr><th class="case-cell" scope="col">Indicator</th><th class="case-cell" scope="col">Unit</th><th class="case-cell" scope="col">Period</th><th class="case-cell" scope="col">Value</th></tr></thead><tbody><tr><th class="case-cell" scope="row">Response time</th><td class="case-cell">seconds</td><td class="case-cell">May 2026</td><td class="case-cell">1.8</td></tr></tbody></table>

…
client.

## Synthetic measurements

Synthetic measurements

| Indicator | Unit | Period | Value |
| --- | --- | --- | --- |
| Response time | seconds | May 2026 | 1.8 |

The conclusion must be read with its unit, period, scope and caveat. Finding a word in an output is not enough to prove that the relationship was preserved.

Offline synthetic fixture · v1.2.0

{
  "status": "ok",
  "tool_class": "markdown_converter",
  "format": "markdown",
  "table_structure": "markdown_layout",
  "expected_data_row": "exact_values_in_order",
  "column_header_relation": "markdown_header_row",
  "row_header_relation": "not_encoded_in_markdown",
  "column_labels": [
    "Indicator",
    "Unit",
    "Period",
    "Value"
  ],
  "data_values": [
    "Response time",
    "seconds",
    "May 2026",
    "1.8"
  ],
  "evidence": {
    "header_row": "| Indicator | Unit | Period | Value |\n| --- | --- | --- | --- |",
    "data_row": "| Response time | seconds | May 2026 | 1.8 |",
    "table_excerpt": "| Indicator | Unit | Period | Value |\n| --- | --- | --- | --- |\n| Response time | seconds | May 2026 | 1.8 |"
  },
  "output_field": "additional_extractors.markdownify.markdown",
  "output_sha256": "b89ed68e1940ec52ddc6c2ca9f80ec35d1b57d7cde93df26244dd029a4fcff13",
  "source_column_headers_explicit": true
}

Offline protocol for preserving relationships


Edikka · semantic HTML extraction protocol · v1.2.0

# Offline protocol for preserving relationships

This synthetic document compares two markups while text, order, classes and surroundings remain identical. The data are fictional and describe neither Edikka nor a client.

## Synthetic measurements

Synthetic measurements

| Indicator | Unit | Period | Value |
| --- | --- | --- | --- |
| Response time | seconds | May 2026 | 1.8 |

The conclusion must be read with its unit, period, scope and caveat. Finding a word in an output is not enough to prove that the relationship was preserved.

Offline synthetic fixture · v1.2.0

{
  "version": "1.2.2",
  "configuration": "No configuration field in this output; consult the archived runner."
}

<table><caption>Synthetic measurements</caption><thead><tr><td class="case-cell">Indicator</td><td class="case-cell">Unit</td><td class="case-cell">Period</td><td class="case-cell">Value</td></tr></thead><tbody><tr><td class="case-cell">Response time</td><td class="case-cell">seconds</td><td class="case-cell">May 2026</td><td class="case-cell">1.8</td></tr></tbody></table>

…
client.

## Synthetic measurements

Synthetic measurements

| Indicator | Unit | Period | Value |
| --- | --- | --- | --- |
| Response time | seconds | May 2026 | 1.8 |

The conclusion must be read with its unit, period, scope and caveat. Finding a word in an output is not enough to prove that the relationship was preserved.

Offline synthetic fixture · v1.2.0

{
  "status": "ok",
  "tool_class": "markdown_converter",
  "format": "markdown",
  "table_structure": "markdown_layout",
  "expected_data_row": "exact_values_in_order",
  "column_header_relation": "markdown_header_row",
  "row_header_relation": "not_encoded_in_markdown",
  "column_labels": [
    "Indicator",
    "Unit",
    "Period",
    "Value"
  ],
  "data_values": [
    "Response time",
    "seconds",
    "May 2026",
    "1.8"
  ],
  "evidence": {
    "header_row": "| Indicator | Unit | Period | Value |\n| --- | --- | --- | --- |",
    "data_row": "| Response time | seconds | May 2026 | 1.8 |",
    "table_excerpt": "| Indicator | Unit | Period | Value |\n| --- | --- | --- | --- |\n| Response time | seconds | May 2026 | 1.8 |"
  },
  "output_field": "additional_extractors.markdownify.markdown",
  "output_sha256": "b89ed68e1940ec52ddc6c2ca9f80ec35d1b57d7cde93df26244dd029a4fcff13",
  "source_column_headers_explicit": false
}

Offline protocol for preserving relationships


Edikka · semantic HTML extraction protocol · v1.2.0

# Offline protocol for preserving relationships

This synthetic document compares two markups while text, order, classes and surroundings remain identical. The data are fictional and describe neither Edikka nor a client.

## Synthetic measurements

Synthetic measurements

| Indicator | Unit | Period | Value |
| --- | --- | --- | --- |
| Response time | seconds | May 2026 | 1.8 |

The conclusion must be read with its unit, period, scope and caveat. Finding a word in an output is not enough to prove that the relationship was preserved.

Offline synthetic fixture · v1.2.0

{
  "version": "1.2.2",
  "configuration": "No configuration field in this output; consult the archived runner."
}

Identical text and isolated intervention within this pair, according to the protocol witnesses. Translations are not independent observations. View pair witnesses.