Mediterranean Species Expansion Without Making Things Up

Adding a fish species to an app sounds easy.

Add a name. Add a picture. Add a few facts. Let people search for it.

For a fishing forecast, that is not enough.

If the species affects predictions, the app needs defensible traits: temperature range, depth range, activity pattern, spawning season, habitat, regional presence, salinity context, and whether the evidence is strong enough to score behavior.

That is why Gilli's Mediterranean expansion starts as a research queue, not a runtime switch.

Taxonomy Comes First

Common names are messy.

One fish can have several local names. One common name can point to different species depending on region. Some names are synonyms, some are outdated, and some are plain confusing.

For marine species, taxonomy needs an authority layer before it becomes app data. Scientific names and accepted species status should be checked before aliases are exposed to users.

That prevents the app from teaching confusion.

Encyclopedia Is Safer Than Scoring

Not every useful species entry should immediately drive predictions.

An encyclopedia profile can safely explain identification, habitat, distribution, diet, seasonality, and conservation cautions when the sources are adequate. A scoring profile needs more: thresholds and behavioral assumptions that influence forecasts.

Those are different confidence levels.

Gilli's expansion workflow keeps that separation. A species can be queued for content before it is trusted for prediction.

Some Species Are High-Risk

Mediterranean sport species are not all equal from a product perspective.

Gilthead seabream, little tunny, bluefish, white seabream, common pandora, and sand steenbras are useful recreational targets. Atlantic bluefin tuna is highly relevant but carries conservation, regulation, movement, and scoring risks. Groupers can be important for identification and context, but conservation rules and local protections matter.

The app should not flatten those differences.

Species with legal or conservation sensitivity need more cautious language and stronger source handling.

Image Generation Is Not the First Step

Field-guide art is valuable, but it should not lead the workflow.

If images are generated before taxonomy and species IDs are stable, the asset system can drift. The safer order is research, verify, promote, then generate or attach artwork with metadata.

Pretty assets do not fix uncertain biology.

What Good Expansion Looks Like

A good species expansion has:

• accepted scientific name
• stable app ID
• known aliases
• source-backed regional presence
• defensible depth and temperature context
• clear uncertainty flags
• conservation and regulation cautions where needed
• a decision on encyclopedia-only versus forecast-ready

That sounds slower than just adding fish.

It is also how the app stays trustworthy as coverage expands.