docs: propose M11.2 funded lives and atomic control contract
Foundation / checks (checks) (push) Successful in 5s
Foundation / checks (deploy) (push) Successful in 5s
Foundation / checks (ecs) (push) Successful in 4s
Foundation / checks (network) (push) Successful in 4s
Foundation / checks (postgres) (push) Successful in 5s
Foundation / checks (tsan) (push) Successful in 4s
Foundation / checks (client) (push) Successful in 47s
Foundation / postgres-tools (push) Successful in 4s
Foundation / server-image (push) Successful in 4s
Foundation / image (push) Successful in 4s

This commit is contained in:
dingo
2026-10-09 18:06:23 -04:00
parent 93e1ab08ae
commit 7ee1c68a82
5 changed files with 243 additions and 1 deletions
+65
View File
@@ -0,0 +1,65 @@
# M11.2: Primitive lives and persistent control
2026-10-09. Server-side continuation of M11.1 at `93e1ab0`.
[ADR-0100](../adr/0100-primitive-lives-and-persistent-control.md) is proposed.
This plan does not close 11.2 or settle unaccepted game rules.
## Contract review
Reviewed PROJECT_VISION, ENGINEERING_CONSTITUTION, SYSTEM_OVERVIEW,
SIMULATION_ARCHITECTURE, PERSISTENCE_ARCHITECTURE, REGION_DURABILITY,
REPRODUCTION_MODEL, ENERGY_MODEL and ADRs 0062, 0091, 0092, 0098 and 0099.
Inspected founder, development/metabolism, lineage/archive, host, checkpoint,
batch and account-control headers and lineage-region/account-control tests.
`closure_is_required` in lineage_region_tests correctly rejects an extra living
organism outside the two fixture bindings. Migration 0011 / ADR-0092 permits
duplicate no-effect publications; biological effects need the losing checkpoint
rejected in full. ADR-0100 proposes explicit contract replacements for gameplay.
ADR-0099's full-grown founder analysis is an assumption, not funded creation.
## Delivery segments
Validate each segment, record evidence/limits in VALIDATION.md, then commit and
push its scoped changes. Gate completion needs all applicable rows; library
tests alone are not a durability proof.
| Segment | Modules | Acceptance |
|---|---|---|
| 11.2a: contract and funded creation | Biology budget helpers if needed; server lifecycle; accounting callers; docs/tests | Settle funding, growth/reserve, placement and ADR-0100; equal old/new-account starts; atomic source/body/reserve/heat/provenance; insufficient channels, allocation, placement and overflow leave state unchanged |
| 11.2b: recoverable cellular state | Cellular state owner; codecs; persistence profile; lineage closure | New profile/history declaration; exact timers/reservations/retries; hostile bounds/versions/bindings refused; old profile goldens unchanged; no synthetic actors adopted as wildlife |
| 11.2c: durable ownership | Migration/adapters; account control; publication; host | Real PostgreSQL concurrent spawn/takeover, stale generations/leases, exact/changed retries; one nonterminal life across regions; losing candidate never publishes inventory; uncertain commit reconciliation; no runtime-role bypass |
| 11.2d: server integration | Session/host; versioned protocol; headless probe; process tests | Explicit spawn; reconnect to existing life; route to owner; no marker as organism; no offline progress; kills before/after transaction and final answer; same result after restart; network callers/codecs updated |
11.3-11.7 add the biological action loop and complete death/logout behavior.
This plan adds no renderer, UI, deployment or dependency.
## Fault and equivalence matrix
- New and historical accounts get identical biological starts for identical rule
and habitat inputs; historical identities may differ.
- Competing requests in one/two regions publish at most one nonterminal life.
Different accounts cannot overdraw the same finite source.
- Exact retry resolves once; changed content conflicts; retry of an old successful
spawn after its death returns the old result, never a new life.
- Failed allocation/funding/placement spends nothing and publishes no ancestry.
Allocation gaps are allowed; identity reuse is not.
- Kill before upload, before transaction, after commit and after final answer.
Recover only the committed cut and exact result.
- Race refresh/takeover with publication; stale control cannot publish a body or
replace life ownership.
- Missing body/archive/source debit/provenance/binding prevents readiness.
- Timers/reserves remain exact across restart/offline intervals; terminal history
remains terminal, never resurrected by recreating a session.
- Run under NDEBUG, verify channel conservation and canonical round trips.
## Validation lanes
Use README commands/presets: Windows debug/release and affected network/QUIC;
Linux debug/release, ASan+UBSan, clang-tidy and format-check; real PostgreSQL
migration/ownership and process-kill checks when those segments exist. Run network
presets whenever a replicated type changes. Record unavailable environments.
Local checks do not close ADR-0097's reference-worker qualification.
This initial review changes documentation only. No spawn, migration, provisioning
or biological implementation has been performed.
+15
View File
@@ -5462,3 +5462,18 @@ Executed:
- WSL `network-clang` 65/65 and `quic-linux` 68/68.
- clang-tidy 19: clean.
- Windows `debug` 61/61, `quic` 5/5, `client-network` 15/15.
## 2026-10-09 — M11.2 contract review (documentation only)
Proposed ADR-0100 and M11_2_DELIVERY_PLAN document two incompatible reuse paths:
the two-actor checkpoint's exact living-set closure and the no-effect action
publication's first-result-wins semantics. They propose a new cellular profile and
atomic life/funding/result publication. Starting funding remains a maintainer
decision; no M11.2 implementation or gate completion is claimed.
Executed: `git diff --check`, plus whitespace and relative-link checks on both new
documents. Reviewed existing headers, migration 0011 and relevant tests as listed
in the delivery plan. No C++/SQL/wire code changed; builds, CTest, clang-format,
clang-tidy and sanitizers were not run for this documentation-only change.
No environment limitation was encountered during these documentation checks.
No deployment, world mutation or provisioning was performed.