26 lines
1.5 KiB
Markdown
26 lines
1.5 KiB
Markdown
# 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.
|
||
|
||
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.
|