Scavenger
The cheapest listing may be the wrong part; the attractive vehicle may carry unanswered questions. Scavenger keeps a finite acquisition campaign open to inspection until its evidence supports a decision, a commitment, a parcel outcome, or an honest stopping point.
Contract
scavenger revision 3 publishes scavenger.plan_campaign@1, scavenger.observe_market@2, scavenger.qualify_candidate@1, scavenger.rank_candidates@1, scavenger.negotiate@1, scavenger.commit@1, and scavenger.receive@1.
A campaign begins with its revisioned subject profile, concrete need, known inventory, budget, deadline, region, evidence standard, source policy, and autonomy ceiling. It may return a durable campaign, reviewed field, explicit preference revision, shortlist, seller thread, negotiated outcome, commitment, parcel result, or diligence packet.
Scavenger owns criteria, observations, evidence, rankings, judgments, preference revisions, offers, commitments, parcels, inspections, and diligence alongside the campaign. Scout owns bounded acquisition/interaction receipts. The Magus retains private disclosure, final commitment, payment, acceptance, dispute, and every property transaction.
Unbounded scraping, spam, false identity or leverage, hidden criteria changes, professional certification, and unapproved commitment, payment, deposit, signature, or settlement remain outside the contract. Scavenger searches a finite market; Hunter instead adversarially challenges an already formed candidate.
Revision continuity
Revision 2 selected scavenger.observe_market@1 alongside the other six Pattern references.
It remains the historical finite-market design; its meaning is not rewritten into a new custody
or recovery protocol. Revision 3 keeps the application and those other references, and selects
scavenger.observe_market@2 for the explicit finite feed observation
request, retained whole field, deletion and recovery contract. The direct complete-seed admission
is part of that successor, not evidence that plan_campaign executed.
The tracked registry and application stores have no revision-2 Scavenger implementation or executable data migration. This records that source boundary; it does not claim knowledge of private implementations. State separately records registration and native acceptance. The first observation profile does not implement qualification, ranking, bargaining, commitment, receipt or preference learning.
Open the campaign
Campaign fixes the need and permitted consequence. Market follows the whole candidate field into evidence, ranking, and correction; Bargain takes approved questions to a seller. When exact terms are ready, Acquisition follows commitment into receipt, inspection, dispute, or diligence.