← WI-069 Platform Foundations — app/edge API envelope + DTO boundary (implements the G12 invocation decision) ★ Live Board · Overview WI-071 P&C exit proof — e2e happy path (photo→table_hunt→item_scan→validate→rank→review→promote) + quarantine clean →

WI-070 · Platform & Contracts · scan-session-orchestration

Scan Session & Orchestration — session identity + candidate lineage + next-scan execution

queued P1 medium risk   Owner: Paul   Reviewer: Paul   0% · 0/1 tasks complete

Gates: P10 Requirements: — Updated: 2026-06-22

At a glance

CodeWI-070
PhasePlatform & Contracts
Order31 of 93
Story points13
Primary surfaceScan-session conductor (links P1/P2/P3/P4/P5/P8)
Retires—
Depends onFreeze scan I/O contract schemas + versioning
Blocks—
Evidence
queued (P10 — late P&C; conducts the pipeline)

Goals

Build the progressive-scan conductor: a scan session with stable candidate lineage across scans, and next-scan execution that turns P1 next_scan directives into the next request — resolving P1's deferred cross-scan identity.

Spec document

P10-scan-session → · source ↗

Implementation — what to build

Session + lineage

  • scan_session_id; candidate lineage across table_hunt -> item_scan -> mark_scan; result-local ID -> session lineage mapping.

Next-scan execution

  • Consume P1 next_scan; validate target/parent; create the next P1 request; trace-link rather than hold one span.

Handoff

  • Call P2 attempts, P3 trusted outcomes/recovery, P4 ranking when applicable; no untrusted/provider-native result bypasses P3/P4.

Checklist

  • ○ P10 Scan Session & Orchestration: scan_session_id + candidate lineage across scans, next-scan execution, P2/P3/P4/P5/P8 handoff, and the e2e happy-path proof (photo -> table_hunt -> item_scan -> validate -> rank -> review -> promote).

Gates & testing

  • ○ P10 Scan Session & Orchestration: scan_session_id + candidate lineage across scans, next-scan execution, P2/P3/P4/P5/P8 handoff, and the e2e happy-path proof (photo -> table_hunt -> item_scan -> validate -> rank -> review -> promote).
    CODE TEST HITL QA

Requirements

No linked requirements.

Verify (done when)

scan_session_id + scan-attempt IDs + parent/child candidate lineage; stable mapping from result-local P1 candidate IDs to session-level lineage; next_scan execution validates target/parent refs, creates the next P1 request, and preserves trace links (no one indefinitely-open operation). Resolves P1 cross-scan identity. Per P10 spec.

Cost triggers

No paid API / infra spend triggered by this item.

Status & editing

queued   Sprint: P&C Wave 5: Integration & Exit

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.