Breed. Build. Battle.

Incubation controls

Fixture: an egg becomes 100% ready after 3 actions; it stays ready indefinitely until manually hatched. This example gives final-stage environment a *visible color-expression* effect only, not an invented combat bonus or permanent genotype edit.

Physical capacity

This bench simulates housing capacity and egg holding capacity independently. Incubator transfers, remote planetary incubation, and egg freight are outside scope.

Inspect a specimen

Local trade fixture

Transfer the selected creature to simulated Collector B. Its genetic Core, Tier, achieved Core Expertise grade, ancestry, and history travel with it; only incomplete within-grade Core progress is lost. Equippable Stones are removed first and stay in the previous owner's inventory. This is a local fixture, not a live marketplace.

Attribute Stones — independent inventory

Each Stone has a stable ID, owner, source metadata, Expertise, and optional equipped position. A fully documented donor-derived stone carries fixed targeting plus Attack/Buff/Debuff modifiers. Older imported stones retain unknown properties rather than receiving invented ones. Install one in each outer slot without changing the creature's inherited Core or genetic positional profile. The installation costs and compatibility rules are not yet modeled.

Find recorded individuals by their actual observed identity, origin, elements, inherited Core, ancestry, or acquired Stones. The Atlas does not predict breeding outcomes or grant discovery credit.

A missing value is shown as not recorded. Natural secondary elements describe appearance, not additional matchup advantages. Export is a factual filtered extract, not a complete save backup.

Side-by-side biological records, current Power Delta components, and recorded family connections. A difference is not a strength rating, and no pairing outcome or genetic probability is predicted.

Choose two different recorded specimens.

Recorded parents and grandparents reflect available IDs only; missing records cannot prove absence of kinship. Acquired Attribute Stones and their Expertise are not inherited genes. Secondary elements remain appearance-only. All numeric fixture values are provisional.

Recorded specimens

Actual collection credit

Founders have personal wild-capture credit. Player-hatched offspring receive personal breeding credit. Transfer alone does not award credit to a buyer, and past credit is never removed.

Four-part Power Delta

The inherited Core is always the center component. Each outer position holds a separately equipped Stone; only the Stone for the current combat role activates alongside the Core. Previewing a role does not change equipment.

Fire Core transformation illustration

Hypothetical Scorch Core — these named combinations demonstrate the intended architecture, not a Core swap on an owned creature or finalized damage calculations.

All 57 concepts are approved. Their definitions do not authorize custom recombination of an acquired stone’s fixed properties. The full numeric balance remains TBD.

Source: Power Delta Canon v1.1, 2026-10-28. Names and descriptions are canon concepts; examples and numeric settings in this lab remain fixtures.

Three-creature combat Power Delta

Assign three distinct owned creatures. Each uses its current role's Stone. The normal schedule is Debuff → Buff → Attack; actual combat, timing, status, and enemy calculations are outside this lab.

Rotation preview is a nonpersistent demonstration, not a finished combat engine. It does not change creature genetics, Stone equipment, or records.

Cost demonstration — fixture only

When a Stone is equipped: effective Core cost + effective Stone cost. For illustration only, the bench begins with 8 and 3 mana and subtracts one per respective Expertise grade (minimum 1). These coefficients are not canonical. Core Expertise never discounts Stone cost and vice versa. Empty-slot costs/effects are not calculated.

Inspect one Core + the stone’s fixed targeting + one modifier selected by position. Example donor stones are fixed, authored demonstration records—no actual creature was consumed. This is not a stone-crafting interface or a full combat engine.

What this validates

1. Distinct immutable IDs and documented parent/grandparent ancestry.
2. Breeding requires the same owner and permanent home base.
3. Separate eggs with ordered incubation histories.
4. Ready eggs do not hatch automatically.
5. Hatch requires available physical housing.
6. Each offspring expresses exactly one Core. Its source is traceable to a parent or eligible documented ancestor.
7. Parental Core matches are prioritized; when neither matches, grandparent Cores can participate (test-only weights).
8. Installed learned Stones and inherited positional genetic profiles are separate fields; Stone installation does not modify the inherited field.
9. Newborns have empty learned Stone slots and a separately unresolved genetic positional profile; inherited Stone abilities are not assumed.
10. Creature trading preserves Core Tier and achieved Core Expertise grade while losing only within-grade progress; external equipped Stones stay with their owner. Individual Stone trade resets that Stone's Expertise.
11. Accomplishment credit comes from personal collection or breeding, not importing.
12. A hatched offspring can breed again with an unrelated founder in a second generation.

Experimental Core weighting — not canon

For each potential offspring, choose a dominant element from the actual parental elemental components (dominant component test weight 3, secondary component 1). With exactly one matching parental Core, use 9:1 baseline source weights before Expertise adjustment. With both matching, weight both by Expertise. With neither matching, include each recorded ancestor's actual expressed Core, with a decreasing depth factor. Every candidate's weight is multiplied by (1 + 0.15 × its Core Expertise). These coefficients are research fixtures, not approved final genetics. Core source and candidates are revealed on the specimen record after hatch, never as a breeding prediction.

Positional genetics — evidence boundary

Supported: one central inherited Core, three learned outer Stone positions, and a later secondary summary of inherited positional genetic profiles as packages with occasional ancestry-constrained recombination.

Not yet supported: the actual genetic profile values, which slot an inherited profile makes compatible, whether it grants an aptitude, or an exact recombination probability. The bench stores parent-profile provenance and explicitly marks resulting profiles not determined. It never treats installed parent Stones as the offspring's inherited profile.

Known exclusions

True inheritance probability formulas (including Expertise weighting and ancestor depth), exact inherited positional profile compatibility/recombination (status stored but outcome not calculated), Cold Core investment pricing, hidden brood ceilings, broader kinship cutoffs, incubation heritability, breeding/maturity timers, learned cross-element Core interactions, acquisition economies and costs, role compatibility, and full combat resolution. These must not be inferred from the fixture.

v0.7 canon integration

All 57 canonical modifiers are browsable. Three explicitly simulated donor-derived stone fixtures encode fixed targeting + Attack/Buff/Debuff modifiers. The ability lab demonstrates magnitude splitting, total periodic potency distribution, sequential stop-on-first-success binary chances, immunity/no redistribution, and position-anchored Poison Location. v0.9 expands the isolated training-only combat resolver with predefined donor profiles, more effect fixtures, and active targeting feedback; this is not a finalized real combat/economy engine. Neither donor extraction nor genuine encounter rewards are implemented.

Local session safety & recovery

This test bench keeps your collection in this browser and site address. A new domain has separate storage. Export a JSON file before moving or deploying to another address. No session file is sent to a server.

If a saved file cannot be loaded, this app will not silently overwrite it. Review an import or restore a valid backup; explicit replacement first preserves the unreadable original separately.