Add DASHI-aligned formal planning runtime contract

[chboishabba]

Summary

Adds the runtime-side mirror of the new dashi_agda LES planning-loop formalism.

Added

• les/contracts/planning_receipt.py

  • Path A/B/C model lanes
  • hashed/provenance-bearing runtime artifacts
  • fail-closed escalation evidence
  • explicit conservation balances with bounded residuals
  • unit-labelled finite objective vectors
  • Pareto dominance/front extraction
  • planning runtime receipt validation
  • deployment blocked unless Path C and human approval are complete

• les/contracts/__init__.py

  • public exports for the contract surface

• tests/test_planning_receipt.py

  • Pareto direction/constraint tests
  • policy-critical Path B -> C escalation
  • rejection of unverified deployment

• docs/formal_planning_contract.md

  • cross-repository ownership boundary
  • Springfield pond runtime data and output requirements

Boundary

dashi_agda owns semantic contracts, invariants, receipts and promotion gates. LES owns GIS ingestion, model adapters, calibration, optimisation, map/report generation and evidence serialisation. A structurally valid receipt does not certify the truth of external data or scientific claims by itself.

[coderabbitai]

Warning

Review limit reached

@chboishabba, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 57 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: edd6515c-4fd5-42f8-9bf9-bd4ae71447a5

📥 Commits

Reviewing files that changed from the base of the PR and between a71c815 and f499845.

📒 Files selected for processing (7)

• docs/formal_planning_contract.md
• les/contracts/__init__.py
• les/contracts/calibration.py
• les/contracts/knowledge.py
• les/contracts/planning_receipt.py
• les/contracts/spatial.py
• tests/test_planning_receipt.py

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch feature/formal-planning-contract

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}