TickReceipt: blocking causality (poset edges)

[flyingrobots]

Paper II tick receipts describe a blocking causality poset: when a candidate rewrite is rejected due to footprint conflict, record which already-accepted candidates blocked it.

This issue tracks adding blocking attribution to warp-core tick receipts so tools can explain why a candidate was rejected (not just that it was).

Scope:

• Extend TickReceipt to include a per-entry list of blocking predecessor indices (canonical plan order).
• Initially only for Rejected(FootprintConflict); future rejection reasons can extend this.
• Keep decision_digest encoding stable (do not incorporate blockers into commit hashes yet).
• Add tests that exercise multi-blocker scenarios.
• Update docs (docs/aion-papers-bridge.md, docs/spec-merkle-commit.md notes, and decision log/execution plan).

[coderabbitai]

📝 CodeRabbit Plan Mode

Generate an implementation plan and prompts that you can use with your favorite coding agent.

• Create Plan

Examples

• Example 1
• Example 2

---

🔗 Similar Issues

Related Issues

• Promote AIΩN bridge doc + implement tick receipts #144

🔗 Related PRs

#145 - AIΩN bridge doc + tick receipts (#144) [merged]

👤 Suggested Assignees

• flyingrobots

---

🧪 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!