For organizations

Buy work that arrives as evidence.

Every packet states the place, the task, the proof that will be accepted, and the price, before anyone begins. What comes back is a receipt your own auditor can check without asking us.

This is not a separate product for organizations. It is the same public board every worker uses, seen from the side money enters. You name a need, or you attach money to a need somebody else named. You do not dispatch anyone and you do not decide what counts as done after the fact: the packet already says.

Where you enter

Two doors in, and one seat that is not yours.

Name a need. A building, a watershed, a site, a route, in plain words. You do not need to know what work it becomes: the packet is shaped in the open, where you can argue with the scope, the method, the proof rule and the price before committing to any of them. The same door a resident uses.

FUND The only step where money moves

Fund a packet at what the work is worth to you. There is no ceiling and no minimum. Paying above the ask is a premium the worker keeps.

attached across open packets

Your role. An organization is a buyer of evidence here. It is not an employer, not a dispatcher, and not a reviewer of physical proof. That seat belongs to a human who is admitted to it and who cannot review their own work.

Protocol adoption

One need, five decisions, one accountable record.

This is the institutional flow. Start with a place and a problem, or start by funding a packet already on the board. Stop whenever the next decision belongs to a human or to your own payment process.

  1. Name the needPlace and problem

    Choose one building, route, site, or ecosystem condition. Write the problem in plain language. The protocol shapes it into a bounded packet; it does not invent a site or dispatch a crew.

  2. Assign authorityPermission and safety

    Your site authority supplies access permission, local hazards, stop-work authority, licensed-professional boundaries, and the maintenance owner. These decisions stay with your institution.

  3. Read the packetScope and proof rule

    Before anyone starts, inspect the scope, exclusions, method version, acceptance rule, privacy level, evidence requirements, and declared funding path. If the packet is wrong, revise or stop.

  4. Choose the railFunding or earned record

    Fund through your own approved external payment process, or follow the packet's separate earned-credit path when no funder exists. Vealth does not hold escrow, move capital, or turn earned credit into money.

  5. Review and learnProof, receipt, maintenance

    A human reviewer accepts or returns physical proof. The record links the decision and any external payout. A maintenance steward owns follow-up, and a lapse is recorded instead of hidden.

One real packet

Live from the board, right now.

Not an example. This is whatever the board is offering at this moment, drawn by the same renderer a worker reads it through, or an honest absence.

Work packet

Reading DO Open the board

Nothing is claimed here until the board answers. Funding never changes who may claim this work.

Reading a live packet from the board…

Place
Proof required
Pay
Nothing pays before approved proof. Proposed until funded, and funded is never universally cash-payable.

Its own page appears here once the board answers.

What rides on it

The definition of done is written before the work starts.

That is the difference from a contractor invoice: the evidence a packet will be judged on is public before anyone begins, and the evidence against it is public afterwards. These hold for the packet above and for every other one.

Automating this instead of clicking it? The whole loop is available to an agent over one endpoint: vealth.net/mcp. Discovery, funding quotes and receipt verification are the same calls we use ourselves. Give it to your AI.

What comes back

Downstream of the packet, in the order it happens.

What we do not claim

The claim never grows larger than the evidence.