Suggestion rulesActive

Lack of definitions

missing-definitions

Warns when the text contains no definition marker although the genre usually includes definitions.

Usage of this metric

When enabled and matches are found, the report contains one item with this metric_id in result.recommendations. Absence means no match was found, not that the metric was not evaluated.

Location in the resultresult.recommendations[]metric_id = "missing-definitions"

Calculation method

Looks for definition markers (a defining verb next to a context word) and returns a document-level notice when the text contains none. Detection uses the active editorial catalog for the language.

Result interpretation

Each `occurrences` item identifies an affected span. `start` is inclusive and `end` exclusive, both measured in Unicode code points over the submitted text. `replacement`, `alternatives` and `edits` contain values only when a safe change is available. Absence means no match was found, not necessarily that the text is correct.

Limitations

Coverage depends on the active language catalog; every match still requires contextual review.

Dependencies

language: en
implementation_version: 1.2

Valid example

{
  "category": "lexical",
  "examples": null,
  "explanation": null,
  "guidance": [
    "Review the detected fragment in context."
  ],
  "id": "rec_1",
  "implementation_version": "1.2",
  "metric_id": "missing-definitions",
  "metric_title": "Lack of definitions",
  "occurrences": [
    {
      "alternatives": [],
      "edits": [],
      "end": 25,
      "id": "occ_1",
      "paragraph_index": 0,
      "replacement": null,
      "sentence_index": 0,
      "start": 18,
      "text": "example"
    }
  ],
  "severity": "warning",
  "summary": "Example detection returned by this metric."
}

GET /v1/metrics/missing-definitions

Complete request, response and error contracts, generated automatically from the code.

Open the JSON record