M11.1: environmental rules 3 with per-second rates (ADR-0099, segment 3)
Foundation / checks (deploy) (push) Successful in 3m27s
Foundation / checks (ecs) (push) Successful in 1m58s
Foundation / checks (client) (push) Successful in 12m20s
Foundation / checks (network) (push) Successful in 13m53s
Foundation / checks (tsan) (push) Successful in 8m9s
Foundation / checks (checks) (push) Successful in 33m4s
Foundation / postgres-tools (push) Canceled after 0s
Foundation / server-image (push) Canceled after 0s
Foundation / image (push) Canceled after 0s
Foundation / checks (postgres) (push) Canceled after 21m43s

Rules 3 is rules 2 with irradiance, growth, intake and decay per second. The community
derives its per-tick form once at creation and restore (rationals exact via the tick in
numerator and denominator, caps rounded down); steps and the snapshot layout are rules
2's; the codec reads formats 1-3. At 50 ms a x20 per-second twin steps identically
through feeding, death and decay and across a snapshot; at 25 ms caps halve. Rules 1/2
and the development-v1 opening are unchanged. Development version 1 outputs stay tied
to their 50 ms quantum and the tick-abstract M2 fixtures are not migrated (recorded).
environmental-qualification's "unknown rules" case moves from 3 to 4.
Refresh the dev session window.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
dingo
2026-10-09 14:55:45 -04:00
co-authored by Claude Opus 5.5
parent b5ea632165
commit 4319da2750
10 changed files with 224 additions and 26 deletions
+7 -2
View File
@@ -24,8 +24,13 @@ the maintainer chose directional rounding):
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.
- **Segment 3 (done):** environmental community rules 3 states irradiance, growth,
intake and decay per second. At 50 ms it steps identically to its rules 2 twin. The
dev world's rules 2 opening is unchanged. Development version 1 outputs stay tied to
their declared 50 ms quantum. The tick-abstract M2 fixtures are not migrated. ADR-0089's
rate migration is complete.
- **Next in 11.1:** development version 2, a first bud fundable within a session
(ADR-0098 decision 7).
Open from M10 (BACKLOG):
- the maintainer's native-client observation, moved to the later 2k drill;
@@ -98,6 +98,31 @@ contract and a versioned migration that preserves 50 ms behaviour.
- **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.
## Segment 3 as implemented (2026-10-09)
- **Environmental community rules 3** is rules 2 with every rate per second:
irradiance and growth as rationals per second, and intake and decay caps per
second.
- At creation and restore, the community derives its per-tick form once. The
rationals convert exactly, because the tick folds into numerator and denominator.
The caps round down.
- Steps run on that form unchanged, the snapshot keeps rules 2's layout, and the
codec reads rules 1 to 3.
- At 50 ms, a ×20 per-second twin of a rules 2 configuration steps identically
through feeding, death and decay, and across a snapshot. At 25 ms the caps halve.
- Rules 1 and 2, including the dev world's fixed `development-v1` opening, are
unchanged.
- **Development version 1 outputs** (maintenance, movement, intake limit) stay per
tick of its 50 ms quantum, which is how that version is defined.
- A live process at another tick reads them through `per_second_from_per_tick` and
`per_tick`.
- Development version 2 (the birth-cost re-derivation, ADR-0098) is defined per
second natively.
- **The M2 ecosystem fixtures** (consumer and producer configurations, the feeding
decomposition limit) are tick-abstract test oracles with no time base, and are not
migrated. New gameplay processes (11.3) use per-second rates from the start.
- **Result:** every rate that a live world can run on is now either per second
(genome schema 2, rules 3) or tied to a declared quantum it converts from.
## Consequences
- Segment 1: `accounting/rates.hpp` (`per_tick`, `exact_per_tick`,
`per_second_from_per_tick`) and the `rate-contracts` test.
+24
View File
@@ -5399,3 +5399,27 @@ Executed:
- The 18 Postgres suites passed, including region upgrade and clone comparison, so
checkpoints are unchanged.
- Windows `debug`: 61/61.
## 2026-10-09 — M11.1 time-based rates, segment 3: environmental rules 3 (ADR-0099)
Environmental community rules 3 has rules 2's layout with irradiance, growth, intake
and decay per second. It derives a per-tick form at creation and restore: exact
rationals, caps rounded down. Its format is 3 (`schemas/environmental-community.md`).
Development version 1 outputs stay tied to their 50 ms quantum, and the
tick-abstract M2 fixtures are not migrated. Both are recorded in ADR-0099.
`rules3_per_second` tests:
- a ×20 twin of a rules 2 configuration over 60 ticks, through feeding, a consumer
death and decay, with reports and every inventory equal each tick;
- snapshot and restore as format 3, then identical steps;
- at 25 ms, a 2000-per-second intake cap admits 50 and refuses 51;
- an overflowing rate and an over-long tick are refused.
`environmental-qualification` used rules 3 as "unknown". It now uses 4, with the same
intent.
Executed:
- WSL `linux-debug` and `linux-asan`: 61/61 after that change.
- clang-tidy 19 on the changed sources and tests: clean.
- The 18 Postgres suites: passed.
- Windows `debug`: 61/61.