3.4 KiB
ADR-0160: Portable transfer of funded maturing wildlife
Status and scope
Accepted for the scoped M12 portable maturation-transfer prerequisite, 2026-10-19. Extends ADR-0144/0157/0159. No new biological rule, SQL schema, durable migration admission, automatic route, live upgrade or production enablement.
Decision
Allow exact no-tick transfer candidates between owner-7 cuts with equal rules 9, using the same complete group, eligibility, placement, history, identity, stock and boundary-flow checks as rules 8. Raw and population envelope 2 use the same biological operation. Preserve realized growth, body, reserve, damage, mutation state, coordinates and every other life field exactly. Neither endpoint matures at the transfer cut. Subsequent destination ticks apply their retained rules and environment; source nonresident history never owns or grows a second copy.
Reject mixed rules 8/9 before deriving either result, even at otherwise equal cuts. The existing format-upgrade API remains rules 8 only; moving a rules-9 owner does not repeat an upgrade or create another source of biological rules.
Add portable migration trace 2, magic AEVMIG02, version 2. Keep the same bounded
layout, request/endpoint/member/inventory fields, reserved zero, checksum and size
limit as trace 1. Version 2 means equal rules-9/owner-7 inputs; version 1 retains
equal rules-8/owner-7 inputs and its exact bytes. Population inputs use envelope 2.
Record selects the version from the supported predecessor rule. Replay requires
that exact version/rule pair in addition to the trusted request and complete
rederived candidates. Unknown versions, mixed magic/version and cross-rule trace
replay fail. No checksum or embedded request grants authority.
The durable adapter remains bundle 10/trace 1 only, including explicit portable trace-version refusal. A later gate must admit bundle 11/trace 2 through source freeze, destination staging, atomic paired publication and complete recovery, including registered pending-handoff census evidence. Portable support alone must not silently expand those SQL or activation contracts.
Alternatives, costs and qualification
Reusing trace 1 would change a retained rule contract. Copying or re-deriving adult bodies would change actual biomass. Treating transfer as a tick would progress frozen life. A separate migration algorithm risks representation drift. Retain one operation, require equal biological rules and distinguish replay evidence. The additional version adds a small dispatch branch and a second qualification matrix without increasing allocation bounds or dependencies.
Require real player-origin buds, growth before/after transfer, exact life equality at the cut, raw/cohort equivalence, source nonresident/census exclusion, combined channel conservation, repeated return trips, collision/capacity/eligibility refusal, canonical codec attacks, old bytes, cross-rule refusal and independent process replay/continuation. Run Release, ASan/UBSan, analysis and affected private durable regressions. This does not qualify sustainable generations, linked geometry/environmental budgets, cross-host partitions, actual days or M12 product readiness.
ADR-0161/schema 54 subsequently admits exact bundle-11/trace-2 pairs through the existing durable workflow and complete recovery/census verification. It preserves the trace-version and equal-rule contracts above; no automatic route is added.