Foundation / checks (deploy) (push) Successful in 4s
Foundation / checks (ecs) (push) Successful in 2m38s
Foundation / checks (network) (push) Successful in 22m52s
Foundation / checks (client) (push) Successful in 23m48s
Foundation / checks (tsan) (push) Successful in 23m38s
Foundation / checks (postgres) (push) Successful in 53m31s
Foundation / checks (checks) (push) Successful in 1h9m6s
Foundation / postgres-tools (push) Successful in 2m0s
Foundation / server-image (push) Successful in 4m2s
Foundation / image (push) Successful in 4m40s
60 lines
4.4 KiB
Markdown
60 lines
4.4 KiB
Markdown
# Validation strategy
|
|
|
|
M12.4f's checkpoint contract exercises explicit portable bundle-9 to 10 upgrades
|
|
for raw owners and a real nonempty cohort with retained policy/sequence. It
|
|
requires complete candidate equality, canonical restore, continued batch-2
|
|
biology and bundle-preserving representation changes. Negative cases cover
|
|
old/new payload confusion, malformed source/lease/digest bindings, exhaustion,
|
|
repeated upgrade and new genesis. The private PostgreSQL population suite must
|
|
continue refusing these portable candidates through schema 45 and existing
|
|
prepared/generic publication paths without advancing the head. Durable admission
|
|
and upgrade crash/retry recovery remain separate gates.
|
|
|
|
Tests defend contracts, not directory coverage. All checks remain active in
|
|
Release builds. Current proof has no actual network, biology or distributed
|
|
recovery, so those categories below are milestone gates rather than passing
|
|
test labels attached to empty targets.
|
|
|
|
| Category | Foundation evidence | Future gate |
|
|
|---|---|---|
|
|
| Unit | PRNG reference vectors, entity lifecycle, capacity/error boundaries | Genome development and energetic transfer rules |
|
|
| Deterministic regression | Frozen canonical fingerprint plus independent reference calculation; uninterrupted vs restored execution | Versioned ecosystem baseline ensembles |
|
|
| Property-style | Many explicit seeds and tick split points; coordinate and ID invariants | Conservation, nonnegative mass/population and phenotype prerequisites |
|
|
| Serialization | Exact byte round-trip, malformed lengths/versions/checksum/IDs/coordinates; validate before publication | Compatible migrations, verified object archive and replay range |
|
|
| Integration | CLI seed/ticks and replay verification; file save/load comparison | Durable death/reproduction acknowledgment and worker process kill |
|
|
| Fuzz | Optional libFuzzer snapshot decoder with bounded input and sanitizer instrumentation | Authenticated protocol/parser and migration fuzzing |
|
|
| Static/sanitizers | clang-format/tidy; ASan/UBSan and separate TSan configurations | TSan on real scheduler and I/O lifecycle |
|
|
| Benchmark/load | Seed/count/tick/time/compiler report for kernel; no noisy portable time threshold | 20+ clients, region load, interest bandwidth, recovery backlog |
|
|
| Biological regression | Absent until M2; do not call synthetic particles an ecosystem | Million-tick balances, predator/prey cycles, starvation, diversity and extinction |
|
|
| Disaster recovery | Absent until persistent services exist | Off-host verified backup restore; database/object consistency; old owner fencing |
|
|
|
|
Reference fixture, rules/format 1: seed 123456, create 8 particles at (0,0), then
|
|
1,000 ticks yields canonical payload FNV-1a `d61ad5bf0c928c76`. Expected positions
|
|
by ID: (49,10), (985,993), (39,33), (1008,0), (16,1), (7,3), (1004,1007),
|
|
(995,15). The initial value was computed independently in JavaScript with
|
|
explicit wrapping BigInt arithmetic, not copied from the C++ test result.
|
|
SplitMix64 seed-zero vectors begin `e220a8397b1dcdaf`, `6e789e6aa1b965f4`,
|
|
`06c45d188009454f`, `f88bb8a8724c81ec`.
|
|
|
|
Changing a golden requires a stated rule/format change, compatibility decision,
|
|
independent review and updated documentation. A new compiler or optimization
|
|
mode must reproduce existing integer fixtures. Floating-point biology later
|
|
needs error envelopes and ensemble comparisons in addition to exact fixtures.
|
|
|
|
Unexecuted configurations are not validation. Record exact tools, commands,
|
|
results and limitations in VALIDATION.md at the end of each foundation change.
|
|
|
|
The cohort qualification runs its complete matrix under sanitizers; its wall
|
|
timeout is a bounded CI execution guard, not a portable performance claim.
|
|
Budgets are 180 s normally, 600 s with ASan/UBSan and 900 s with TSan. The larger
|
|
migration contract gets 180/360/600 s respectively. Cases, seeds, checks and
|
|
instrumentation remain identical. The checks job allows 90 minutes for the full
|
|
cold/shared-runner build, instrumented suites and remaining fuzz/benchmark steps.
|
|
|
|
Population and migration restart scripts honor the runtime `EVO_TEST_TMPDIR`
|
|
override and create distinct random fixture subdirectories there. Without the
|
|
override they retain the configured build-directory output paths. The non-root,
|
|
networkless, read-only TSan container sets the override to its existing bounded
|
|
`/tmp` tmpfs; no source/build mount is made writable and no sandbox permission is
|
|
broadened. Fixture path randomness has no biological or test-result meaning.
|