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
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:
@@ -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
|
||||
|
||||
@@ -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
|
||||
|
||||
Reference in New Issue
Block a user