Development record

docs/explanation/process.md promises collision impossibility where the code provides improbability. It calls the minted issue id 'collision-proof (iss-<yymmddHHMMSS><4 random digits>) that no parallel agent can duplicate'. recordid/mint.go:53 records the real property: Mint reads nothing, so two minters cannot converge by sharing a stale view, and 'only a same-second suffix coincidence remains, which is the armed uniqueness detectors' residue to assert (adr-45 ruling 5)'. There is no read-back and no retry, so two agents minting in the same UTC second collide with probability 1e-4. AGENTS.md already documents the sequential-id collision hazard for intents and specs; this page overclaims for the timestamp mint.