# Runtime Path Selector

Wave: 61B
Status: selector-ready
Commit: 926a199

## Purpose
Select the correct runtime path for each mission type without rebuilding the Arena Shell or adding new browser widgets.

## Runtime Paths
- Internal Route → available · readiness pages, dashboards, receipts, vault views, system index views
- API Receipt → available · machine-readable status, text receipts, agent handoff summaries
- External Browser Tab → available-through-user-browser · Vercel, GitHub, ChatGPT, Supabase, OpenAI, WhatsApp, PayPal, banking, streaming
- Provider API Candidate → candidate-requires-source-budget-scope · weather, search, finance, sports, maps, email, calendar, payments
- Chrome Extension Candidate → candidate-not-built · tab observation, user-approved browser handoff, page context transfer, cross-app workflow assist
- Native Helper Candidate → candidate-not-built · desktop automation, local file workflows, device bridge, screen context, keyboard/mouse assist
- Phone / Device Bridge Candidate → candidate-not-built · iPhone handoff, notifications, camera/mic bridge, Bluetooth/USB device work

## Mission Types
- Observe system state → internal-route + api-receipt · System state already lives inside TheoB routes and receipts.
- Open external account app → external-browser-tab · Major account apps block iframe embedding and need user-owned sessions.
- Fetch live public data → provider-api-candidate · Use approved providers with source, budget, freshness, and scope.
- Coordinate agent work → internal-route + api-receipt · Agents need traceable receipts before execution.
- Move across browser tabs → chrome-extension-candidate · A website alone cannot safely control arbitrary browser tabs.
- Operate desktop/device → native-helper-candidate + phone-device-bridge-candidate · Desktop and device control need explicit local/native bridge.

## Visual Policy
- New shell icons added: false
- New shell panels added: false
- Browser widget added: false

## Next
61C Runtime Path Selector Shell Binding Receipt