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
@@ -77,6 +77,27 @@ contract and a versioned migration that preserves 50 ms behaviour.
or not at all, would rescale biology. The goldens at 50 ms are the guard against
this.
## Segment 2 as implemented (2026-10-09)
- **Genome schema 2** ([genome-v2.md](../../schemas/genome-v2.md)): movement and
ingestion are per second, with ranges ×20. `Genome::per_second` reads either schema.
A schema 1 rate reads as exactly ×20.
- **Drafts** default to schema 1, so every existing literal keeps its per-tick
meaning. New records name schema 2.
- **Development version 1 stays defined in 50 ms ticks**
(`development_v1_tick_microseconds`). It reads genome rates per second and converts
them at that quantum, rounding down (capacities). Its per-tick outputs are unchanged.
A schema 1 genome and its exact schema 2 translation develop identically.
Development's outputs move to per-second rates in segment 3, at the consumers.
- **Mutation** keeps the parent's schema and step. Mutation offers are seeded from the
genome's digest, so migrating a lineage's records would change every later offer;
no lineage is migrated.
- **The lineage archive** header names exactly the highest schema held. An all-schema-1
archive, which is what dev worlds hold, keeps its bytes.
- **The development opening** (`development-v1`) names schema 1 explicitly; it is a
fixed genesis.
- **Tests that used 2 as an unknown future schema** now use the next unknown one. The
archive decoder refuses a header that misstates its contents.
## Consequences
- Segment 1: `accounting/rates.hpp` (`per_tick`, `exact_per_tick`,
`per_second_from_per_tick`) and the `rate-contracts` test.