ADR 0127
Foundation / checks (deploy) (push) Successful in 6s
Foundation / checks (ecs) (push) Successful in 2m23s
Foundation / checks (tsan) (push) Successful in 10m11s
Foundation / checks (client) (push) Failing after 14m26s
Foundation / checks (network) (push) Successful in 18m54s
Foundation / checks (checks) (push) Successful in 42m9s
Foundation / checks (postgres) (push) Successful in 43m51s
Foundation / postgres-tools (push) Skipped
Foundation / server-image (push) Skipped
Foundation / image (push) Skipped

This commit is contained in:
dingo
2026-10-15 09:32:51 -04:00
parent 0a0f6c3bb1
commit 817a830a8a
20 changed files with 474 additions and 28 deletions
@@ -52,6 +52,27 @@ after each death.
- While a life is active, a new request is still a permanent `existing_life`
refusal for that request id.
#### Birth refusal scheduling clarification (2026-10-15)
An expected nursery funding, placement, or existing-life refusal must not reject
the entire region tick. The scheduler's `append_with_birth_refusals` separates
these requests from accepted births, advances the ordinary tick, and returns
transient refusal reports. Strict `append` retains its all-or-nothing contract.
Malformed input or unexpected biological errors still reject the append.
After confirmed publication, the host removes refused requests from its spawn
queue and records the existing lease-fenced `reject_primitive_life` result. An
uncertain database answer stays unknown; a bounded transient cache withholds the
request from spawning while an exact request/query reconciles it, including after
account control takeover. After cache eviction or process recovery, the durable
reservation is checked again before any retry. No refusal is reported as final
until the store confirms it. A lost, unacknowledged report may be re-evaluated;
a durable refusal remains final for that request ID.
No nursery refill, alternate spawn rule, protocol/schema revision, simulation
version or replay format is introduced. Refused births are absent from the
committed trace; accepted births still use the existing publication transaction.
### Old sessions
- A carried action whose account has no living life, or that names a patch the life
+8
View File
@@ -96,3 +96,11 @@ return requested actions; the app owns sessions, fixture and selection.
M9.8d (ADR-0085) adds SDL-free bindings (actions vs HID key usages, validation,
versioned controls file) to `evo_client_controls`; the adapter maps keys through
them and offers binding capture ahead of toolkit and world input.
The v10 cellular app shows observed reserve differences as **net** changes across
the named tick interval, never as measured intake. Duplicate views retain the last
change; reconnect and a different life reset its baseline. Energy/matter patch
markers and stock cards use copied sensor data only. A final birth refusal permits
an explicit new request even before a perception arrives; pending/unknown requests
retain their ID and an existing-life result waits for that life. These are app
presentation/control policies, not biological rules.
+18
View File
@@ -83,6 +83,24 @@ death notices are not a historical death query. Automatic feeding uses observed
contact, so a patch crossed entirely between observations can still be missed;
slowing near food reduces that risk without predicting authority.
Food reading (2026-10-15): zoomed-in patches carry a gold `E` for remaining energy
and a teal `M` for remaining matter. The Food tab shows energy stock and all four
matter channels, and explicitly labels matter-only and depleted patches. Auto-feed
prefers an energy-bearing patch when several stocked patches touch the cell;
manual selection remains available. These stocks are shared and finite. Uptake
is capacity-limited and maintenance precedes feeding, so processing a feeding
attempt does not guarantee gaining energy or surviving. The Cell tab reports
net reserve change across successive observed ticks (including all spending),
last-tick upkeep/movement, and an energy-free target warning. It does not claim an
exact intake amount that v10 does not carry.
Pending birth feedback now says that the server has not confirmed a cell. The
client rechecks the same request every two seconds. A confirmed funding/placement
refusal or cancellation enables an explicit new request without requiring a first
world view. An existing-life result waits for that life instead. The scheduler
fix in ADR-0127 is also required on the server: a client upgrade cannot repair a
region tick blocked by an unfulfillable nursery request or replenish its nursery.
Coordinate contract discrepancy found during this work: the cellular bridge sends
ADR-0102 lower-left footprint coordinates through the general presentation's
centre-offset fields. Assistance deliberately interprets only cellular-session
+3
View File
@@ -334,6 +334,9 @@ scoped change before starting the next segment.
leaves the builder unchanged. Tests cover empty-region birth replay and
duplicate request refusal. The server still needs to route v5 requests into
this queue and run/publish the scheduler tick.
2026-10-15 correction: strict `append` keeps that contract; the live scheduler
uses `append_with_birth_refusals` so expected nursery refusals cannot stall the
region. The host records those refusals after confirmed publication (ADR-0127).
- 11.3d-7k: region sessions can now enable the reliable v5 life-request
callbacks and v7 cellular action ledger together. Admission remains per
negotiated connection; unsupported v5/v6/v7 modes still fail closed. QUIC