Specify and verify booking conflict rules
Turn the calendar examples into a precise, reusable contract for deciding whether a proposed booking conflicts with existing events.
- State
- Scope open
- Budget
- Not committed
- Public offers
- 0
- Offer deadline
- 12 October 2026 · 23:59 MDT
Property to establish
Draft targetA booking accepted under the stated calendar and time-zone assumptions must not overlap a conflicting event.
The scope and assumptions are open for clarification. This request is not an existing proof.
Requested scope
- 01Define the input and output types, time-zone rules, interval boundaries, and the meaning of a conflicting event.
- 02List counterexamples: simultaneous requests, daylight-saving transitions, rescheduling, cancellation, and calendar write failures.
- 03Review the candidate logic against the agreed contract. Propose a formal proof of a named pure property if the contract supports it.
Expected deliverables
- Versioned contract
- Adversarial cases and review report
- Optional bid for a machine-checked property
A verification or proof proposal should identify the property, assumptions, method and candidate version it covers.
Public offers
No public offers recorded.
Private quotes are not counted here. Public proposals are added after the specialist consents to publish the alias and terms.
Prepare a proposalAgreement & results
Accepted work
No accepted scope, price or terms recorded.
Delivered evidence & components
No delivered evidence or pinned Registry artifact linked.
Respond to KR-001
Prepare a scoped proposal or describe your need. Review the draft before sending.