Skip to content

Review records

Every criterion execution creates one Review Record. Records are append-only: they cannot be edited or deleted after creation, enforced by the access control handler and by hook_entity_access().

Browse them at /admin/config/ai/content-review/records, or per entity at /<entity path>/ai-review/history.

The Review Records listing: source entity, record type, criterion, when and by whom, score, severity and status

What a record holds

Field Meaning
criterion_id, criterion_label Which criterion ran, and its label at the time of execution.
input_hash SHA-256 of the criterion's configuration, identifying the exact question that was asked.
triggered_by, triggered_by_uid How the run started (manual, workflow_event, scheduled, bulk) and who started it.
modality interactive, background or outside_in.
status pending, running, complete, skipped or failed.
score, severity, explanation The result. Score is 0 to 100. Severity is stored as info, warning or critical, and shown in the UI as Low, Medium and High.
error_message The raw detail for a failed run.
ai_provider, ai_model Which provider and model answered.
suggestions References to the Suggestion entities this run produced.
created, reviewed_at When the record was created, and when the AI answered.

Which entity or URL the record is about comes from its bundle. Internal records store entity_type, entity_id and entity_revision_id denormalised rather than as entity references, so a record survives the deletion of what it reviewed.

Statuses

A record is saved three times over a run: pending, then running, then its final status. Paused is shown in the UI for a stepped run whose browser stopped driving it, and it is presentational rather than a stored status: the record is still running and the persisted turns are still there to resume from.

Grades are derived, not stored

A record stores the score. Pass and warn are read from the criterion's current thresholds at render time:

  • No pass threshold configured, or no score: not graded.
  • Score at or above the pass threshold: pass.
  • Warn threshold set and score at or above it: warn.
  • Otherwise: fail.

A score equal to a threshold resolves to the higher grade. This keeps records immutable while letting a threshold change reinterpret existing results without re-running anything.

Record types

Review Records are bundled, and the bundles are plugins. Two ship with the module:

Bundle Reviews
Internal Any Drupal content entity.
External A remote source identified by a URL.

Rules pick their record type in the Reviews field. Entity type and subtype only apply to internal rules. See Review record type plugins to add your own.

Access

Viewing a record requires the View AI review records permission and view access to the underlying entity and revision. If a user loses access to the entity, they lose access to its records with it. The full cross-entity history view additionally requires View AI review records history.