Cherry Creek Hospital Supply Annex
Back to World Models

Exact site

Cherry Creek Hospital Supply Annex

950 Josephine St, Denver, CO 80206

Listing metadata onlyHosted request-gatedPackage request-gatedCapture: Request-scopedReview: Request-scoped

Trust snapshot

Proof depthListing only
Public proofListing metadata only
Capture dateRequest-scoped
FreshnessRequest-scoped
StatusRequest-scoped commercial review

Package

$2,500

Hosted

Hosted request-gated

Proof

Listing only

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.

Listing metadata only

The public page shows site and pricing metadata, but not listing-specific exports.

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 supply room flow with cart loading, corridor return, and room restock points.

Cherry Creek Hospital Supply Annex site plan
Site codeSW-DEN-11
IndustryHospital supply
Workflow laneRestock, cart load, and room return
RuntimeVision + map state

Tasks in this world model

Pre-configured evaluation lanes for hosted review.

Load the cart, deliver to the room, and return through the clear corridor

Load the cart, deliver to the room, and return through the clear corridor

Base workflow lane tied to the exact site.

Base lane
Lighting variation

Lighting variation

Same site, adjusted lighting assumptions.

1.2 km est. path
Clutter variation

Clutter variation

Same route, more clutter and occlusion.

620 m est. path
Export review

Export review

Package and hosted outputs read back against the same exact site.

480 m est. path

Hosted evaluation preview

See the site through the review experience before moving into a deeper scoped session.

Site overview map
00Overview
Staging entry
01Staging
Capture proof
02Proof
Route lane
03Route
Restriction board
04Review

Proof of fidelity

Listing proof fields with request-scoped artifacts.

Capture proof
Warehouse still

Capture manifest

Session ID: cap-cherry-creek-hospital-supply-annex-v1
Frames: capture-backed
Coverage: Listing metadata only
Capture date: Request-scoped
Freshness: Request-scoped

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 currently shows the site, price, and trust fields, but not listing-specific screenshots or export previews.

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.

Harbor Mall Common Corridor

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

Corridor geometry preview with entrance, kiosk, elevator-bank, and seating-zone frames
Rights sheet showing public-common-area limits and store-entry exclusions
Export bundle tree with route notes, raw walkthrough pointer, and review memo

Guardrails

Capture common corridors only
Do not record inside individual stores without store permission
Avoid faces, children, security desks, and camera placements

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

Run 01Baseline aisle navigationRoute is readable through endcap and mid-aisle transitions.Keep lane in hosted review
Run 02Busy public aislePeople and carts create occlusion risk; privacy redaction remains required.Review only, no raw public export
Run 03Refrigeration approachLighting and reflective glass need a dedicated perception note.Add capture note to manifest
Run 04Checkout-adjacent exclusionRoute should stop before payment and identifiable-customer zones.Restricted zone attached

Export tree

manifest/site_package_manifest.json
rights/sample_rights_sheet.md
media/redacted_walkthrough_reference.mp4
routes/public_aisle_loop_waypoints.json
hosted/runs/run_01_observations.json
hosted/reports/sample_hosted_review_report.md

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.

Walkthrough video, timestamps, and camera poses
Site metadata, workflow notes, and provenance
Geometry / depth artifacts when available from source capture
Package manifest plus rights and privacy terms

Best fit

Teams that want all the site data in their own stack

$2,500

Request site package

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.

Streamed world-model runtime on one exact site
Reset, rerun, and scenario changes
Rollout exports, datasets, and raw bundles
Policy comparison on the same site

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.