ProspectSentinel · synthetic offline walkthrough

From incoming request to a reviewable next action

Real extraction and queue logic; scripted review decisions; no live data or actions.

Next action · September 16, 2026

Confirm the disputed approver before preparing a quote.
Owner: Synthetic operator · Open commitment

November follow-up: year unknown.
Referral source date: unknown.

How this guided replay works and what it does not verify

Entirely synthetic and offline. Capture validation, rules-based extraction and queue construction run the existing application functions. Review decisions, role conflict results and materialized rows are scripted fixtures illustrating the SQL review contract; the authenticated review RPC, database transactions and permissions are not exercised. No AI model, live source, workspace, quote ledger, load integration or outreach is connected.

Frozen scenario date: 2026-09-14. All names, text, IDs and dates are invented. Extraction version: broker-capture.rules.v1. Inspect persistent state · Inspect reconstructed queue

1. Capture the incoming request and referral

Use supported source types and explicit labels. The undated referral stays undated; collection time is not substituted for source time. Quoted history is ignored by extraction.

SYNTHETIC — incoming quote request

Source timestamp: 2026-09-13T14:00:00.000Z · Capture 1

Synthetic Orchard / Charleston, SC → Synthetic Market / Atlanta, GA · Reefer

Quote ID: SYNTHETIC-Q-001
Currency: USD
Response: requested
Requester: Synthetic Referral Desk
Shipper: Synthetic Orchard
Provider approver: Synthetic Orchard Procurement
Follow up on 2026-09-16 to confirm provider approval before preparing a quote.
Actual payer: unknown

SYNTHETIC — undated referral with conflicting approver

Source timestamp: Unknown · Capture 2

Synthetic Orchard / Charleston, SC → Synthetic Market / Atlanta, GA · Reefer

Provider approver: Synthetic Market Procurement
Contact in November to discuss the same lane.
Callback timing is not agreed.
> Provider approver: Ignored quoted history

2. Review exact excerpts

These are the real extractor's proposals with scripted operator decisions and fixture review results. The shipper is accepted against its excerpt. The two different approvers for the identical lane remain disputed. Requester identity does not establish authority; no approver is treated as verified.

Observation	Exact source excerpt	Extracted value	Fixture review result
1 · role	Shipper: Synthetic Orchard Capture 1 · 2026-09-13T14:00:00.000Z	{ "role": "shipper", "party_label": "Synthetic Orchard" }	accepted Checked the exact synthetic excerpt; accept only the role or timing precision it states.
2 · role	Provider approver: Synthetic Orchard Procurement Capture 1 · 2026-09-13T14:00:00.000Z	{ "role": "provider_approver", "party_label": "Synthetic Orchard Procurement" }	disputed Retain the explicit scoped claim, but the two sources disagree; neither approver is verified.
3 · commitment	Follow up on 2026-09-16 to confirm provider approval before preparing a quote. Capture 1 · 2026-09-13T14:00:00.000Z	{ "title": "Follow up on 2026-09-16 to confirm provider approval before preparing a quote.", "timing_precision": "day", "due_date": "2026-09-16" }	accepted Checked the exact synthetic excerpt; accept only the role or timing precision it states.
4 · gap	Actual payer: unknown Capture 1 · 2026-09-13T14:00:00.000Z	{ "question": "Who is the actual payer for this arrangement?" }	unknown Source does not establish this fact; leave the question open.
5 · quote	Quote ID: SYNTHETIC-Q-001 Currency: USD Response: requested Requester: Synthetic Referral Desk Shipper: Synthetic Orchard Provider approver: Synthetic Orchard Procurement Follow up on 2026-09-16 to confirm provider approval before preparing a quote. Actual payer: unknown Capture 1 · 2026-09-13T14:00:00.000Z	{ "quote_key": "SYNTHETIC-Q-001", "rate": null, "currency": "USD", "rate_type": "flat", "response": "requested", "conditions": "Quote ID: SYNTHETIC-Q-001\nCurrency: USD\nResponse: requested\nRequester: Synthetic Referral Desk\nShipper: Synthetic Orchard\nProvider approver: Synthetic Orchard Procurement\nFollow up on 2026-09-16 to confirm provider approval before preparing a quote.\nActual payer: unknown" }	accepted Checked the exact synthetic excerpt; accept only the role or timing precision it states.
6 · gap	Requester: Synthetic Referral Desk Capture 1 · 2026-09-13T14:00:00.000Z	{ "question": "Synthetic Referral Desk: can this requester award the quote, or is approval held by someone else?" }	unknown Source does not establish this fact; leave the question open.
7 · role	Provider approver: Synthetic Market Procurement Capture 2 · Unknown	{ "role": "provider_approver", "party_label": "Synthetic Market Procurement" }	disputed Retain the explicit scoped claim, but the two sources disagree; neither approver is verified.
8 · commitment	Contact in November to discuss the same lane. Capture 2 · Unknown	{ "title": "Contact in November to discuss the same lane.", "timing_precision": "month", "due_month": null, "timing_text": "November" }	accepted Checked the exact synthetic excerpt; accept only the role or timing precision it states.
9 · gap	Callback timing is not agreed. Capture 2 · Unknown	{ "question": "What is the agreed callback date or time window?" }	unknown Source does not establish this fact; leave the question open.

3. Keep timing precise and the next action persistent

The queue below is constructed by buildEvidenceQueue after reading state.json back from disk. The September 16 commitment has an explicit day. “November” has no year: neither a due month nor a day is invented. The undated callback remains an open timing question.

Follow up on 2026-09-16 to confirm provider approval before preparing a quote.

Owner: Synthetic operator · Status: open

Precision: day · Due date: 2026-09-16 · Due month: Unknown

Follow up on 2026-09-16 to confirm provider approval before preparing a quote.

Source timestamp: 2026-09-13T14:00:00.000Z

Contact in November to discuss the same lane.

Owner: Synthetic operator · Status: open

Precision: month · Due date: Unknown · Due month: Unknown

Contact in November to discuss the same lane.

Source timestamp: Unknown

Questions to resolve

Who is the actual payer for this arrangement?

Actual payer: unknown

Synthetic Referral Desk: can this requester award the quote, or is approval held by someone else?

Requester: Synthetic Referral Desk

What is the agreed callback date or time window?

Callback timing is not agreed.

Quote evidence, not an operational quote

The requested quote has an explicit request ID and currency, with no offered price (Unknown). Review acceptance means evidence was accepted; the commercial response remains “requested.” Nothing is sent, booked, priced or synchronized.

4. Reopen and prove persistence

From the repository run npm run evidence:walkthrough:replay. A separate process reads the saved fixture, checks its exact synthetic boundary, rebuilds the queue using the application function and verifies it matches queue.json. Re-running npm run evidence:walkthrough deterministically regenerates only these synthetic artifacts.

Operator close: retain both disputed approval claims; confirm the correct approver before preparing a quote. Keep the explicit next action and unresolved timing visible. This demonstrates an evidence workflow, not production readiness or live source coverage.