Files
aevolution/docs/adr
dingoandClaude Opus 5.5 6de2b7b1ca
Foundation / checks (client) (push) Successful in 5s
Foundation / checks (checks) (push) Successful in 6s
Foundation / checks (deploy) (push) Successful in 6s
Foundation / checks (ecs) (push) Successful in 5s
Foundation / checks (network) (push) Successful in 4s
Foundation / checks (postgres) (push) Successful in 4s
Foundation / checks (tsan) (push) Successful in 5s
Foundation / postgres-tools (push) Successful in 5m17s
Foundation / image (push) Successful in 6m23s
Foundation / server-image (push) Successful in 8m26s
feat(admin): end a stranded life from the portal (schema 69)
ADR-0182 section 18. Region 16 refused every birth for an account with
"Existing cell is already bound to this account" although no cell in it
held the account: a published reservation was never ended, and the only
remedy was tools/ops/end-account-life.sql as the database owner.

- Account action POST /api/accounts/<uuid>/end-life?request=N. The admin
  API reads the life's region from the account's lives and refuses while
  that region's live view lists a cell holding the account (also a bud,
  split offspring or organism control moved to), a region it cannot view,
  an incomplete view, an unpublished request or a life no longer open.
- Schema 69: admin_end_account_life_v1 (admin role only) ends it at the
  region's latest commit and appends who and why to admin_life_endings.
- The account page shows End life for each published life not ended.
- A region refusing a birth because the account holds a cell (life_exists)
  could never record it: reject_primitive_life accepted reasons 1..3 only.
  The reservation stayed open and unpublished and refused every later
  birth. Schema 69 and the C++ wrapper accept existing_life (4).
- A region with no ticking cells ignored queued admin commands (such as a
  spawn) until something else woke it; a queued command now keeps it
  ticking until applied.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-29 07:32:08 -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.