Files
aevolution/docs/engineering/CELLULAR_PLAYTEST_TUNING.md

71 lines
4.3 KiB
Markdown
Raw Permalink Blame History

This file contains ambiguous Unicode characters
This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.
# Cellular playtest opening controls
The reproduction safety trial is recorded as `reproduction.safety_version = 1`
([ADR-0181](../adr/0181-cellular-reproduction-safety.md)). Its split share is the
controlled cell's share (800/1000); mutation offspring launch at 800 um/s; growth
preserves 60 seconds of the resulting body's full-demand fuel. Ordinary bud fees
return to the selected player cell. Missing safety keys preserve historical rules.
These declarations apply to future openings only, not an existing running region.
The complete prepared profile is
`deploy/kubernetes/region/dev/tuning/cellular-reproduction-safety.tuning`; it is not
mounted by the active overlay. Use it as `--revamp-tuning` only with a build that
supports safety revision 1 and a fresh opening. The currently mounted profile
remains compatible with the currently promoted image. Image/region promotion is
a separate operation; a Git push does not activate the gameplay trial.
These trial settings live in
`deploy/kubernetes/region/dev/tuning/cellular-revamp.tuning`. They are read by
`evo-world-clone provision --opening cellular-v10 --revamp-tuning FILE`; the owner
then retains its recorded rules. Editing the file does not retune an existing
region. Open a fresh disposable region for a changed trial. See [ADR-0180](../adr/0180-dev-starting-wildlife.md).
| Key | Current DEV value | Meaning |
| --- | --- | --- |
| `playtest.starting_wildlife_cells` | 32 | Initial random-genome cells; 0 disables; max 255 and below the organism cap. Omission defaults to 0 for older files. |
| `body.growth_per_tick_centi_mille` | 625 | 6.25 per thousand per tick at growth speed 100, up from 5: 25% faster when funded. |
| `reproduction.bud_fee_e_pj` | 250000 | Additional energy fee per bud action. |
| `reproduction.bud_fee_c_fg` | 100000 | Additional carbon fee. |
| `reproduction.bud_fee_n_fg` | 30000 | Additional nitrogen fee. |
| `reproduction.bud_fee_p_fg` | 10000 | Additional phosphorus fee. |
| `reproduction.bud_fee_o_fg` | 60000 | Additional other-matter fee. |
| `reproduction.bud_fee_scale_percent` | 100 | Percentage of the listed fee charged; 0 disables it. |
The fee controls already existed; this change activates and documents them and
corrects the displayed cost to include them. Offspring tissue and starting reserve
remain funded biological costs. Faster growth spends the same resources in less
time; insufficient nutrients can still hold it back.
The DEV manifest prepares world 100, region 14, with a new stable genesis commit
and `--playtest-wildlife-first-id 900000003584` below
`--life-allocator-start 1000000000000`. This declares a reserved fixture range;
operators must audit its uniqueness across the world's other retained regions.
Regions 1–13 remain stored. Counts other than 32 need a correspondingly audited
range and enough nursery stock. The fixture spends the nursery rather than
minting resources; player founders draw its remainder.
Each cell uses founder-6 capabilities and full growth, no damage or spare matter,
30 seconds of its own full demand as reserve energy, and a seeded genome with
75–125-point body, collection, burn, engulfment and movement indices. It has no
acquired modules, player account or fabricated ancestry. Randomness is stable
for world, region and identity. Normal autonomous wildlife control takes over.
Recovery and repeated provisioning retain the saved population, including deaths;
they do not top it up.
Bud uses the current expressed parent and inherited offspring plan, plus the fee;
internal-cell litter conservatively shows its largest possible charge. Hover a
grey Bud button to inspect every required/available channel. A resource-ready
button still submits an intention: growth, placement, regional capacity and
changes before execution can affect the authoritative outcome.
The region-14 configuration requires an image built from this change before
manual Argo sync. The currently pinned image is not claimed to support the new
opening flag. Build promotion, deployment, live playtesting and identity auditing
against production stores were not performed by these local checks. No World0
operation is involved.
Focused durable verification in a new private local PostgreSQL cluster:
```sh
bash tools/ci/postgres-check.sh --starting-wildlife-only "$PWD/build/playtest-postgres/evo-postgres-tests"
```