PÓLYAGuides

Guide 04 · REVIEW TRIGGER

CONTRACT REVIEW · TEST_ONLYReview-candidate contract and local fixture evidence only · no distributed SDK, operational API, publisher parity, or decision authority

Reopen a prior decision when evidence changes.

Record counterevidence, expiry, refuted assumptions, and manual review without overwriting the prior decision.

01

v1 distinguishes four review triggers

  • COUNTEREVIDENCE — new material conflicts with the current path
  • REFERENCE_STALE — an external reference expired
  • ASSUMPTION_REFUTED — a material assumption was contradicted
  • MANUAL — the accountable human explicitly requests review
02

DECIDED and CLOSED can return to REVIEW_REQUIRED

Do not delete a prior decision or assume it remains current. Bind the ReviewTrigger to its source node and time, then transition the case to REVIEW_REQUIRED.

  1. 01
    Verify the new reference

    Check schema, tenant, scope, lifetime, and publisher binding.

  2. 02
    Find affected nodes

    Connect the assumption, option, Scenario, or Decision that is now in question.

  3. 03
    Open a new version

    Preserve the prior snapshot while updating version and lineage.

  4. 04
    Require human review

    Revisit open questions, dissent, and conditions without automatic reselection.

03

Review completion is not RAIFFA eligibility

A reorganized PÓLYA case does not grant approval or permission to act. RAIFFA requires a separate EligibilityGateRef bound to the current DecisionCaseRef, actor, and scope.