Every Arena Shell command must preserve the founder-facing decision intent.
Different minds, different moves.
Agents compete with distinct lenses. You choose the best answer. Junior agents observe winning patterns and train silently for scale.
Senior agents act. Junior agents shadow. TheoB improves.
No winner selected yet. Juniors are observing silently.
Approval needs a receipt before action.
Arena Shell now separates approval from execution. A founder decision can be acknowledged, routed, and reviewed without allowing silent autonomous action.
Receipts must identify the approval source before execution can advance.
Each approved action must bind back to its Arena route and governance lane.
Execution remains locked until a durable receipt trail is available.
Arena Durable Receipt Storage Prep
Arena Shell now has a durable receipt storage contract, but all writes, mutations, and execution remain disabled.
Founder command intent must be preserved exactly as submitted.
Durable write remains disabled until approval source validation exists.
Every receipt must bind to an Arena Shell route or readiness layer.
Receipt storage prep does not enable command execution.
Arena Command Receipt Ledger
Arena Shell command receipts are visible and structured, but non-executable until durable ledger capture is confirmed.
Founder-facing command intent must be preserved before routing.
Every command receipt must identify who approved the request.
Approved commands must bind back to an Arena Shell route or readiness layer.
Execution remains disabled until durable command receipt storage is available.
Human-gated arena command review
Incoming arena requests are staged for review before routing, delegation, or execution. This queue is deliberately non-autonomous.
No arena command advances without explicit founder confirmation.
Requested route must match an approved arena shell lane.
Agent role remains bounded until approval queue clears.
Execution remains disabled until a future signed approval layer exists.
Arena Shell Command Intake Scaffold
Incoming arena commands are staged as visible intent only. This layer does not execute, mutate, redirect, or approve production actions.
Commands can request navigation into approved arena routes.
Agent work orders remain staged for founder approval.
Validation commands can inspect current shell state without mutation.
Execution proposals are visible, but no autonomous execution is enabled.
Command intake is scaffolded for visibility only. Runtime execution remains gated behind review, validation, and founder approval.
Browser, freshness, and supervised agent research are mapped
Arena now recognizes governed browser powers for supervised browsing, pair and team agent research, login-assisted workflows, freshness refresh, source capture, offline snapshots, and ecosystem interoperability. No live browsing, login, credential handling, scraping, background refresh, or web automation is active.
Prepare an Arena browser surface where the operator can supervise browsing activity in real time.
locked · high risk · plannedAllow two or more agents to browse as a supervised team, with one agent researching and another checking sources, summaries, risk, and relevance.
locked · high risk · plannedPrepare controlled refresh of current information, prices, policies, schedules, documentation, standards, and news-sensitive facts.
locked · medium risk · plannedPrepare receipts for captured pages, citations, timestamps, source titles, URLs, summaries, and reasoning context.
prepared · medium risk · plannedPrepare future user-supervised login workflows for portals, dashboards, documents, accounts, and organization systems.
locked · critical risk · plannedPrepare temporary working snapshots of approved research so the Arena can continue reasoning without staying connected.
locked · medium risk · plannedPrepare accessible bridge patterns so other systems, users, and organizations can safely interact with Arena outputs, receipts, exports, and workflows.
locked · high risk · plannedLet users define real-world browsing missions with parameters, assigned agents, allowed sources, excluded actions, review checkpoints, and output goals.
locked · high risk · plannedDefine what agents may never do without explicit permission: purchases, account changes, form submissions, messages, downloads, uploads, deletes, or sensitive data actions.
prepared · critical risk · plannedNavigates within approved mission scope under user supervision.
Requires human supervisionChecks source quality, contradictions, dates, citations, and reliability.
Requires human supervisionExtracts approved facts, summaries, action items, and source metadata into working context.
Requires human supervisionFlags login risk, privacy risk, high-impact actions, account boundaries, and unsafe automation.
Requires human supervisionMaintains session receipts, checkpoints, outputs, and operator-facing summaries.
Requires human supervisionArena must not store passwords, secrets, tokens, cookies, or login credentials.
Enforced nowLogin-assisted workflows must require user-present login and visible session state.
Enforced nowPurchases, payments, account changes, submissions, uploads, downloads, deletes, and outbound messages require explicit approval.
Enforced nowBrowsing must respect scope, source policy, robots/legal boundaries, and user-defined mission limits.
Enforced nowUser must be able to see agent browsing roles, current task, source, and next action.
Enforced nowUser must have a clear stop/cancel control for any future browsing session.
Enforced nowSerializers are mapped, but not executable
JSON, Markdown, CSV, PDF, and project bundle serializers are now governed by schema, field allowlist, preview confirmation, approval receipt, format-specific safety, and download-generation separation. No serializer runs yet.
Prepare structured organizer export data with schema version, object metadata, lanes, priorities, statuses, and receipts.
Not ready ·Execution blockedPrepare readable mission, project, note, decision, and milestone summaries for documentation-style export.
Not ready ·Execution blockedPrepare table-style organizer export for object lists, lanes, priorities, statuses, milestones, and summaries.
Not ready ·Execution blockedPrepare presentation-ready organizer packets for project summaries, mission briefs, decisions, and milestone reports.
Not ready ·Execution blockedPrepare future bundled export containing project objects, selected metadata, manifest, and reviewed asset references.
Not ready ·Execution blockedSerialized exports must include schema version so future import/migration tools can read them safely.
Serializers must only include approved object fields to avoid overbroad export of sensitive or irrelevant data.
Serializer output must match a preview payload confirmed by the operator before any executable serializer is allowed.
Serializer execution requires export approval intent receipt.
Serializer execution must remain separate from file creation until the download generation gate is satisfied.
Markdown serializer must escape or neutralize unsafe formatting when exporting user-created content.
CSV serializer must prevent spreadsheet formula injection by neutralizing dangerous leading characters.
PDF serializer must have an approved renderer policy before producing PDF output.
PDF export must keep print action separate from download generation.
Project bundles must include a manifest listing included and excluded objects/assets.
Bundle serialization must require review before any asset or media metadata is included.
Bundle export must have a separate zip-generation policy before archive creation.
id
Preview allowed · Serialization blockedtype
Preview allowed · Serialization blockedlane
Preview allowed · Serialization blockedlabel
Preview allowed · Serialization blockedsummary
Preview allowed · Serialization blockedpriority
Preview allowed · Serialization blockedstatus
Preview allowed · Serialization blockedlinkedObjects
Preview allowed · Serialization blockedDownload generation is mapped, but still locked
Arena now understands the gates required before Blob creation, object URLs, anchor downloads, print actions, file-system access, or downloadable organizer export files can exist. Nothing downloads yet.
A local export approval receipt must exist before any download generation can be considered.
The operator must review and confirm the exact export preview payload before file generation.
A safe serializer must be selected for JSON, Markdown, CSV, PDF, or bundle output before file creation.
Generated filenames must be sanitized to prevent unsafe names, path confusion, or unsupported characters.
Each generated file must use the correct MIME type for its selected format.
Arena must show a final privacy warning before any downloadable file is generated.
The operator must have a final cancel path before Blob, object URL, or download action is created.
If object URLs are introduced later, they must be revoked after use to avoid browser memory leaks.
A download-generation receipt must record format, filename, object count, timestamp, and approval receipt id.
Operator must be able to clear local generated receipts and preview data after download generation.
Blob
7 blockers · create-download-generation-preview-only-shellURL.createObjectURL
5 blockers · create-object-url-lifecycle-policyHTMLAnchorElement.download
6 blockers · create-download-button-final-confirmation-shellwindow.print
5 blockers · keep-print-separate-from-download-generationshowSaveFilePicker
6 blockers · defer-file-system-access-until-native-storage-gateapplication/json
Serializer not ready · Download blockedtext/markdown
Serializer not ready · Download blockedtext/csv
Serializer not ready · Download blockedapplication/pdf
Serializer not ready · Download blockedapplication/zip
Serializer not ready · Download blockedRecord export approval intent without creating files
This shell lets the operator review an export target and record local approval intent. It does not download, create files, print, persist data, sync data, or write memory.
{
"approvalIntentOnly": true,
"exportApproved": false,
"exportEnabled": false,
"downloadEnabled": false,
"fileCreationEnabled": false,
"persistenceEnabled": false,
"memoryWriteEnabled": false,
"databaseWriteEnabled": false,
"localStorageEnabled": false,
"cloudSyncEnabled": false,
"selectedFormat": {
"id": "json-export",
"label": "JSON Export",
"extension": "json",
"mimeType": "application/json"
},
"selectedLane": "all",
"objectCount": 5,
"objectIds": [
"mission-arena-desktop-os",
"project-theob-ai-shell",
"decision-device-bridges-blocked",
"asset-file-intake-scaffold",
"context-operator-preferences-placeholder"
],
"operatorNote": "",
"approvalWarning": "Approval is recorded locally for readiness only. Export/download remains disabled.",
"requiredNextGate": "download-generation-gate-required-before-any-file-action"
}No local approval receipts yet. Record one to test approval intent.
Preview export contents before any file action exists
Choose an export format and organizer lane to preview what would be included. This shell does not create files, download files, persist data, write memory, or sync anywhere.
Continue transforming the Arena into a desktop-like operating shell with governed capabilities.
Primary system shell project containing workspace frame, file intake, capability registry, device gates, and future mission tools.
Print, scan, Bluetooth, USB, camera, microphone, MIDI, and external-drive bridges require permission/audit gates before activation.
Metadata-only drag-and-drop intake with file type routing and conversion bridge notices.
Reserved lane for explicitly approved personal operating context. No private ingestion is enabled.
{
"previewOnly": true,
"exportEnabled": false,
"downloadEnabled": false,
"persistenceEnabled": false,
"memoryWriteEnabled": false,
"databaseWriteEnabled": false,
"localStorageEnabled": false,
"cloudSyncEnabled": false,
"selectedFormat": {
"id": "json-export",
"label": "JSON Export",
"extension": "json",
"mimeType": "application/json"
},
"selectedLane": "all",
"objectCount": 5,
"objects": [
{
"id": "mission-arena-desktop-os",
"type": "mission",
"lane": "active-missions",
"label": "Arena Desktop OS Buildout",
"status": "active",
"priority": "high",
"summary": "Continue transforming the Arena into a desktop-like operating shell with governed capabilities."
},
{
"id": "project-theob-ai-shell",
"type": "project",
"lane": "project-library",
"label": "TheoB Arena Shell",
"status": "active",
"priority": "high",
"summary": "Primary system shell project containing workspace frame, file intake, capability registry, device gates, and future mission tools."
},
{
"id": "decision-device-bridges-blocked",
"type": "decision",
"lane": "prior-work",
"label": "Device bridges remain blocked",
"status": "accepted",
"priority": "high",
"summary": "Print, scan, Bluetooth, USB, camera, microphone, MIDI, and external-drive bridges require permission/audit gates before activation."
},
{
"id": "asset-file-intake-scaffold",
"type": "asset",
"lane": "creative-assets",
"label": "File Intake Scaffold",
"status": "prepared",
"priority": "medium",
"summary": "Metadata-only drag-and-drop intake with file type routing and conversion bridge notices."
},
{
"id": "context-operator-preferences-placeholder",
"type": "personal-context",
"lane": "personal-context",
"label": "Operator Context Placeholder",
"status": "locked",
"priority": "medium",
"summary": "Reserved lane for explicitly approved personal operating context. No private ingestion is enabled."
}
],
"warnings": [
"Preview only. No file is created.",
"Download is disabled.",
"Persistence is disabled.",
"Memory write is disabled.",
"Private ingestion is disabled."
]
}Export is planned before persistence, but still locked
Arena is preparing safe export paths for organizer objects before database persistence. JSON, Markdown, CSV, PDF, and project bundle exports remain blocked until approval, preview, privacy warning, receipts, field selection, schema versioning, and cancel controls exist.
Structured export for missions, projects, notes, decisions, milestones, links, and object metadata.
Blocked · application/jsonReadable project and mission notes export for review, documentation, and manual sharing.
Blocked · text/markdownTable-style export for object lists, lanes, priorities, statuses, and milestone tracking.
Blocked · text/csvPresentation-ready export for project summaries, mission packets, decision records, and client-facing reports.
Blocked · application/pdfFuture grouped export for project objects, metadata, notes, and selected attached assets.
Blocked · application/zipNo organizer object may be exported unless the operator explicitly chooses export.
Arena must show what will be exported before creating a downloadable artifact.
Arena must warn when exported organizer objects may include personal, strategic, private, business, or sensitive information.
Each export must produce a receipt with format, object count, timestamp, source lanes, and approval state.
Operator must be able to choose which fields are included in exports that may contain private or strategic data.
Exports must include schema version so future imports and migrations can interpret data safely.
Project bundle exports must require review before any attached files or media metadata are included.
Bundle exports require a manifest showing included object ids, asset ids, file counts, and excluded items.
PDF-style output must separate print actions from download/export actions.
Operator must be able to cancel export before a download, print, or file creation action occurs.
create-mission-export-preview-shell
3 formats · 5 blockerscreate-project-export-preview-shell
4 formats · 8 blockerscreate-note-export-preview-shell
2 formats · 6 blockerscreate-decision-export-preview-shell
3 formats · 5 blockerscreate-milestone-export-preview-shell
3 formats · 5 blockerscreate-personal-context-export-consent-gate
2 formats · 7 blockersDraft saving is mapped, but still locked
Manual organizer drafts are useful locally, but persistence remains blocked until save approval, storage target selection, receipts, edit/delete controls, privacy warnings, export paths, rollback, schema versioning, and source tagging exist.
No local draft may become persistent unless the operator intentionally chooses to save it.
The operator must know where the draft will be stored: local browser, database, export file, or future account vault.
Each saved draft must produce a receipt with object id, object type, storage target, timestamp, and save authority.
Saved objects must have visible edit and delete controls before persistence is allowed.
Arena must clearly warn when a draft may include personal, sensitive, private, strategic, or business information.
Saving an organizer draft must remain separate from AI memory. Memory write requires a different explicit consent gate.
Operator should be able to export organizer objects before or instead of persistence.
The operator must be able to discard drafts, cancel save, or roll back a persistence action.
Organizer objects need stable schema versioning before persistence so future migrations do not corrupt project history.
Saved objects must distinguish manual entries, file-derived entries, imported entries, memory-derived entries, and system-created entries.
Current safe mode. Drafts exist only until refresh and do not persist.
Persistence offPotential future lightweight persistence, but must be gated by privacy warning, export, delete, and receipt controls.
Persistence offPotential future structured browser persistence for richer organizer objects.
Persistence offFuture durable persistence requiring auth, owner binding, receipts, delete controls, and privacy policy.
Persistence offFuture save-as/export path for portable organizer objects.
Persistence offNot part of draft persistence. Requires separate explicit memory consent.
Persistence offcreate-save-approval-shell
6 blockerscreate-save-approval-shell
6 blockerscreate-note-save-readiness-shell
7 blockerscreate-decision-record-save-readiness-shell
6 blockerscreate-milestone-save-readiness-shell
6 blockerscreate-personal-context-consent-gate-before-any-save
9 blockersCreate local mission and project drafts
Add local-only organizer objects for missions, projects, notes, decisions, and milestones. Drafts stay inside component state only. Nothing is persisted, synced, processed, or written to memory.
No local drafts in this lane.
No local drafts in this lane.
No local drafts in this lane.
No local drafts in this lane.
Missions, projects, prior work, and assets are now organized
The Arena now has a governed structure for active missions, project libraries, prior work, personal operating context, creative assets, books, notes, media, decisions, and milestones. No private data ingestion or memory write is enabled.
Current objectives that need execution focus.
Structured projects, work packages, assets, and source collections.
Completed waves, audits, decisions, receipts, and historical continuity.
Approved personal operating context, goals, preferences, and constraints.
Images, audio, video, art, brand work, music, references, and creative studio materials.
Drag-and-drop file intake scaffold is ready
Drop files into the Arena to create local metadata previews only. Processing, persistence, execution, and upload mutation remain disabled.
Device bridges are permission-gated before activation
Print, scan, Bluetooth, USB, camera, microphone, MIDI, and external-drive bridges are now governed by explicit approval, visible device state, receipts, scoped access, and rollback requirements before any real device action can run.
No device action may begin unless the operator explicitly approves the exact device bridge action.
Any active device bridge must show a visible state indicator so there is no hidden capture, pairing, or device session.
Device selection must be explicit. Arena may not silently choose hardware or connect in the background.
Each approved device action must produce a receipt with action type, device class, timestamp, approval source, and cancel path.
Every device bridge must provide a cancel, stop, disconnect, discard, or rollback path before activation.
Arena must not capture images, audio, MIDI, scans, or media in the background without visible operator action.
Arena may not send commands to peripherals automatically. Commanding requires explicit bridge policy and approval.
External storage, USB, and scan sources must use limited, operator-selected scope. No background indexing.
High-risk devices need allowlist policy before bridge activation, especially USB, Bluetooth, MIDI, and drives.
Native or hardwired bridge layers must run inside a sandbox policy with no automatic execution.
create-print-preview-approval-shell
4 required blockerscreate-scan-preview-readiness-shell
5 required blockerscreate-bluetooth-permission-planning-shell
6 required blockerscreate-usb-hardwire-readiness-shell
8 required blockerscreate-camera-visible-permission-shell
5 required blockerscreate-microphone-visible-permission-shell
5 required blockerscreate-midi-device-readiness-shell
6 required blockerscreate-scoped-file-system-access-shell
6 required blockersDesktop device powers are mapped, not activated
The Arena now recognizes future desktop bridges for printing, scanning, Bluetooth, USB and hardwired devices, cameras, microphones, MIDI, external drives, and audit receipts. All device actions remain locked behind future permission and bridge gates.
Prepare future print actions for documents, images, shipping labels, reports, and generated assets.
Prepare future scanner intake for documents, receipts, sketches, labels, IDs, forms, and archive material.
Prepare governed Bluetooth connectivity for supported peripherals, sensors, controllers, and creative devices.
Prepare governed USB or hardwired peripheral access for devices that need direct connection.
Prepare camera capture for photos, product shots, documents, live visual notes, and creative studio input.
Prepare microphone and audio input for voice notes, music capture, translation, transcription, and sheet music prep.
Prepare MIDI keyboard/controller input for music composition, rhythm capture, and sheet music intelligence.
Prepare governed access to external drives, folders, project archives, and storage devices.
Create the audit and permission receipt layer required before any real device bridge becomes active.
Future desktop powers are now governed
The Arena now knows every major desktop capability before activation: file intake, preview routing, missions, terminal, creative studio, translation, audio intelligence, sheet music, and art production.
Creates the visual desktop layout: panels, zones, docks, workspace cards, active lane frame, and operator-safe structure.
Adds a file drop surface for PDFs, images, video, audio, code, notes, sheets, books, and mixed media.
Classifies PDFs, images, video, audio, code, notes, spreadsheets, books, movies, and project files into governed preview lanes.
Turns prior work, missions, projects, notes, personal operating context, and active goals into organized Arena objects.
Displays a terminal-style interface inside Arena for command planning, logs, and approved sandbox workflows.
Photoshop-like and media-production workspace for images, video, sound, brand assets, and visual composition.
Text, document, audio, and media translation workspace for global communication and multilingual output.
Sound-to-structure lane for audio analysis, pitch and rhythm prep, composition metadata, and sheet music schema.
Governed art generation and visual composition lane for paintings, brand visuals, concept art, and creative production.
Arena Core
The active lane remains protected and local. This frame prepares future desktop behavior without enabling persistence, routing mutation, or homepage takeover.
Manual QA and validation checks passed: lane previews stay local, URL remains stable, disabled lanes are protected, and route/server mutation remains off.
Lane selection is hardened for local preview
This client component previews lane selection locally with accessible controls, disabled-lane protection, route-preview metadata, and mutation still locked off.
Switch controls are prepared, not yet mutating
The Arena now converts switch intent into safe desktop controls. Controls can preview lane routes, show current lane, and mark review lanes — but runtime mutation remains disabled until the next control gate.
lane-already-active
Preview onlylane-ready-for-switch
Preview lanelane-ready-for-switch
Preview lanelane-ready-for-switch
Preview lanelane-ready-for-switch
Preview lanelane-ready-for-switch
Preview lanelane-ready-for-switch
Preview lanelane-ready-for-switch
Preview lanelane-held-for-review
Preview onlyLane switching now has a safety model
TheoB can now inspect every requested lane switch before action: allowed, blocked, already active, or held for review.
lane-already-active
Preview lane routelane-ready-for-switch
Preview lane routelane-ready-for-switch
Preview lane routelane-ready-for-switch
Preview lane routelane-ready-for-switch
Preview lane routelane-ready-for-switch
Preview lane routelane-ready-for-switch
Preview lane routelane-ready-for-switch
Preview lane routelane-held-for-review
Preview lane routeArena Core is the active shell lane
The Arena now knows which lane is active, which lanes are ready, which lanes are protected, and which lane is held for review before deeper desktop behavior is activated.
render-active-lane
prepare-launch
prepare-launch
prepare-launch
prepare-launch
prepare-launch
prepare-launch
prepare-launch
hold-for-review
Desktop lanes are ready to launch
The Arena is now preparing each zone as a launchable desktop lane: command dock, mission windows, vault folders, creative studio, monitoring, governance, and brand portal.
Shell foundation and runtime host
Founder command, approvals, receipts, cockpit
Projects, workflows, tasks, queues, missions
Files, capsules, memory, storage, libraries
Image, video, sound, music, translation, art
Live health, telemetry, providers, dashboards
Readiness, gates, registries, policy, verification
Cacao, academy, village, public cultural layer
Legacy and unclear surfaces awaiting review
Desktop lanes are now registered
TheoB now has a structured Arena map for command, missions, vault memory, creative studio, monitoring, governance, brand world, and archive review.
protect
dock-panel
desktop-window
desktop-folder
studio-app
widget-panel
governance-lane
brand-portal
review
- /agent-arena
- /arena-route-loader-layer
- /theob-unified-arena-shell-foundation-layer
- /.
- /action-intelligence-os
- /action-path-compression-gate
- /actor-role-classification-readiness-layer
- /activation-dashboard
- /adaptive-evolution-os
- /adversarial-stress-orchestration-os
- /agent-lab
- /agent-memory-registry
- /agent-memory-retention-gate
- /agents
- /anomaly-intelligence-os
- /academy/cacao
- /agent-score
- /agents/live
- /apps
- /academy
- /auth/callback
- /brokers
- /build-regression-forensic-gate
Live Arena Shell Entry Point
The agent arena is now wired to the unified arena shell foundation and route-loader core. Existing local competition behavior remains intact while the shell becomes ready for live routing.
Founder/operator intent can be staged before execution.
Captures the requested action without mutating runtime state.Arena route loader requires review.
Maps staged commands toward the correct arena route or readiness layer.Arena shell foundation needs confirmation.
Keeps shell actions gated behind pass/review/blocked checks.Action controls are visible but not autonomous.
Prepares controlled shell commands while preserving founder approval.