the signals and their derived score are provisional and subject to change.
validate manually before sharing.
adad5f1e6cb49888644e520bcc5adfd4157d3d6343b6cd800ede5 months agoCo-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>cbb0f31326376 months agoCo-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>95bf7b6abfa16 months agoCo-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>0fe0490a39c26 months agoCo-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>73097fcdc6037 months agoCo-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>d55e2cf211917 months agoCo-authored-by: Copilot <175728472+Copilot@users.noreply.github.com># Snowflake IDs
Twitter-style packed integer IDs: `[timestamp | worker | sequence]`. The bit
layout is encoded in the type via const generics, so the ID and its generator
share the same layout parameters at compile time.
## Layout parameters
```rust
Snowflake64<const T: u32, const W: u32, const S: u32>
```
- `T` — timestamp bits
- `W` — worker/shard bits
- `S` — sequence bits
Constraint: `T + W + S <= 63` (top bit reserved to keep IDs positive for
systems that can't handle unsigned, e.g. Java or .gitignoreclaude-codeCLAUDE.md.gitignoreclaude-code.claude/