CreaPodzDevelopment workspace · v0.6
Local-first research

Recovering the complete project

Breed. Build. Battle.
One workspace, preserved systems.

The original creature workshop is back. The newer lifecycle prototype and verified Power Delta replay experiments remain available alongside it, without overwriting either application's rules or saved creatures.

Two independent research applications. Their data is not automatically synchronized. Existing Netlify saves do not automatically travel to Cloudflare.

Main foundation · recovered v0.340

Creature workshop

Breeding, ancestry, development, incubation, Ability Stones, Expertise, collection records, and experimental Power Delta combat management.

Full restored browser interface · independent browser session
Launch workshop
Lifecycle contracts · v0.3

Capture & lifecycle

In-combat capture fixture, finite Podlets, caldera unloading, incubation, hatching, and eight deterministic battle replays from the recovered Python engine.

Research-only fixture · independent browser session
Launch lifecycle lab
Historical deployment

Original Netlify site

Open the previous v0.100 browser app to export an existing collection. Import that JSON into the restored workshop using its review-first importer.

Existing Netlify session is preserved on its original origin
Open older site

Safety first

Saved research sessions

These are two different data formats. This overview only reads their counts; it never writes to them. Each app retains its own export/import controls.

Creature workshop

Checking…

Capture & lifecycle

Checking…
Moving from Netlify? On the old site, download your current session JSON. Then open Creature workshop, go to Records & data, choose the file for review, and explicitly select Import reviewed session. Do not import the lifecycle save into the workshop, or vice versa.

Shared evidence registry · v0.5

Cross-lab specimen index

This registry maps each saved specimen to a source-qualified identity and preserves recorded ancestry, Core, Stone and custody evidence. It does not equate unrelated test creatures, invent genetic attributes, or mutate either save. Eggs are indexed separately for specimen ancestry.

Loading source registry…

LabIndividualKnown CoreLocationRecorded parentsEvidence
No Cloudflare sessions found yet.

One specimen · every recorded field

Select a specimen

Source-qualified identity, physical custody where known, inherited Core, parent records, eggs, Stone equipment, and original raw record. Unknown attributes remain unknown.

A dossier is a diagnostic record, not an importable gameplay save.

Milestone 56 · Core reference replay

The creature's recorded Core identity only selects a replay generated by the authentic historical Python engine. Research battle stats, enemies and support creatures are fixed fixtures—not this individual’s genetics, Stone loadout, rank, custody or real combat outcome.

Select a creature whose Core has a verified research trace.

Save continuity · explicit restoration only

Combined research archive

Export both saved laboratories in one lossless JSON archive. Import first stages a review; only the sources you select are restored. No biological fields are translated and nothing is silently synchronized.

No archive staged.

The restore preview validates source structure and custody invariants before writing. Local browser storage is still device-specific; download independent archives periodically.

Source boundaries

What's actually integrated?

RecoveredFull browser workshop code, tested loading and mobile layout.
Retainedv0.3 lifecycle capture fixture and authentic Python-engine precomputed replays.
Still separateFull live Python combat in the browser, genuine genetic probability model, and workshop-save creature minting. The M57 Python capture/custody integration is independently tested and shown as a research replay, not connected to either browser save.

No historical creature identity or game canon is silently modified. Numerical fixture mechanics remain experimental.