Files
aevolution/docs/adr
dingoandClaude Opus 5.5 b1cc3b121b
Foundation / checks (checks) (push) Successful in 5s
Foundation / checks (client) (push) Successful in 5s
Foundation / checks (deploy) (push) Successful in 5s
Foundation / checks (ecs) (push) Successful in 5s
Foundation / checks (network) (push) Successful in 4s
Foundation / checks (postgres) (push) Successful in 5s
Foundation / checks (tsan) (push) Successful in 5s
Foundation / postgres-tools (push) Successful in 30s
Foundation / server-image (push) Successful in 4m44s
Foundation / image (push) Successful in 5m33s
feat(admin): live admin commands in trace 5 (schema 63)
The admin portal can now spawn wildlife, add bubbles, add to or release the
spent pool, remove a cell and grant a cell's reserve on a running rules-13
region (ADR-0182 section 10). No new owner format or region opening.

- Trace 5: trace 4 plus 64-byte command records counted in the tick header's
  last word; a batch without commands stays trace 4 (older builds replay it).
  Bundle 15 admits trace 5.
- CellularLives::admin_candidate applies a tick's commands after its births,
  each on a copy kept only when it applies and closes: imports through the
  boundary ledger, removals into the spent pool with a new `removed` corpse
  cause, spawned roots via the ADR-0180 seed (now a shared helper) funded by
  an exact import. Refused commands change nothing.
- Schema 63: the immutable admin_commands queue (spawn identities from the
  life allocator), pending/history reads, and binding of every recorded
  command exactly once inside both cellular publishers; the SQL trace parsers
  read trace 5 through its trace-4 normal form.
- The region polls pending commands every 2 s and appends up to 16 per tick;
  the admin API and portal gain region actions, per-cell Remove/Grant and the
  command history.
- Fixes an existing test that did not advance its head after a tick commit.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-27 17:14:04 -04:00
..
2026-10-08 12:08:53 -04:00
2026-10-08 12:08:53 -04:00
2026-10-08 12:08:53 -04:00
2026-10-08 12:08:53 -04:00
2026-10-08 12:08:53 -04:00
2026-10-08 12:08:53 -04:00
2026-10-08 12:08:53 -04:00
2026-10-08 12:08:53 -04:00
2026-10-08 12:08:53 -04:00
2026-10-08 12:08:53 -04:00
2026-10-08 12:08:53 -04:00
2026-10-08 12:08:53 -04:00
2026-10-08 12:08:53 -04:00
2026-10-08 12:08:53 -04:00
2026-10-08 12:08:53 -04:00
2026-10-08 12:08:53 -04:00
2026-10-08 12:08:53 -04:00
2026-10-08 12:08:53 -04:00
2026-10-08 12:08:53 -04:00
2026-10-08 12:08:53 -04:00
2026-10-08 12:08:53 -04:00
2026-10-08 12:08:53 -04:00
2026-10-08 12:08:53 -04:00
2026-10-08 12:08:53 -04:00
2026-10-08 12:08:53 -04:00
2026-10-08 12:08:53 -04:00
2026-10-08 12:08:53 -04:00
2026-10-08 12:08:53 -04:00
2026-10-08 12:08:53 -04:00
2026-10-08 12:08:53 -04:00
2026-10-08 12:08:53 -04:00
2026-10-08 12:08:53 -04:00
2026-10-08 12:08:53 -04:00
2026-10-08 12:08:53 -04:00
2026-10-08 12:08:53 -04:00
2026-10-08 12:08:53 -04:00
2026-10-08 12:08:53 -04:00
2026-10-08 12:08:53 -04:00
2026-10-08 12:08:53 -04:00
2026-10-08 12:08:53 -04:00
2026-10-08 12:08:53 -04:00
2026-10-08 12:08:53 -04:00
2026-10-08 12:08:53 -04:00
2026-10-08 12:08:53 -04:00
2026-10-08 12:08:53 -04:00
2026-10-08 12:08:53 -04:00
2026-10-08 12:08:53 -04:00
2026-10-08 12:08:53 -04:00
2026-10-08 12:08:53 -04:00
2026-10-08 12:08:53 -04:00
2026-10-08 12:08:53 -04:00
2026-10-08 12:08:53 -04:00
2026-10-08 12:08:53 -04:00
2026-10-08 12:08:53 -04:00
2026-10-08 12:08:53 -04:00
2026-10-08 12:08:53 -04:00
2026-10-08 12:08:53 -04:00
2026-10-08 12:08:53 -04:00
2026-10-08 12:08:53 -04:00

Architecture decision records

Locked requirements outrank these records. Review architecture, ADRs, public contracts, tests, then implementation. Stop expanding implementation on conflict.

Adopted for proof applies only to the bounded initial headless slice. Proposed recommends without adopting a dependency. Deferred requires a named experiment. Later Accepted and Superseded preserve rationale. Proof choices do not silently settle gameplay or production infrastructure.

Records 0001–0015 cover language, build, dependencies, tests/benchmarks, ECS, ticks, randomness, serialization, units, errors, threads, logging, PostgreSQL, messaging and metrics. 0016–0019 cover durability/ownership, networking/security, infrastructure and voxels. 0020 scopes Gitea delivery and the stateless dev Job. Each record has the eight required sections. 0021 authorizes the opt-in ECS comparison only, not a production dependency. 0022 adopts the bounded sequential lifecycle-command scheduler for the proof. 0023 defines local periodic neighborhood queries and a measured linear baseline. 0024 adopts finite, typed energy/matter inventory transfers for M2.1. 0025 scopes finite capture, growth recipes and residual accounting for M2.2. 0026 adds shared community ownership and bounded synthetic feeding for M2.3. 0027 adds terminal inventory ownership and budgeted nutrient return for M2.4. 0028 adopts funded reproduction, bounded slot capacity and retained lineage IDs. 0029 scopes the deterministic ecosystem driver and bounded measured episodes. 0030 adopts the immutable genome v1 record, validation and canonical encoding. 0031 adopts deterministic development, derived phenotype and bounded plans. 0032 derives non-uniform metabolic budgets and the first genome/ledger path. 0033 adopts the bounded mutation catalog and uniform seeded candidate draws. 0034 adopts the permanent lineage archive and absence that is never extinction. 0035 derives strategies from genomes and measures them over a split-half gradient. 0036 defines the tier 2 cohort, its declared resolution and exclusive ownership. 0037 collapses individuals into a cohort as one sampled, ledger-exact transaction. 0038 accounts a proposed interval, refusing rather than clamping, without picking a model. 0039 materializes representatives on shares that round down and ages that never fall. 0040 measures what aggregation costs and refuses to call the result equivalence.

Every dependency adoption records exact version/commit and integrity hash, transitive license obligations, maintenance/security review, owner and removal boundary. Candidate performance and binary-size comparisons are hypotheses until benchmarked. Primary sources were reviewed during the initial September 2026 design. No unadopted candidate is a link dependency of the proof.