Your CreaPodz workspace

Creature research, with a clear next step.

Review the specimens you have, follow the intended game journey, and keep your saved work protected. This is a research preview; chapter progression and live combat are not yet implemented here.

Manage creatures

Original exploration craft

1active combat Pod

2holding Podlets

1shield bubble

Holding Podlets are physical custody, not additional battle positions.

—recorded identities

—recorded eggs

—saved research sources

Suggested next step · based on local research data

Checking this browser's records

No game quest status is inferred from research saves.

Understand your creatures

Inspect a deduplicated, read-only collection, or go to the Workshop for equipment, Expertise, breeding and eggs.

Know what unlocks next

See the intended exploration-to-capture-to-development path, with unavailable gameplay clearly identified.

Collection · one source-qualified identity per individual

Your creatures

The list below reads the existing research records without altering them. A captured individual's quarantined Workshop alias is not a second creature.

Manage / equip in Workshop Breeding Eggs and incubation

M59 · Single identity projection

Refined specimen registry

This registry counts a correctly linked M58 capture and Workshop quarantine alias as one research individual. Its original records remain unchanged. The independent lifecycle fixture is never silently equated with an M57 capture. Eggs are indexed separately for specimen ancestry.

Find by ID, name, Core or parent Source

Loading source registry…

Checking aliases for conflicts…

Lab	Individual	Known Core	Location	Recorded parents	Evidence
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.

For testing and development

Research tools

Prior prototypes and deterministic engine traces remain preserved for verification. They are not alternative player-facing combat or breeding systems.

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 and genuine genetic inheritance remain separate. M58 can persist captured engine-trial identities as quarantined Workshop research records; M59 coalesces their aliases for read-only inspection; these cannot breed, deploy or grant credits.

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

Archived duplicate experiments are not part of the primary activity routes.

Development & verification only

Preserved research instruments

These are isolated diagnostics, not additional production processes. Their fixture mechanics and separate saves remain intact for regression testing. Do not use a lab capture as a real-game capture or treat its biology as authoritative.

Lifecycle capture / breeding fixture M57 Python capture evidence Workshop battle practice Original Netlify export

New · Milestone 57

Real engine → in-combat capture → physical holding

We integrated a Python capture hook directly into the original Milestone 56 combat engine and ran 1,164 source regression tests. This is not yet playable live combat in your browser. Inspect two source-generated capture and shield-return transcripts without modifying either saved collection.

Review M57 engine capture evidence

Milestone 58 · Source-preserving identity transfer

Research capture intake

Import source-generated M57 capture and physical custody evidence. Inspect an individual before creating a persistent record. Only a specimen with a verified local housing receipt can enter the Workshop as an inert, non-breedable research record; unknown elements, anatomy, parents and inherited profiles stay unknown. This is not a real-game reward or an authenticated live capture.

Or choose an M57 evidence JSON file

No M57 evidence staged. Existing Workshop and Lifecycle saves have not been changed.

I reviewed the source-owner, captured identities and physical custody. I authorize adding selected records to this device's M58 research registry, and housed ones to Workshop quarantine.

Saved intake records

No records imported.

M58 writes are backed up before any Workshop or intake changes. Unselected source saves are untouched.

Confirm restoring the previously backed-up Workshop and M58 registry bytes

A research JSON can be modified externally; structural validation does not authenticate a player action. No imported record becomes battle-ready until the missing biological and game-authority evidence has been established.

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.

Research formation Role in full Delta

Select a creature whose Core has a verified research trace.