Project Phoenix

OpenClaw Operator Shell

Current status of the outer-layer integration: verified operator surfaces, hardening gate, incident workflow, and the first completed use-case bundle.

5
Live HTTP Surfaces
7
Completed Use Cases
2
Primary Papers Featured
4
Tracked Incidents (2 Resolved)

Current Position

Project Phoenix already had deterministic authority: grounded domain tools, solver-backed computation, and benchmark-backed evaluation. The missing piece was the outer layer — interface, monitoring, and workflow discipline. OpenClaw now fills that operator-shell role without becoming the authority.

What Exists

Five live operator surfaces, a hardening gate, screenshot and incident workflows, and deterministic script-backed packets for benchmark review, model comparison, routing policy, and run-trace triage.

What Changed

The line has moved from feature build-out into use-case expansion. The first seven-use-case bundle is complete and documented in the operator-shell architecture paper.

What Stays Fixed

OpenClaw is the shell. Phoenix remains the deterministic authority. The model never becomes the source of truth for correctness.

Operator Snapshot

AreaStatusCurrent read
Phase 2 presentationCompleteScreenshot pack captured and linked.
Phase 3 entry pointCompleteOpenClaw-invoked deterministic Phoenix surface is live.
Phase 4 monitoringCompleteSummary, status, workspace, and trends surfaces verified.
Phase 5 benchmark supportCompleteBenchmark summary is surfaced through the operator shell.
HardeningActivescripts/check_openclaw_hardening.sh is the default verification gate.
Use-case expansionCompleteFirst seven-use-case bundle completed on 2026-04-16.

Featured Current Papers

Paper 1.16

The Model Did Not Fail The Protocol, The Terminal Did

Primary paper on protocol capture integrity. Legacy ollama run terminal capture overstated thinking-model failures. Under clean REST API capture, gemma4:31b passes 6/6.

Operator Shell Pattern

Building on Project Phoenix Without Replacing It

Architecture paper for the OpenClaw outer layer and the first seven completed operator use cases. The shell reduces friction and enforces discipline without crossing the authority boundary.

The full inventory remains in canonical portfolio order. These featured papers are highlighted because they define the current OpenClaw/Project Phoenix line.

Live Surfaces

SurfaceRoleCurrent use
/phoenix-ops-summaryAuthority snapshotDeterministic system-state view.
/phoenix-ops-statusBackend healthOperator-facing backend and aggregate checks.
/phoenix-ops-workspaceCompression surfaceStarting point for operators; status, routing, screenshot, and incident context.
/phoenix-ops-trendsTrend reportingCompact view of recent movements.
/phoenix-benchmark-summaryBenchmark packetDeterministic benchmark exposure through OpenClaw.