Exact site
Harborview Grocery Distribution Annex
1847 W Fulton St, Chicago, IL 60612
Trust snapshot
Package
$2,400
Hosted
Hosted request-gated
Proof
Commercial exemplar with listing proof fields + request-scoped hosted request path
Capture
Request-scoped
Review
Request-scoped
Listing status
What is real, sample, and gated.
The listing is allowed to look polished without pretending every downstream artifact is open. Buyers should be able to see exactly what the public page proves and what still needs request review.
Visible now
Site metadata, workflow lane, pricing frame, trust fields, and request path.
Gated
Package files, raw exports, live hosted runtime, and listing-specific commercial proof open through request review and runtime readiness checks.
Why gated
Rights, privacy, freshness, and buyer context need to remain attached before access expands.
Commercial exemplar
A commercial listing with clear pricing, proof fields, and request-scoped follow-up.
Request-scoped proof
More proof can open after rights, privacy, and buyer context are reviewed.
Hosted request-gated
The hosted path is a commercial next step, but live launch still depends on entitlement, account type, and runtime readiness.
Package request-gated
Package access follows the normal request-specific rights and export review.
Site overview
A backroom layout with dock access, aisle replenishment paths, and a short handoff into shelf staging.
Tasks in this world model
Pre-configured evaluation lanes for hosted review.
Walk to shelf staging and pick the blue tote
Base workflow lane tied to the exact site.
Lighting variation
Same site, adjusted lighting assumptions.
Clutter variation
Same route, more clutter and occlusion.
Export review
Package and hosted outputs read back against the same exact site.
Hosted evaluation preview
See the site through the review experience before moving into a deeper scoped session.
Proof of fidelity
Listing proof fields with request-scoped artifacts.
Capture manifest
Restrictions and change
Know what is stable and what stays bounded.
Current public status
Commercially legible, but access still follows request-specific review.
Proof and fidelity
This listing is the commercial exemplar: real pricing, listing proof fields, and a clearer path into hosted evaluation request or package access.
Restrictions and change
Final access still follows the normal request-specific review, even when the listing looks ready.
Artifacts visible today
This listing shows site metadata, price, trust fields, and request-scoped paths. Screenshots or export previews open during follow-up when approved.
Example public capture
Harbor Mall Common Corridor
Shopping mall common areas / Sacramento, CA
Capture example
Public capture example for this listing.
This example shows what a robot team can inspect for a public-facing route: capture cue, capturer rules, robot question, hosted report rows, and export files. Listing-specific proof appears here when it is approved.
Capture app cue
$45 review cue, 30 minute walkthrough
Buyer
Evan Cho, Autonomy product manager
Capture mode
Public common-area loop
Evidence opened
Guardrails
Decision note
A buyer can keep the corridor in review while leaving storefront interiors out of scope until each store gives permission.
Hosted report rows
Export tree
Site package
Buy the site package.
Get all the site data for this exact workflow area so your team can run or build its own world model.
Best fit
Teams that want all the site data in their own stack
$2,400
Hosted evaluation
Configure a hosted evaluation request for this site.
Request a Blueprint-managed runtime session for this exact site when your team wants reruns, review, and exports without moving the package first. The next screen verifies account access, entitlement, and runtime readiness before anything launches.
Best fit
Teams that want Blueprint to verify a hosted run
Hosted evaluation is request-gated until site-world artifacts, entitlement, and runtime readiness are verified.
Next step
Ready to evaluate this site?
Request access to verify hosted evaluation readiness, or take the package path when your team wants the site data inside its own stack.