Verified 20 Data Policy — All Monsters / All Recipes True Source

Public teaching true source for this wiki (content layer, 2026-08-07): the verified dataset of 20 base Fulus and 20 base essence recipes. Community base drafts that are not in that set are phantoms until multi-source re-verification with a client version string.

This page is the ops/content policy that other catalog pages implement. It does not replace the scannable list — use All Monsters / Complete Fulu List and All Fulus for the tables.

Coverage badge (what UI and copy should show)

Badge field	Value to display
Base Fulus coverage	20 / 20 verified
Base recipes coverage	20 / 20 verified (one essence trio per base output)
Family labels on verified rows	5 — Pyre, Aqua, Flora, Neutral, Hybrid
Essence inputs trusted for base trios	Fire / Water / Nature / Neutral
Client patch anchor	Public Steam notes through v0.2.3.3 (2026-04-13 on patch tracker)
Verification tags	`verified: true`, `source: official` on verified rows

If a page or widget cannot show 20 / 20, it must not imply a larger “complete” roster without labeling extras as unverified drafts.

Why this policy exists

Pressure	Evidence used (this pass)
Trust vs clean competitor lists	SERP competitors already ship complete base tables (ops note: e.g. “all 20 base families / complete recipe table” style lists)
GSC list intent	all monsters shows strong CTR when a clean list exists (action-card window: high CTR, position ≈ 5.1)
Merge inflation on this codebase	Unfiltered base+verified merge still yields 37 monsters and 39 recipes with 17 phantom monster IDs surviving (action card + local merge check on this worktree)
Official scale language	Game / marketing language around 20 unique Fulu families / base set — wiki teaches 20 base outputs under 5 verified family labels without inventing missing family names

Phantom drafts in calculators and DB UIs lose to cleaner external lists even when our verified tables are correct.

Merge math (content-visible fact, not a purge)

App data still merges community base JSON with verified overrides by id. Verified wins on collision, but base-only IDs remain.

Layer	Monsters	Recipes
Verified true source	20	20
Base community drafts (worktree check)	22 file rows (includes non-verified)	19 file rows
Merged public count if unfiltered	37	39
Phantom monster IDs still surviving in merge	17	—

Phantom monster names (do not teach as all-monsters canon)

These names appear in base draft data and are not in the verified 20. Full teaching blocklist is mirrored on All Fulus:

Aqualine, Kenis, Zephyros, Zephyrion, Terrak, Terradon, Voltix, Voltron, Glacius, Magmar, Steamix, Lumina, Umbra, Florix, Floragon, Crystix, Toxin.

Phantom essence / recipe patterns

Distrust as base teaching inputs when they appear only on unfiltered draft rows:

Air / Earth / Electric essence labels as standalone base trio inputs
Evolution / hybrid / legendary draft recipe IDs that output the phantom names above

Trusted base essence labels: Fire, Water, Nature, Neutral only.

Content true-source map

Intent	True-source content surface
All monsters / complete Fulu list	All Monsters + All Fulus
Family roll-up	Families index
All recipes teaching table	All Fulus recipes section + Recipe index
Interactive recipes UI	Breeding Calculator — prefer verified tags
Interactive monsters UI	Monster Database — eng still needs verified-default
Care / 养成	Pet Care — not a bestiary
Mid-game rarity	Empower guide

Writer rules (hard)

Lead with verified 20 on any all-monsters / all-recipes answer.
Never present phantom names as equal peers in the main table.
State coverage as 20 / 20 and attach the client version anchor when claiming completeness for the base set.
Separate care copy from catalog copy — all-monsters keywords stay off Pet Care.
Do not invent family names beyond the five verified labels.
When mentioning merge inflation, use the documented 37 / 39 / 17 research figures or re-measure — do not invent new counts.

Engineering handoff (outside `content/` — still required)

Content can document and demote phantoms. Content cannot delete src/lib/data/monsters.json draft rows or change React defaults.

Eng task	Desired end state
Base JSON purge or filter	Base only retains IDs present in verified, or UI defaults to verified-only
Calculator default	Verified-first / hide phantoms unless “show drafts” is explicit
`/monsters` title + H1	All Monsters / Complete Fulu List (or equivalent) + 20 / 20 badge + version string
Coverage UI	Always show verified coverage and client patch anchor

Until eng lands, content surfaces above remain the trustworthy public answer.

FAQ

Is verified the only data that exists in the repo?
No. Base drafts still exist and inflate merges. Verified is the only public teaching true source.

Can content ops finish the JSON purge?
No. Iron rule for this pass: only content/ is editable. Purge is eng.

What version should pages cite?
Public notes through v0.2.3.3 as the client research anchor on this snapshot, plus date 2026-08-07 on content lastVerified / dateModified fields.