M11.1: genome schema 2 with per-second rates (ADR-0099, segment 2)
Foundation / checks (deploy) (push) Successful in 3m32s
Foundation / checks (ecs) (push) Successful in 1m56s
Foundation / checks (client) (push) Successful in 12m56s
Foundation / checks (network) (push) Successful in 13m46s
Foundation / checks (tsan) (push) Successful in 7m59s
Foundation / checks (checks) (push) Successful in 33m36s
Foundation / checks (postgres) (push) Successful in 45m30s
Foundation / postgres-tools (push) Successful in 20s
Foundation / server-image (push) Successful in 25s
Foundation / image (push) Successful in 2m36s

Movement and ingestion are stored per second in schema 2 (ranges x20). Schema 1 records
stay valid, are never rewritten, and read as exactly x20 via Genome::per_second; drafts
default to schema 1 so existing literals keep their meaning. Development version 1
converts genome rates at its own 50 ms quantum (round down), so phenotypes are
unchanged. Mutation keeps the parent's schema and step; the lineage archive header names
exactly the highest schema held (all-schema-1 archives keep their bytes); the
development-v1 opening names schema 1. No golden changed; two tests that used 2 as an
unknown schema now use the next one. Refresh the dev session window.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
dingo
2026-10-09 13:16:55 -04:00
co-authored by Claude Opus 5.5
parent a4c6181540
commit 17fe23e5f0
17 changed files with 385 additions and 56 deletions
+6 -2
View File
@@ -20,8 +20,12 @@ the maintainer chose directional rounding):
- **Segment 1 (done):** `accounting/rates.hpp` converts a per-second rate to a per-tick
amount without saved state. Costs round up and capacities down, so rounding never
favours the organism. The migration's exact ×20 inverse refuses inexact values.
- **Segments 2–3 (next):** genome schema v2, development version 2, and the process and
checkpoint fields, with unchanged 50 ms goldens.
- **Segment 2 (done):** genome schema 2 stores rates per second. Schema 1 records are
read ×20 and never rewritten. Development version 1 converts at its own 50 ms
quantum, mutation keeps a lineage's schema, and an archive of schema 1 records keeps
its bytes. No behaviour or golden changed.
- **Segment 3 (next):** development outputs, feeding and decay limits per second,
converted at each process's tick.
Open from M10 (BACKLOG):
- the maintainer's native-client observation, moved to the later 2k drill;