# Closer Question Guide Correction Summary

## Why this update was required

The writing documents and the active importer disagreed about production depth and file shape.

The old guide allowed human-readable depth strings such as `light`, `medium`, and `deep`. The active Room-backed importer expects an integer field, so string depth can be read as `0`.

The old workflow also did not clearly forbid a partial batch or patch manifest from replacing a production JSON filename.

## Correct production authority

Production packs now require:

```text
top-level category object
top-level questions array
category.id
category.display_name
category.description
category.access
category.icon_name
question.category_id
question.type
question.text
question.depth as integer 1/2/3
question.access
question.tags array
```

`sex` remains optional and nullable unless a documented feature specifically reads it.

## Work artifacts

The corrected guides explicitly classify these as non-production:

```text
partial batches
simple-pack batch JSON
patch manifests
validation reports
coverage maps
continuation notes
apply scripts
review summaries
```

They must not overwrite production filenames or live in importer-scanned production locations.

## Daily pack rule

`daily_fun_multiple_choice_v3.json` must always remain the complete 511-question Daily Single-Choice Weekday System.

A JSON document containing only changed IDs is a patch manifest. It must be applied to the complete 511-question source; the resulting complete pack is the file that ships.

## Catalog-wide rule

Every production file must pass individually, then the complete catalog must pass together.

The catalog gate rejects:

- duplicate IDs across files
- duplicate exact or normalized question text across files
- blocked cross-category near-duplicates
- unknown categories
- partial or patch artifacts under production filenames
- depth or other field coercion caused by schema mismatches

## Immediate file remediation implied by the corrected guide

### `rebuilding_trust.json`

Do not ship the 25-question Batch 1 artifact.

Rebuild or complete the production pack using:

- full `{ "category": ..., "questions": [...] }` shape
- required category object
- `category_id` on every question
- integer depth `1`, `2`, or `3`
- tags arrays
- the approved final count and access/type distribution

Keep the last complete production version in place until the full replacement passes validation.

### `daily_fun_multiple_choice_v3.json`

Restore the complete 511-question source.

Apply the 17-ID patch to that complete source.

Ship the complete validated 511-question result, not the patch manifest.

### Cross-file duplicate

Reword one instance of:

```text
Comfort first or solutions first?
```

Do not allow identical question text in both Emotional Intimacy and Stress. Give each version a category-specific angle, then rerun the complete catalog gate.

## Catalog count changes

Intentional 250-to-150 pack reductions are allowed under the 150-question cap.

Every completion report must still show:

```text
old pack count
new pack count
net catalog change
free/premium change
approval or product rationale
```