RecensaRecensa home
Recensa

Methodology

How Recensa runs three independent reviewers on Claude, GPT, and Gemini in parallel—author intent and voice, skeptical claims and citations, structure and consistency—reconciled by an arbiter into an issue ledger, with additional reconciliation passes when configured for reviewer agreement. Written for technical readers evaluating document assurance workflows.

Last updated 2026-05-14

Pipeline

Methodology map

How to use

  1. 01

    Three reviewers

    Claude, GPT, Gemini—parallel structured findings

  2. 02

    Arbiter reconcile

    Merge, deduplicate, label disagreement

  3. 03

    Label disagreement

    Reviewer splits stay visible

  4. 04

    Generate issue ledger

    Prioritized backlog you can disposition

  5. 05

    Produce Proof Report

    Export-oriented summary for sign-off

  6. 06

    You keep final control

    You decide what ships, signs, or files

Technical detail

How the pipeline works

Structured review pathFrom reviewer output to a disposition-ready record.

Each Document Check runs three independent reviewers in parallel on Claude, GPT, and Gemini, assigned to distinct review roles—author intent and voice, skeptical claims and citations, structure and consistency. Each returns structured findings—not free-form chat. An arbiter reconciles their output; Recensa deduplicates similar issues, groups material conflicts, and decides when a deeper debate step is warranted versus when the issue ledger should be synthesized from what reviewers already agree on.

Reviewer agreementAgreement and conflict are both visible in the ledger.

When reviewers align, findings merge cleanly. When they diverge, the disagreement is labeled so your team can reconcile—not buried behind a single fluent answer.

When additional cycles runTargeted passes with clear stop reasons.

When enabled, additional reviewer cycles focus on targeted sections and refresh reconciliation—with stop reasons such as incomplete reviewer quorum, plan limits, or thresholds met before Apply Fixes.

Additional reconciliation passesReviewer agreement when configured—narrows disagreement, not judgment.

When reviewers disagree, the system can run additional reconciliation passes (when configured) to narrow competing outputs into a clearer issue list—reviewer agreement you can act on. It narrows disagreement; it does not replace your judgment on what still matters.

Partial completion and limitsHonest status when a full pass is not possible.

When a provider is unavailable or limits apply, Recensa labels partial status instead of implying a complete review. Your team should treat partial runs as incomplete evidence, not as sign-off.

Your verificationSoftware assists review; accountability stays with you.

Recensa helps surface candidates for attention. You verify facts, citations, regulated language, and final send-ready packages—especially before signature, filing, delivery, or submission.

Run a Document Check

See structured findings, disagreement labels, and Proof Report outputs on a finished file.

Run a Document Check