d4fe11cf552e7feb6804a142fd2ffc495d4acb7e
11
Commits
| Author | SHA1 | Message | Date | |
|---|---|---|---|---|
|
|
a2c4543df2 |
Complete M7.4b lineage checkpoint profile; M7.4 done
ADR-0062 adds a canonical LineageArchive codec (parents before children, organisms by id, FNV) that decodes by replaying admit/record_birth/ record_death and requires byte-identical re-encoding; it never overwrites an existing archive. LineageRegion binds the environmental producer and consumer accounts to archived organisms with identity high-waters, enforces closure (lifecycle vs deaths, exact living set, tick bounds) and records deaths in the tick that causes them. Checkpoint profile 2 (environmental-lineage-v1, history profile 1) publishes that container; schema v4 admits it with a 4,268,144-byte cap and requires each commit to keep its predecessor's profile, RNG, history and durability declarations. Linux adds provision/publish/recover for the profile on the shared publication path. Qualification found WSL2 stepping CLOCK_REALTIME back ~0.5 s every ~32 s, which made two 1 s-lease tests flaky under ASan. Tests now wait on database-time expiry; ADR-0060 records the slewed-clock requirement. Validated: Windows CTest 57/57; Linux GCC Debug/Release, clang-tidy and ASan/UBSan CTest 57/57 each; PostgreSQL suites 2x Release, 2x analysis, 5x ASan; SQL and C++ mutations each caught. No Docker/Gitea CI, remote store, process kill or deployment. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> |
||
|
|
29ce255cfb |
Close the forms of forgetting that are not named like removal
The retention claim covered methods named like removal and nothing else,
so the archive forgot everything on assignment: archive = LineageArchive{}
discarded every record, and assigning a copy taken before a death
restored that organism's living state, defeating terminal death as well.
The copy and move policy is now part of the interface rather than left to
the defaults. Both forms of assignment are deleted, which also makes the
archive unswappable since swapping needs them. Declaring the copy
constructor suppresses the implicit moves, so a move decays to a copy and
a moved-from archive still holds every record rather than being emptied
the way a moved-from container would be.
Copying stays available on purpose: a clone takes nothing from the
original, and GENOME_MODEL expects migrations to be rehearsed on cloned
worlds. Deleting the move constructor as well would be stricter but would
stop an archive being returned from a function, so it decays instead.
The interface tests now cover assignment, replacement from a temporary
and swapping alongside the named methods, each with a std::vector
positive control so the checks are known to be live. Runtime checks
confirm a copy taken before a death leaves the original's terminal record
standing, and that a moved-from archive still holds everything. All four
static assertions were confirmed to fail with the deletions removed.
ADR-0034 said the type offered no way to forget. That was too narrow, and
the Decision and Alternatives now say why assignment counts.
Native Release, clang-tidy analysis, ASan and format checks pass 21/21.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
|
||
|
|
8020347f9b |
Keep every lineage, and never call absence extinction
M3.5 retains the genomes M3.4 produces and the organisms that carried them. The named risk is deleting extinct genomes, so the answer is structural: LineageArchive has no removal operation at all, not a guarded one and not a private one. Retention is a property of the interface rather than a rule someone has to remember, which is the only form of "keep extinct genomes indefinitely" that a later change cannot quietly undo. Four concepts assert that, with a positive control so the check is known to be live rather than vacuous. Admission requires the parent to be present, so ancestry never dangles and the parent graph is acyclic by construction: a cycle would need one of its members admitted before itself. A duplicate identity is refused rather than overwritten, because overwriting is deletion renamed. Organism identity and genome identity stay separate. A death is terminal for the organism and touches nothing about the genome it carried; ancestry, descendants and divergence all resolve afterwards. The quieter risk is calling something extinct that is merely unobserved. The archive reports living or absent and has no third answer: terminal extinction is a policy judgement over a reconciled watermark covering suspended members, eggs, spores and in-flight transfers, none of which this type can see, so the word does not appear in the API. Absence is also reversible, and a test shows a lineage regaining a carrier. Capacity is bounded and admission fails loudly at the limit, since refusing to record is not deleting but a silent drop would be. The roadmap lists an NPC-mutation decision as a dependency, and OPEN_QUESTIONS leaves it open until M12. It stays open: the archive records an origin event and never an actor, so whether an NPC may diverge changes nothing here. Two clang-tidy findings were fixed rather than suppressed. std::map members made the archive's move potentially throwing, because MSVC's map move constructor allocates; sorted vectors replaced them. A wrapper struct holding a Genome by value had the same problem, since ADR-0030 made Genome copy-only, so genomes are stored directly under their own id(). The redundant carrier tally went with it: carriers are counted from the organism records, so no second tally can drift. Native Release, clang-tidy analysis, ASan and format checks pass 21/21. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> |
||
|
|
badd28fe9b |
Check the context an offer records, not the list it produced
Selection established that a context was unchanged by regenerating the candidate list and comparing it. That cannot establish it. Four of nine operators is only 126 distinct lists, so different contexts draw the same one routinely, and an offer from event 1 was accepted under event 239. An offer now records what produced it: the parent's identity and digest, and the context itself. Selection compares those directly, before anything else. Because the context and parent then determine the draw, a list that still differs means the offer itself was altered, which is now reported as its own error rather than as a context having moved. The regression searches for a context whose draw collides with the offer's and asserts that such a collision exists rather than assuming one, then requires selection to reject it. It was confirmed to fail against the previous implementation. One expectation of mine was wrong and is now stated correctly: rewriting an offer's recorded context to name the colliding one is accepted, and should be. Those candidates genuinely are what that context draws, so the result is a legitimate offer for it rather than a forgery. The check is that the recorded context matches the current one, not provenance. Editing a candidate remains caught, as an altered offer. Native Release, clang-tidy analysis, ASan and format checks pass 20/20. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> |
||
|
|
5497f4d74c |
Propose mutations without proposing a best build
M3.4 adds the candidate-generation experiment GENOME_MODEL describes: a static catalog of four effects over the seven capabilities, drawn from a recorded context with an explicit stream. The named risk is a hidden best build or offerings biased toward what would help, so the defence is structural rather than asserted. Nothing is ranked: candidates are drawn without replacement by rejection sampling, making every eligible operator exactly as likely as any other, and the result is returned sorted by operator ID. No score exists in the record, position carries no meaning, and nothing about an organism's situation makes a helpful mutation more likely to be offered. Eligibility is not a second rulebook. An operator is eligible when the genome it would produce passes the M3.1 validation unchanged, so prerequisites, required capabilities, ranges and the acyclic development graph are enforced once, where they were defined. Shedding a capability another declares as a prerequisite fails that check with no rule written here to catch it. Range boundaries are refused rather than clamped, since a clamp would make two operators agree and offer a no-op as a choice. The draw reads the parent digest and the context and nothing else, so the same context always returns the same candidates and a retry cannot reroll; a new event index is what earns a new draw. select_mutation regenerates the offer and refuses unless it still matches, so a changed context is rejected rather than answered with a different mutation. Cost is not invented: a candidate reports the successor's own maintenance and mass under ADR-0032, and reserves nothing. The eligible set is pinned by hand from the schema rather than observed, and the uniformity check is confirmed to fail against a draw that takes the first eligible operators. The rejection sampling that removes modulo bias is correct by construction, not test-verified: at this scale the bias is one part in 10^18. That is recorded rather than claimed. No organism mutates and no fixture calls any of this. Candidate count, mutation cost as a game rule, inherited versus acquired expression, NPC mutation and recombination all remain open, as GENOME_MODEL requires. Native Release, clang-tidy analysis, ASan and format checks pass 20/20. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> |
||
|
|
36ee71cfe9 |
Decide affordability where composition is known
A construction transition could require more of an element than was available, because the check compared net mass. A step growing a body from 13 to 14 femtograms nets one femtogram but acquires a carbon and a nitrogen while freeing one of other, and released other pays for neither. Matching totals let one element silently fund another. Net mass was never the right question, and the layer asking it could not ask a better one: plan_development has no composition. A single scalar pool could not carry the answer either, since it cannot say that carbon is plentiful while nitrogen is not. The environment now states what is available per ledger channel. plan_development keeps a total-mass bound, which is sound because net never exceeds gross, but it is a proposal rather than an authority. metabolic_budget narrows it to the largest step whose own intake fits channel by channel, and reports the growth that step actually funds. That revises ADR-0031 on this point, recorded in both ADRs. The tests place a single femtogram in each channel in turn and require that no step needing a different element is funded, that nothing is acquired beyond what is present, and that the mass-only plan would have admitted the step; a carbon and a nitrogen together then fund it exactly. Across six target sizes by seven growth fractions by four stock levels, every reported intake fits the availability channel by channel and never exceeds the proposed step. Confirmed to fail with the check removed. The releasing case moved to a target of 20 femtograms, where the step occurs at the full rule step rather than depending on a scarce supply that the corrected plan no longer bounds the same way. Native Release, clang-tidy analysis, ASan and format checks pass 19/19. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> |
||
|
|
e0fd4680f6 |
Make construction reproduce the body it claims to build
Construction composed the mass difference instead of differencing the two composed bodies. Those are not the same: composing the difference throws away the rounding the existing body already carries, so the budget summed to the right total while funding individual channels short or over. At target mass 1001 growing from 10 to 60 it funded C25 N7 P2 other16, leaving nitrogen and phosphorus one short each and other two over, so spending it could not produce the body the same rules derive. Construction is now the per-channel difference between the composed bodies, which funds C25 N8 P3 other14 for that case. That difference can be negative on a channel, because the remainder rule is not monotone: a body growing from 13 to 14 femtograms sees other fall from 6 to 5. Construction is therefore a transition with an intake and a release rather than a single requirement, and the release is a rounding artifact bounded by a few femtograms, not excretion. The invariant held + intake - release == reached is asserted per channel for the reported case, for the releasing case, across six target sizes by seven growth fractions by four material budgets, and across a forty-step walk from nothing to full growth where accumulated intake and release are checked against the whole history. The net of every transition is also asserted to equal what a plan charges material for. These tests were confirmed to fail against the previous implementation. Native Release, clang-tidy analysis, ASan and format checks pass 19/19. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> |
||
|
|
be71d4f441 |
Give capability a cost without giving it a multiplier
M3.3 turns a phenotype into the budgets a ledger can hold: body composition, maintenance, movement, the next construction step, the per-tick intake limit and the reproduction investment. metabolism is the single place the genome's description of capability becomes accounting quantities, so the record itself stays free of those types and M3.1's boundary is crossed once, explicitly. The named risk is reintroducing RPG modifiers, where a capability parameter becomes a flat percentage over every budget. Each budget is therefore derived from a different phenotype quantity: maintenance from mass plus membrane upkeep, movement from mass and speed, intake from surface, construction from the mass a growth step adds, investment from the body a parent already has. One parameter moves some budgets and not others, by different amounts. Doubling membrane thickness costs more matter to build, more energy to hold and more to haul, while leaving uptake, speed, assimilation and structural mass identical, and the mass and maintenance ratios differ, so no single multiplier could produce it. The test asserts that non-uniformity rather than describing it. Composition is declared per compartment, and membrane is the carbon-rich one, so a thicker membrane changes what a body is made of and not only how much. A split assigns the first three channels by share and gives the remainder to the last, so parts always sum back to the whole and a derived body can be spent through the ledger without a rounding leak. That is checked at four awkward masses where every share floors. processes::consumer_for is the first path from a genome into the M2 fixtures. Opening inventory stays the caller's: a genome says what an organism can do, never what it holds, and a derived config that invented an opening balance would create matter. A derived consumer is shown driving a real feeding tick with the ledger conserving exactly, and a bite one femtogram past the derived cap refused by the M2.3 contract. Every budget is asserted as a hand-calculated literal. The constants are chosen so budgets are of comparable magnitude, which is legibility for tests and not tuning. No existing fixture reads genomes, and no organism spends any budget: there is still no starvation, death or repair rule. Native Release, clang-tidy analysis, ASan and format checks pass 19/19; every existing golden and fingerprint is unchanged. Linux CI has not run. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> |
||
|
|
3f86dada0e |
Derive a phenotype from the genome without touching it
M3.2 adds derive_phenotype and plan_development as pure integer functions of a genome, a growth state and an environment. Nothing is stored: a phenotype is recomputed from retained inputs rather than cached, so a cached copy can always be checked against a recomputation. The risk this increment was scoped against is confusing the genome with runtime damage. Growth and damage live in a separate state that no function may write back, and no entry point takes a mutable genome. Damage changes the phenotype and leaves the encoded bytes and content digest identical, so heredity cannot carry acquired condition. The genome's development version selects a rule set, which is what makes that field worth carrying; an unknown version fails closed rather than deriving under the wrong rules. Version 1 declares every constant. The shape model is explicit rather than implied: the body is a cube of uniform declared density, so extent is an exact integer cube root and surface is six extents squared. Membrane mass follows surface and the genome's thickness, maintenance follows total mass plus a membrane upkeep term, and uptake scales with surface, so size trades uptake against maintenance. A capability the genome does not carry yields zero. A plan advances growth by at most the rule step, reduced to the largest step the available material funds exactly, never a partial one and never a grant. It reserves nothing and pays for nothing: the matching transfer does not exist until M3.3, and an apply that moved no inventory would look like a committed operation while conserving nothing. The fixture genome is an exact 20 micrometre cube, so every derived value is asserted as a hand-calculated literal, as are the half-built, damaged, maximum and cube-root-boundary cases. Determinism is checked over 45 growth and temperature combinations. The declared flooring is pinned rather than hidden: a body whose mass floors to zero advances its counter for no material, granting no structure because none exists either way. Omitted physics is a documented model limitation, not a modifier. Nothing here is balance, and no organism yet develops. Native Release, clang-tidy analysis, ASan and format checks pass 18/18; every existing golden and fingerprint is unchanged. Linux CI has not run yet. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> |
||
|
|
64a12c4dfc |
Make genome validity survive moves and freeze the v1 encoding
Two defects from review of
|
||
|
|
8584eb1f6f |
Add the immutable genome v1 record and its canonical encoding
Open M3 with the record that development and mutation will read, in a new evo::biology library that nothing else links yet. A genome is validated once at construction and exposes no mutator, so an invalid one cannot exist at runtime and callers never revalidate. A draft carries unvalidated input; create and decode apply identical semantic checks, so a decoded record is never less validated than a constructed one. Schema 1 fixes the seven v0.1 capability kinds. Each has a unit, an inclusive range, whether every genome must carry it, and the capabilities it mandates, all held as schema facts rather than record data, so no record can contradict its own units. A capability adds one parameter and a bitmask of declared developmental edges; the union of declared and mandated edges must be acyclic, which seven nodes make exact and bounded. Identity is a nonzero world-scoped genome ID distinct from every runtime identity, a nonzero origin event, and zero or one parent. Zero parents identifies a documented founder. The format reserves room for a second so recombination needs a schema version rather than a layout change. The encoding follows ADR-0008: explicit little endian, bounded before any allocation, an exact length match so trailing bytes are rejected, records strictly ascending by kind so the bytes are canonical and duplicates fall out of the same comparison, a stored digest recomputed on decode, and a trailing checksum. The digest covers identity and ancestry, so identical capabilities from different origins never share one. Neither value is an authenticity claim. Unknown schema versions fail closed. Tests cover ancestry rules, every declared range boundary from both sides, self, mutual and three-node cycles, a cycle closed by a mandated edge, truncation at every length, trailing and oversized buffers, every single-byte corruption, and three resealed edits that reach the digest, version and ordering checks rather than stopping at the checksum. One branch is recorded as uncovered rather than given a test that cannot fail: in schema 1 every mandated capability is also required. No genome affects any simulation. Native Release, clang-tidy analysis, ASan and format checks pass 17/17; golden d61ad5bf0c928c76 and ecosystem fingerprint 2cd4a15f9fbe9949 are unchanged. Linux CI has not run yet. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> |