nogood-id-collision-prevention
IN premise
After importing nogoods, `_next_nogood_id` is set to one past the highest imported ID, preventing `network.record_nogood` from generating a conflicting ID later.
Summary
When nogoods are imported from an external source, the system updates its internal counter to start numbering new nogoods above the highest imported value. This prevents a subtle bug where an auto-generated nogood ID could collide with one that was already imported, which would corrupt the conflict record.
Dependents
These beliefs depend on this one:
- nogood-ids-are-durable-and-collision-free — Nogood IDs form a durable collision-free sequence: the counter only increases (surviving deletions and clears), persists across save/load cycles via the network_meta table, and advances past imported IDs to prevent collisions — no operation can produce a reused or ambiguous contradiction identifier
Details
| Source | entries/2026/04/24/reasons_lib-import_beliefs.md |