Acquisition

A parcel arrives with the right tracking number and amount. Its contents and condition still need inspection. scavenger.receive@1 compares carrier, tracking, amount, expected identity, and package notes, then records acceptance, rejection, dispute, return, or loss. Cash on delivery (COD) alone proves neither what is inside nor its condition; the Magus makes the final payment, acceptance, dispute, and return decisions.

To judge the parcel, return to the exact terms freshly authorized through scavenger.commit@1. Property revision one never reaches that effect: it ends at a diligence packet, without contact, viewing, offer, reservation, deposit, signature, or settlement.

Keep the chain reconstructible. Campaigns, snapshots, score inputs, seller claims, messages, approvals, commitments, parcels, inspections, disputes, and diligence questions remain separately attributable. Checkpoints pin Pattern, source, selector, catalogue, parser, template, and policy revisions.

Restart reuses pinned observations and idempotency keys. Changed source state parks the occurrence; unknown commitment or send is reconciled before retry. Export separates private anchors, messages, evidence, and delivery data. Deletion disables schedules/sessions and inventories open commitments and disputes without pretending to erase the seller's copy.

Proving the campaign

Network-disabled Slovak fixtures cover a Bazoš RAM campaign and a two-room property campaign. Prove DDR4/DDR5 and SODIMM/UDIMM rejection, dated price intervals, bounded replies and stop rules, lost-acknowledgement recovery, deleted-listing uncertainty, reproducible score intervals, and restart without duplicate observations or messages. No live crawl, seller, credential, private coordinate, payment, deposit, signature, or professional query enters the proof.

Return to Scavenger.