Implement M5.5 atomic terrain excavation and debris accounting

This commit is contained in:
dingo
2026-09-26 14:56:44 -04:00
parent 25ac646f93
commit 8b5bf48795
19 changed files with 770 additions and 30 deletions
+24
View File
@@ -0,0 +1,24 @@
# Excavation request digest v1
This defines digest input only, not a persisted file or network envelope. Never dump
native C++ structures. Request shape is validated before hashing; total input is bounded.
FNV-1a uint64 offset=14695981039346656037, prime=1099511628211; for each byte b:
`h = (h xor b) * prime modulo 2^64`. Every integer below is little endian.
| Order | Field | Width |
|---|---|---|
| 1 | Request contract version, literal 1 | u32 |
| 2 | Command ID | u64 |
| 3 | Destination ID, literal 1 | u32 |
| 4 | Cut count | u32 |
| 5, repeated in canonical cut order | Chunk x, y, z | three u64 conversions of signed coordinates modulo 2^64 |
| 6, per cut | Local x, y, z | three u32 |
| 7, per cut | Expected revision | u64 |
| 8, per cut | Removed fill | u32 |
Digest field is excluded. Canonical order is chunk lexicographic x/y/z then X-fast
local ordinal, with no duplicates. Store identity/descriptor is bound by the target
store, not this digest; neither digest nor revision authenticates a caller. M5.6 must
add world/frame/base versions, bounds, integrity checks and transaction framing to
its separately reviewed persistent format. Geometry, debris and retry metadata form
one consistent persistence unit; recording only a request digest cannot recover it.