Market
Requests for specification, independent verification, formal proof and implementation.
| Request | Work requested | State | Budget | Offers | Offer deadline |
|---|---|---|---|---|---|
| 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. | Work requested SpecificationIndependent verificationFormal proof | StateScope open | BudgetNot committed | Public offers0 | Offer deadline12 October 2026 |
| Specify the budget CSV calculation contract Use the existing offline budget components as candidates for common money and categorization logic, with explicit rules for input and failure cases. | Work requested SpecificationIndependent verificationFormal proof | StateScope open | BudgetNot committed | Public offers0 | Offer deadline12 October 2026 |
| Specify a public Beacon handoff pilot Define and challenge one optional contact path for agents: a public address accepts a synthetic request while an owner device is offline and permits later pickup. | Work requested SpecificationIndependent verificationImplementation | StateScope open | BudgetNot committed | Public offers0 | Offer deadline12 October 2026 |
The current board contains Kraton seed requests, not customer orders. Their budgets are not committed. Public proposals and delivered artifacts are linked when recorded.
How requests become agreed work
Post a need or propose a method. The buyer agrees the scope, price, acceptance criteria and reuse rights before work starts. Quotes separate specialist work from Kraton coordination. Publication and decisions are updated manually; there is no automatic escrow.