# Curation Method

## Candidate Record

The evaluated longlist contains **1,500 serious candidates**: core: 480; expansion-ready: 868; merged: 2; research-reserve: 140; deferred: 6; excluded: 4. Every record retains title, essence, proposed Class and Domains, Modes, provisional relationships, readiness, safety review, eight score dimensions, weighted score, rationale, date, and promotion gate. Rejected or merged ideas remain visible so the same decision can be audited instead of repeatedly rediscovered.

## Scoring

The explicit editorial rubric weights canonical fit 18%, distinctiveness 16%, evidentiary clarity 14%, cross-Domain reach 12%, symbolic depth 12%, gameplay utility 12%, safety readiness 10%, and visual legibility 6%. Every dimension carries a candidate-specific criterion note, and the weighted score is computed from those declared judgments rather than a hash or quota position. Scores organize review; they do not replace editorial judgment. A high total cannot override an unsafe health claim, a duplicated archetype, absent provenance, or copyrighted expression.

## Dispositions

- **Core:** complete content, safety, source context, visual direction, and graph requirements.
- **Expansion-ready:** independent function is clear; one focused evidence/graph/art pass remains.
- **Research-reserve:** promising, but sources, community review, mechanism, or differentiation is incomplete.
- **Merged:** terminology or presentation belongs inside an existing Tile.
- **Deferred:** preserve for specialist or community review without implying readiness.
- **Excluded:** self-sealing, unsafe, non-distinct, or irreducibly dependent on protected expression.

## Promotion Gate

Promotion requires stable ID, distinct essence/archetype/Gift/Shadow, concept-appropriate Modes, claim-level Evidence States, a real external context source, original-synthesis provenance, safety review, four typed neighbors across three families, a cross-Domain bridge, and a 96-pixel visual proof. Regenerate data deterministically, run schema and graph validation, compare coverage, and record the release checksum.
