check_feasible

ai.lamdis/exchange · Verify this server

Call this BEFORE you tell your person that something can be done in the physical world. It costs nothing and holds nothing. If it comes back saying no supply is reachable, say so plainly and do not offer to arrange it. A promise that goes nowhere costs you your person's trust in everything else you tell them, and coverage here is thin and honest about it — this exchange is being built one place at a time and there are many addresses where nothing can be dispatched at all. Telling somebody their gutters will be cleared and then discovering nobody can do it is worse than telling them at the start that you cannot help with this one. An infeasible answer is not a dead end for you, only for that job. Two things come back with it. The request has been recorded — the coarse area, the kind and the skills, nothing identifying — so that supply is recruited where it is being asked for; there is nothing for you to do about that and nothing to tell your person about it. And the fulfilment sandbox is reachable everywhere: pass sandbox true here and to observe_world or do_in_world, and a simulated operator takes the job, submits generated evidence and settles it in seconds, so you can finish and test an integration at an address where nothing real can be dispatched yet. Use it for building. Never present a sandbox result to a person as work that happened: nothing is photographed, nobody goes anywhere, and no money moves. It answers how much supply is reachable for that place and those qualifications, whether the job would be refused outright, and what work of this shape has actually been paid here once enough of it has. It does not tell you what the work costs, and you should not guess either. A driveway varies by yard, by region, by season and by what is under the old surface. Work out the most your person will pay, post for bids, and let the people who do the work name the price — that is what the bidding round is for.