# H11.0-P4.5 — JCKH Deferred Readiness & Non-Blocking QA Policy

## Decision

JCKH / Kandar is classified as:

`DEFERRED_NOT_READY`

for the current migration/testing phases because its database is not yet at the
same readiness/parity level as NJCH and MNH.

## Blocking QA scope

- NJCH: READY / blocking QA.
- MNH: READY / blocking QA.
- JCKH: DEFERRED_NOT_READY / non-blocking QA.

## Database update scope

JCKH remains in the database-update propagation scope.

Therefore future controlled database migrations/updates must still include:

- NJCH
- JCKH
- MNH

However JCKH business-data parity and live functional tests do not block phase
acceptance until its database readiness is formally approved.

## GMOV legacy status

The exact historical function remains:

`PARTIAL_DEFERRED_BRANCH`

It is not promoted to MATCHED while JCKH is deferred.

Current acceptance scope:

- NJCH + MNH.
- 12 months.
- Year + date-range modes.
- 48 exact value checks.
- `max_difference = 0`.
- Oracle writes: NONE.

Full 3-branch MATCHED closure will be re-opened only after JCKH becomes READY.