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
+27
View File
@@ -5372,3 +5372,30 @@ Executed:
- Windows `debug`: 61/61.
No biology uses the conversion yet, so no golden is affected.
## 2026-10-09 — M11.1 time-based rates, segment 2: genome schema 2 (ADR-0099)
Genome schema 2 stores movement and ingestion per second (ranges ×20;
`schemas/genome-v2.md`). Schema 1 records stay valid and read as exactly ×20, and drafts
default to schema 1. Development version 1 converts genome rates at its 50 ms quantum.
Mutation keeps the parent's schema and step. The lineage archive header names exactly
the highest schema held, and the development opening names schema 1.
New tests:
- `schema_v2_rates` (genome);
- range boundaries per schema;
- `schemas_mix_without_rewriting` (archive);
- `schema_v2_rates_develop_identically`: phenotypes and plans equal across schemas, and
sub-tick rates round down;
- `successors_keep_their_parents_schema` (mutation).
Two existing tests used 2 as "an unknown future schema". They now use the next unknown
schema, and the archive decoder now refuses a header that misstates its contents. No
golden changed: the frozen schema 1 record and its digest are byte-identical.
Executed:
- WSL `linux-debug` and `linux-asan`: 61/61 each.
- clang-tidy 19 on the changed sources and tests: clean.
- The 18 Postgres suites passed, including region upgrade and clone comparison, so
checkpoints are unchanged.
- Windows `debug`: 61/61.