Deterministic, order-independent ID allocation

[flyingrobots]

Salvaged from old Continuum crates/jitos-graph/src/ids.rs, preserved only in git history (formerly listed in GoodIdeas.md, now deleted).

Idea: deterministic ID allocation should be order-independent for independent operations.

• antichain swaps must not change identity
• IDs should come from normalized operation content, not accidental insertion order
• replay should reproduce identity exactly

Scope: Echo / git-warp runtime-internal concern, not a Continuum-owned contract. Filed here to preserve the idea before deleting the salvage note; move it to the owning runtime repo when picked up.

[flyingrobots]

Re-homing to Echo: deterministic runtime identity/allocation belongs with the causal runtime, not the Continuum coordination tracker.

[coderabbitai]

🔗 Related PRs

#153 - warp-core: policy_id plumbing + edge replay index [merged]

---

📝 Issue Planner

_{Check the box below or use the @coderabbitai plan command to generate an implementation plan and prompts that you can use with your favorite coding assistant.}

• Create Plan

---

🧪 Issue enrichment is currently in open beta.

You can configure auto-planning by selecting labels in the issue_enrichment configuration.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord!