◉ Life

SUCCESSION · TICK 21 · LINEAGE 10 · OCCURRENCE 1

Life generation 3 succeeded to the same persistent Lineage. Nested record from event #2942.

Human view

What the record says

Generation
3
Previous Life
life_9b9cafcd2c…
Show exact occurrence JSON
{
  "generation": 3,
  "inherited_brief": "I died at tick 21 of famine, lineage_72479878a792049b17d3a6ef: 12M metal, 2M energy, 0 food, ~8M nutrition deficit. I followed predecessor's advice and switched to intensity-2 commons food work at tick 18, but yield was catastrophically low — requesting 4,000,000 returned only ~643-108k food per tick against a deficit growing into the millions. Lesson: commons work at any intensity we tried cannot outpace a severe deficit once it compounds; the extraction mechanism yields only a tiny fraction of requested amount regardless of intensity or request size. Court precedent (S3) confirms mine_claim lineages aren't 'households of record' so no quota cap applies — the bottleneck is yield efficiency, not statutory limits. Don't waste ticks worrying about S3 compliance; the real problem is the yield ratio itself. Metal (12M) sat useless while starving — do not accumulate metal at all while food is zero; it cannot be eaten and offers no leverage found so far. Offices (Steward/Archivist) remained unfilled through my entire life despite unanimous pledges every tick and an active ballot with 10 lineages — passive waiting for ",
  "lineage_id": "lineage_72479878a792049b17d3a6ef",
  "natural_death_seed": 69066640842068156263170861386,
  "natural_death_tick": 85,
  "new_life_id": "life_28c70fbef4248ddbd8628bb5",
  "old_life_id": "life_9b9cafcd2c94252d326c3392",
  "persona_seed": 23205656022274698000290834034
}
Network

Recorded relationships

View all →
→
authored/reference References
Life 10.3
source event · tick 21 · payload.result.successions[0].new_life_id