60Y · EXISTING BRIDGE CONSOLIDATION

Activation Spine Selected

This page consolidates existing TheoB bridge, browser, device, native, agent, vault, and System Index modules without changing the Arena shell look.

Existing modules to consolidate

Activation spine

1. Shell as canonical home candidate
   Arena Shell becomes the main TheoB operating surface when stable.
2. Prime to Agent Mission Control
   Founder/user intent becomes agent mission context.
3. Agent Mission Control to Bridge
   Agent mission becomes an executable work package.
4. Bridge to browser capability registry
   Browser/search/external-tab tasks are classified by capability.
5. Browser capability to device/native readiness
   Choose web tab, Chrome extension, native desktop helper, phone bridge, or provider API.
6. Vault and key settings
   User-chosen credentials, receipts, and memory are stored in the right vault surfaces.
7. System Index feedback
   The System Index records connected, planned, stale, and duplicate paths.
8. Center Arena coordination
   The center field shows mission/control state without changing shell icon language.

Machine receipt

# Existing Bridge Consolidation Patch

Wave: 60Y
Status: activation-spine-selected

## Shell
- Canonical surface: /agent-arena/shell
- Future home candidate: true
- Center role: mission control and agent coordination surface for routes, bridge work, browser/native/device state, Prime, agents, vault, and legal interpretation

## Selected Bridge Model
- Hybrid Shell + Real Browser + Extension/Native Candidate
- Major external account apps do not reliably run inside iframe previews. The shell should coordinate them, while real browser tabs carry user-owned sessions. A Chrome/native bridge is the later path for agent movement across tabs.

## Existing Modules To Use
- unified-search-browser-bridge-map: source-of-truth map for browser/search bridge selection
- arena-web-browser-capability-registry: define what browser actions are supported, blocked, or require native/extension bridge
- arena-device-bridge-readiness: phone, desktop, Bluetooth, USB, camera, microphone, external device path
- arena-desktop-capability-registry: define desktop shell capability classes and future native helper needs
- arena-shell-feature-flow-map: sequence the activation spine without adding duplicate UI
- agent-mission-control: agent-facing coordination layer for browser/native bridge work
- bridge: convert intent and route selections into executable work packages
- shell-tab-action-control: internal tab/action binding before external browser bridge
- key-settings: user-chosen credential/key storage surface; no automatic cookie/password import
- vault: receipts, memory, documents, and proof trail anchoring
- personal-vault: private user workspace memory and personal assets
- system-index: canonical map of live, connected, planned, stale, and duplicate systems

## Activation Spine
1. Shell as canonical home candidate — Arena Shell becomes the main TheoB operating surface when stable.
2. Prime to Agent Mission Control — Founder/user intent becomes agent mission context.
3. Agent Mission Control to Bridge — Agent mission becomes an executable work package.
4. Bridge to browser capability registry — Browser/search/external-tab tasks are classified by capability.
5. Browser capability to device/native readiness — Choose web tab, Chrome extension, native desktop helper, phone bridge, or provider API.
6. Vault and key settings — User-chosen credentials, receipts, and memory are stored in the right vault surfaces.
7. System Index feedback — The System Index records connected, planned, stale, and duplicate paths.
8. Center Arena coordination — The center field shows mission/control state without changing shell icon language.

## Next
60Z — Center Arena Activation Spine Receipt