challenge-id-auto-generation
IN premise
Auto-generated challenge IDs follow the pattern `challenge-{target}`, then `challenge-{target}-2`, `-3`, etc.; explicit IDs that collide raise `ValueError` rather than auto-deduplicating.
Summary
When challenge IDs are not explicitly provided, the system generates them automatically using a predictable naming scheme based on the target, appending incrementing suffixes to avoid collisions. However, if a user explicitly specifies an ID that already exists, the system treats this as an error rather than silently renaming it, which means explicit IDs are considered intentional and collisions signal a real mistake that needs human attention.
Dependents
These beliefs depend on this one:
- system-artifacts-maintain-consistent-identification — Both automatically-generated dialectical structures (challenge nodes with deterministic auto-ID generation) and contradiction records (nogoods with unconditional recording) maintain consistent, referenceable identification schemes — system-generated artifacts are as addressable as user-created beliefs.
Details
| Source | entries/2026/04/23/reasons_lib-network-challenge.md |