Mission Control

About Command Deck

Mike's standalone mission control. Reads the LZ manifest, provides working tags/lists/search/sort, opens apps in an embedded viewer. All state saved to LZ KV cloud — identical on every device.

How Edit Mode Works

Command Deck separates browsing (free, instant, no saves) from editing (batched, one cloud save when done). This prevents wasteful network calls while ensuring nothing is ever lost.

The flow

• Tap ✎ Edit to enter edit mode. An amber bar appears.
• Make all your changes — reorder lists, tag apps, set nicknames, create tags.
• Every change saves to your device instantly (localStorage draft). If the app crashes or your phone dies, the draft survives.
• When you're done, tap Save — one cloud write, everything synced.
• Or tap Discard to revert all changes since you started editing.
• If you reopen the app with an unsaved draft, you're prompted to resume or discard.

What requires edit mode

• Creating, renaming, deleting, or reordering lists
• Adding or removing apps from lists
• Creating or deleting tags
• Applying or removing tags on apps
• Setting or clearing app nicknames

What never needs edit mode

• Opening and using apps
• Searching, filtering, sorting
• Syncing the manifest
• Viewing the About or Data Safety tabs

Source Code Backup — How & Why Tokens Are Preserved

The problem

Storing source code alongside app data means any Claude who opens the app's KV data would load the entire HTML file into their context window, consuming thousands of tokens before any work begins. This is wasteful and can exhaust Claude's context on large apps.

The solution: on-demand loading with a version index

Source code is stored under separate KV keys (cd-source-v1, cd-source-v2, etc.), NOT inside the main state key. The main state key (command-deck) contains only lightweight data — tags, lists, nicknames. A separate index key (command-deck-source) contains a tiny JSON array of version metadata: version number, date, file size. No source code in the index.

When a Claude needs the source, they fetch one specific versioned key on demand. When they don't, the source is never loaded. The About tab only shows the version list (metadata) — the full source loads behind a "View" button that a human taps deliberately.

Limitations

• 25MB per key: KV values max at 25MB. The Command Deck HTML is ~56KB, so this is fine. But if it grew past 25MB, it couldn't be stored in a single key.
• No diffing: Each version is a full copy. 10 versions = 10× the storage. At 56KB each, this is negligible, but worth knowing.
• No encryption: Anyone who knows the KV key pattern can read the source. This is Mike's private infrastructure so it's acceptable, but the data is not encrypted at rest.
• Eventually consistent: KV writes can take up to 60 seconds to propagate globally. A backup made in London might not be readable in Sydney for a minute.
• Single platform: All backups live in Cloudflare KV. If Cloudflare has a catastrophic incident affecting the KV namespace, all versions could be lost simultaneously. See the Data Safety tab for mitigation.

Architecture Reference

For Claude — repair/extend

Single HTML file. No build step. Fetch source from cd-source-v{N}, edit, deploy with wrangler pages deploy . --project-name=command-deck --branch=main. State shape: tags[], appTags{}, lists[], appNicknames{}, savedAt. Manifest from GET /apps. Apps via iframe to /apps/{id}/html.

Source Code Versions

Data Safety Assessment

An honest look at where your data lives, what's protected, what's vulnerable, and what you should do about it.

Where Your Data Lives

What You Should Do

Single Points of Failure