Sprint 5: Demand/Recovery POC - QR demand, watch/offer hooks, disposition, auction-outbound

At a glance

Goals

Sprint 5: Demand/Recovery POC - QR demand, watch/offer hooks, disposition, auction-outbound — advances F1, F2, F3, F4, F5 toward its gate(s).

Implementation — what to build

Checklist

• ○ F1 QR scan demand signal is captured.
• ○ F2 Watch/offer hooks are designed.
• ○ F3 Unsold routing and reconciliation outputs are connected.
• ○ F4 Disposition engine: buyer offers, disposition recommendations, and a responsible-disposal terminal route.
• ○ F5 Auction-outbound integration boundary exports unsold lots to external auction pipelines.

Gates & testing

• ○ F1 QR scan demand signal is captured.
  CODE TEST
• ○ F2 Watch/offer hooks are designed.
  CODE TEST
• ○ F3 Unsold routing and reconciliation outputs are connected.
  CODE TEST
• ○ F4 Disposition engine: buyer offers, disposition recommendations, and a responsible-disposal terminal route.
  CODE TEST
• ○ F5 Auction-outbound integration boundary exports unsold lots to external auction pipelines.
  CODE TEST

Requirements

• REQ-DEMAND-001 accepted QR scans should produce anonymous demand signals.
  Done when: Buyer QR scans create anonymous item interest signals (item_demand_signals) without exposing buyer identity.
  Spec: docs/product/post-sale-reconciliation.md · docs/product/capture-to-sale-tracking.md
• REQ-DEMAND-002 accepted Watch/offer hooks should be designed after scan demand is available.
  Done when: Watch and make-offer hooks are documented and connectable to item demand state; buyer_offers exists; live workflow activates with Auth (no payments).
  Spec: docs/product/disposition-engine.md (Make Offer)
• REQ-DEMAND-003 accepted Unsold routing and reconciliation outputs need to connect to tracked state.
  Done when: Demo routes unsold items and reflects them in reconciliation outputs (sold report, unsold/donation manifests, clearance/leftover plan).
  Spec: docs/product/post-sale-reconciliation.md (Outputs)
• REQ-DEMAND-004 implemented A disposition engine must route post-sale outcomes with explainable recommendations including responsible disposal.
  Done when: recommendDisposition() applies the documented priority ladder (wishlist->auction->republish->offers->consignment->clearance/donation) with shown reasons; responsible_disposal is a terminal route; buyer_offers + disposition_recommendations model the flow.
  Spec: docs/product/disposition-engine.md · docs/technical/data-model.md (Disposition)
• REQ-DEMAND-005 accepted Unsold lots must export to external auction pipelines as seller-reviewed packages (never auto-published).
  Done when: buildAuctionExportCsv produces a reviewed CSV (title/description/category/condition/suggested starting bid ~40% high est/reserve/tags/notes); auctions are channels, not competitors; nothing auto-publishes.
  Spec: docs/CC-Analysis/auction-outbound-integration-spec.md · docs/product/disposition-engine.md (AuctionNinja/HiBid)

Verify (done when)

demand signals + unsold routing + disposition + auction-outbound connect to reconciliation.

Cost triggers

No paid API / infra spend triggered by this item.

Status & editing

queued   Sprint: Sprint 5 - Demand/Recovery POC

Edit status / sprint on the ★ Live Board → — changes are logged live with who / when / why.

Human-in-the-loop

No human tasks linked.

Findings

None recorded yet.

Concerns

None recorded yet.

Risks

None recorded yet.

Tech debt

None recorded yet.

Tools used

No tool calls recorded.

Files & artifacts

No files / artifacts recorded.

Update log

No log entries yet.