A fair process needs visible rules.

Push keeps both sides working from the same scope, the same status and the same record of what happened.

The assignment lifecycle

Brief openWorker selectedScope acceptedWork submittedApproved and settled

Rules built into the product

One account, either role

A member may hire and work from one account, but cannot apply to their own brief.

The brief becomes evidence

The hiring account may edit an open brief only before the first application. After that, the terms are preserved.

Applications remain private

Only the applicant and the hiring account can read a proposal. Public profiles remain optional.

Selection is exclusive

One applicant may be selected for the current assignment. A second assignment requires a new brief.

The worker accepts the scope

Selection alone does not begin the work. The worker must accept the preserved scope, deadline and budget.

Payment follows a named route

The hiring account selects bank/card simulation, USDC simulation or Stellar testnet USDC. Push does not hold funds in this prototype.

Delivery has a review step

The worker submits evidence against the agreed deliverables. The hiring account may approve it or request a specific revision.

A dispute freezes completion

Either participant can open a dispute before approval. Normal settlement then stops until a future resolution process exists.

Settlement must be verifiable

For Stellar testnet, Push verifies the network, asset issuer, recipient, amount, assignment memo and transaction success.

Reputation must come from evidence

Future ratings should follow completed assignments and verified participation. Push will not sell rankings or invent activity.

What Push does now

Accounts, private profiles, briefs, applications, assignment records, submissions, revisions, disputes and testnet settlement verification.

What remains undecided

Production payment providers, platform fees, dispute arbitration, refunds, identity checks and the first supported countries.

What Push will not do

Issue a proprietary token, collect wallet recovery phrases, or mark a payment complete without the required evidence.