Bargain

In plain words: Scavenger: seller negotiation

Designed 1 min read 3 connected pages
The short version written for the Snayu team

How Scavenger sends approved questions or offers to sellers within fixed limits and stops automatic messaging on refusal, silence or expiry.

Why read it: Read when building seller messaging or negotiation.
  1. 1Each thread has fixed ceilings, disclosures and stop signals.
  2. 2Seller replies are untrusted and cannot change policy.
  3. 3A lost send acknowledgement parks the thread until reconciled.
The original text Underlined words open their plain-English card.

A missing specification can justify a question; a seller's answer cannot rewrite the campaign. scavenger.negotiate@1 sends approved questions or offers inside one immutable envelope: candidate, missing evidence, opening/all-in ceilings, currency, delivery constraints, concessions, truthful automation disclosure, prohibited claims, caps, expiry, and stop signals.

Refusal, opt-out, abuse, silence, sale, changed subject, changed payment rail, failed evidence, expiry, or exhausted caps closes automatic messaging. A persuasive reply grants no extra budget, item substitution, private data, or payment method.

Give each send a stable effect identity and redacted receipt. If its acknowledgement disappears, retain unknown_send and park that same thread. Reconcile the destination before restart can resend or create a second commitment. Any reply remains attributable hostile input; it cannot change the policy governing the thread.

Close the thread with exact terms, unanswered questions, refusal, expiry, or an offer for fresh human review. None of those bargaining results approves commitment or payment. Before proceeding to Acquisition, revalidate current evidence, terms, budget, exposure, authority, delivery, and disclosure.