See what works, what is bounded, and what still needs a real connection.

Internal windows are compositor-owned. Native apertures require the desktop companion and follow a separate S10 owner.

Search owns queries and sourced results; typed URLs do not belong to Search.

Contained navigation works where providers permit it; frame-blocked pages require the connected desktop companion or an explicit external handoff.

The queue persists in browser-local storage and never activates an agent or navigates until the user opens an item.

Launchers request a Browser destination. They do not authenticate, read cookies, copy secrets or grant protected-action authority.

The visible workflow and local receipts work; several external transport, identity and durable-ledger adapters remain gated.

The governed alternatives render behind internal Arena surfaces.

The Electron viewer proof is functional; geometry authoring is a different unconnected capability.

Identity, operational readiness, capability and mission evidence are reconciled read-only. The Stable does not deploy agents.

Local window planning, expiry evaluation and external handoff export work. Founder authority binding, background scheduling, merge, credentials and production deployment remain disconnected.

Local queue analysis and recorded validation receipts work. Automatic decisions, source changes, test execution, merge, scheduling and deployment are disconnected.

Free-first planning, local evidence caching and explicit Search handoff work. Live provider orchestration, credentials, paid action, background jobs and provider success claims remain disconnected.

Browser-local capability storage, import/export, evolution and review receipts work. Content execution, credentials, canonical Vault persistence, activation and deployment are disconnected.

The browser-local layout model is interactive and can inspect live route context, but it never mutates the live shell, routes or production.

Browser-local creation, recovery, context review and promotion-candidate receipts work. Tested does not mean production-ready; consolidation, scheduling and deployment remain disconnected.

Local blueprints and export work; canonical identity, verified training and deployment remain separate.

Browser-local inspection and packaging work. Durable storage, malware scanning, rights review and public exchange are not connected.

Local contract composition works. Live provider execution and canonical token storage are not connected.

The envelope, Search handoff and local brief work. Research is never claimed until evidence is attached.

Fail-closed review and revocable receipts work. Approval and activation-ready states do not mean an agent is running.

Browser-local evidence and temporary-artifact adapters work. Public Search, providers and consequential action adapters are disconnected.

The route is visible, but safe arbitrary-file parsing and native translation are deferred.

David Goldin may display as Prime Founder, but the profile designation does not grant the Founder role or consequential authority.

No verified authoring runtime is present.

Resolved in Checkpoint 156A. Git history preserves the retired legacy implementation.

Resolved in Checkpoint 156B: Browser, Queue, External Account Launchers, Key Master and Founder Controls now have separate owners.

Do not describe readiness ledgers as live execution owners.

Keep Foundry available for building, combining, testing and proving surfaces. Promote verified outputs through governed receipts without renaming S5 or retiring the Foundry.

Permanent internal build, composition, testing and proof capability. It remains available after verified outputs are promoted into governed features.

Manual read-only public research and scholarly Crossref lanes can return cited results. No polling, scraping, spend or consequential action is implied.

The Action/Pulse compositor stores at most 40 source receipts in browser sessionStorage. This is not a universal or durable cache.

No verified universal cache runtime exists. The cached-web provider is a planning candidate selected only when callers report cached evidence.

The visual compositor, categories and bounded probes work. General live feeds, polling, subscriptions, persistence and background refresh remain disabled.

Planning context, source lineage and browser-local handoffs exist across several subsystems, but there is no single durable project/topic/mission context runtime.

The intended deployment target exists, but the Live Pulse registry explicitly disables drag/drop runtime.

Prime can call a model when configured and suggest routes. It is not yet connected to current System Truth, route ownership, projects, missions, dependency effects or a unified Context Mesh.

Current persistence is browser-local or session-local, not authenticated durable storage.

Public Search, credentialed provider and consequential adapters are explicitly disconnected.

Founder authority is not inferred from the Prime Founder profile.

Viewer controls must not be labeled as geometry authoring.