---
title: "Reopen a credit-exposure review."
description: "A complete synthetic flow connecting counterevidence, options, scenarios, work records, and REVIEW_REQUIRED."
updated: "30 August 2026"
availability: "CONTRACT REVIEW · TEST_ONLY"
candidate_route: "/docs/polya/examples/credit-deterioration"
---

# Reopen a credit-exposure review.

A complete synthetic flow connecting counterevidence, options, scenarios, work records, and REVIEW_REQUIRED.

**CONTRACT REVIEW · TEST_ONLY:** Local credit-deterioration fixture evidence · no real company, customer data, investment judgment, or operational authority

## Inspect the DecisionCase review state.

Compare fixed input, structural checks, and result. There is no recommendation or approval control.

**EXAMPLE WORKBENCH:** TEST_ONLY

### Input

INPUT / CASE BOUNDARY

- **Question:** Should a new liquidity-deterioration signal reopen the credit-exposure review?
- **Case ID:** case.credit-001
- **Scope:** finance.credit.exposure.review
- **SignalBriefRef:** opaque / COUNTEREVIDENCE

### Checks

LINEAGE / OPTIONS / DISSENT

- **Reference:** status · digest · time verified
- **Options:** maintain · reduce · freeze new exposure
- **Dissent:** liquidity evidence incomplete
- **ReviewTrigger:** COUNTEREVIDENCE

### Result

RESULT / DIGEST-BOUND REF

- **Schema:** polya.decision-graph.v1
- **Version:** 1
- **Status:** REVIEW_REQUIRED
- **Authority:** NONE — assurance TEST_ONLY

> **Not created:** Recommendation · human approval · external task · RAIFFA permission — DecisionCaseRef is bound only to the validated snapshot digest.

## Fix the synthetic question and scope

The synthetic question is: “Should a new liquidity-deterioration signal reopen the current credit-exposure review?” Scope is `finance.credit.exposure.review`; participating roles are credit analyst, investment owner, and risk officer.

> **EXAMPLE_ONLY:** Names, values, dates, and references are fixed fixtures for contract explanation. They are not a real company, credit opinion, or investment recommendation.

## Trace counterevidence into review

1. **Receive an opaque SignalBriefRef** — Validate COUNTEREVIDENCE status, digest, and time without copying the source body into PÓLYA.
2. **Compare three options** — Connect synthetic maintain, reduce, and freeze-new-exposure options to assumptions and scenarios.
3. **Preserve dissent** — Keep a Dissent and EvidenceRequest stating that liquidity evidence remains incomplete.
4. **Return the case to REVIEW_REQUIRED** — Add a ReviewTrigger and new-version lineage without deleting the prior Decision.
5. **Create the current DecisionCaseRef** — Bind an opaque reference to the validated snapshot digest while authority remains NONE.

## Inspect the bounded result

- No automatic recommendation
- No human approval
- No external task assignment
- No RAIFFA action permission

**Abbreviated DecisionCase state**

```json
{
  "schema": "polya.decision-graph.v1",
  "id": "case.credit-001",
  "version": 1,
  "status": "REVIEW_REQUIRED",
  "scope": "finance.credit.exposure.review",
  "authority": "NONE",
  "assurance": "TEST_ONLY"
}
```

---

Published route: /docs/polya/examples/credit-deterioration