nogood-id-counter-is-monotonic
IN premise
`Network._next_nogood_id` only ever increases — deletion, clearing, save/load, and import never decrease it, preventing ID reuse after the issue #26 fix
Summary
Each nogood gets a unique numeric ID, and that counter never goes backwards. Even when nogoods are deleted, the database is cleared, or data is saved and reloaded, the counter keeps climbing. This prevents a subtle bug where a recycled ID could cause the system to confuse a new nogood with an old one that was already resolved.
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/29/tests-test_nogood_id.md |