This file is the top-level product overview for AllocDB.
For the detailed product docs, read:
AllocDB is a deterministic database for allocating scarce resources under contention.
It exists to make "one resource, one winner" a first-class primitive for tickets, seats, inventory, rooms, and compute slots.
These are product requirements, not implementation preferences:
- Determinism first.
- Boundedness first.
- Assertions for programmer errors, result codes for operating conditions.
- Allocation-free steady-state execution is the target for the Rust trusted core.
- Single-node correctness comes before replication.
The current shape is intentionally narrow:
- single-node, single-shard execution
- logical-slot TTLs
- bounded idempotency window
- bounded reservation-history lookup
- no trusted-core metadata
holder_idrequired forconfirmandrelease
- product.md: problem statement, goals, non-goals, success criteria
- semantics.md: resource model, reservation lifecycle, API contract, consistency
- principles.md: TigerStyle adapted to AllocDB and Rust