Reviewable actions
Prepare and check
Each action shows its exact effect and receives a short-lived hash before it can run.
Prepare configuration Generate local files; do not activate →
Build review plan Validate and create an exact hash →
Check health Read-only policy and service checks →
Activation stays outside this page. Applying a plan, approving cloud egress or machine work, restoring backups, and handling recovery keys keep their separate operator boundary.
Long-running local work
Deep Work
Checking
Checking the content-free local work view.
Draft a long-term goal Not loaded
Open the exact private URL printed by ./pixel ui to load locally admitted inputs and enabled work types.
Draft only. Goals can branch and converge through an acyclic dependency graph; Pixel still runs one bounded eligible milestone at a time and advances only after independent evidence. This form cannot choose host paths, admit files, compile or stage jobs, start or resume work, approve network access, or broaden policy. Exact draft creation follows its enforced permission mode: inline approval, bounded automatic execution, or denial.
Review created goals Not loaded
Open the exact private URL printed by ./pixel ui to inspect retained goal drafts.
No retained goal drafts are loaded.
Evidence before narration. Every card below is reconstructed from exact owner-private custody on this host. It shows what Pixel would attempt, how success is checked, and the maximum authority and resources involved. Separately enabled exact confirmations may prepare an inactive launch package, stage dormant ready custody, and render an inactive event-driven supervisor; they expose no host paths or input identities, cannot install or activate a service, and cannot start work, schedule execution, call a model, or contact a provider.
Long-term goal Not connected
Milestones Not available
Durable checkpoints Not available
Next supervisory step Not available
Progress model Durable events, not a clock
Watchdog role Liveness and interrupted-work recovery only
Aggregate runtime Not available
Model requests Not available
Local token processing Not available
Recorded failures Not available
Remaining goal capacity
Calculated from settled milestones plus the latest observed usage of the active session.
Milestone starts Not available
Runtime Not available
Model requests Not available
Input tokens Not available
Output tokens Not available
Network transfer Not available
Artifact storage Not available
Failures Not available
Event-driven restart safety and independent verification are not connected.
Pause future milestones The current bounded step may finish; only future scheduling is paused →
Resume the reviewed goal Starts no work immediately; the next event-driven cycle reuses only exact paused custody →
Cancel when safely settled Available only when no live worker is hidden and cleanup or pre-launch revocation is provable →
Active sessions 0
Needs attention 0
Produced artifacts 0
Service concerns 0
Service health
The Deep Work controller is not connected.
Private knowledge Not connected
The encrypted local knowledge vault is not connected.
Storage Encrypted locally; no provider fallback
Key custody External runtime credential; never sent to a model
Add a source Review exact private bytes before one confirmed admission
Delete a source Review one exact source; retain a content-free tombstone
Historical backup Reconcile later deletions before restored knowledge can activate
Safe source lifecycle
Keep the title and source in owner-private local files.
Run ./pixel work-knowledge-guide add from the trusted terminal with the exact local vault, source, owner, classification, and retention options.
Inspect the plain-language review, then type its short exact APPLY phrase. Any source or vault drift cancels the confirmation.
Use setup, find, remove, rotate, or reconcile for the other guided operations. Rotation and historical reconciliation additionally require the controller to be offline.
Local and explicit. This page never receives source text, titles, file paths, vault keys, or deletion authority. It cannot retrieve, ingest, delete, rotate, or restore knowledge. The plain-language trusted-terminal guide keeps those sensitive operations outside the browser while preserving exact review and confirmation.
Sessions
No Deep Work sessions are projected.
Candidate and verifier review Not loaded
When a Scout, Researcher, or Data Lab milestone is waiting for judgment, load its exact retained report, acceptance criteria, evidence excerpts, and independent verifier limits here.
Load private candidate review
Disabled in the private control policy.
Private, read-only review. This token-gated loopback view can show owner-authorized work content and relative evidence references. It never shows host-absolute paths or credentials, sends nothing off this machine, and cannot accept, complete, publish, deploy, or widen the work. Acceptance remains an exact trusted-terminal action.
Content-free with checkpoint-bound lifecycle controls. The status view has no job authority. Separately enabled pause, resume, and safe-cancel actions each require an exact fresh review and confirmation. They cannot stop or hide a live worker, expand access, reveal private evidence, or open artifacts.
Safety and maintenance
Operator-enabled actions
These actions are absent until enabled in the owner-only control policy. Sensitive configuration is never shown here.
Check for updates Public registry metadata only; no download or activation →
Create encrypted backup Configured destination and age recipient stay private →
Emergency pause reason
The exact reason is bound into the preview. Do not enter a credential or private content.
Pause Operations Stops new machine execution; resume remains in the terminal →
Pause Frontier Stops new provider egress; resume remains in the terminal →
Fail-closed by default. Update checks, backups, and emergency pause are disabled until an operator installs a private policy. Resume, restore, approval, credential, and activation authority never enter the browser.
Active boundaries
Capability map
Loading capability boundaries…
Local-first routing
Frontier budget
Frontier status is not available
No active budget window
Provider route Not available
Provider setup Not available
Billing boundary Not available
Budget evidence Not available
Jobs Not available
Input tokens Not available
Output tokens Not available
Failures Not available
Cost Not priced locally
Totals only. Prompts, job IDs, account details, and credentials never enter this status projection. Pixel budgets are an additional local stop; they do not replace ChatGPT workspace limits or API Platform billing controls. Approvals still require inspecting the exact private plan outside the browser.
Exact local inspection
Frontier reviews
Load pending sanitized capsules only when you are ready to inspect them on this screen.
Load pending reviews
Disabled in the private control policy.
Review only. This page cannot approve or transmit a capsule. Close screen sharing and consider untrusted browser extensions before enabling this private view.
Local queue
Needs attention
Source changes —
Operations approvals —
Frontier approvals —
Local fit check
Pixel Doctor
Checking
Checking rounded local readiness.
Host contract —
Processor tier —
Memory tier —
Free storage tier —
Accelerator —
Model starting point —
Context starting point —
Accelerator approach —
Generated model —
Configured context tier —
Reasoning mode —
Exact fit —
Readiness checks have not loaded.
Advisory and local only. Values are rounded to reduce fingerprinting. No hostname, serial, device name, model identifier, URL, path, process output, credential, network probe, or provider call enters this view. Exact model fit still depends on model size, quantization, context, and accelerator memory.
Release workspace
Updates and migration
Checking
Checking private release-workspace shape.
Current release —
Candidate releases —
Prepared workspaces —
Rehearsed workspaces —
Activation workspaces —
Migration check —
Next safe step —
Orientation, not authority. This view checks only private filesystem shape. It never claims a signature or migration has passed and never shows paths, hashes, signers, sources, or receipt content. Verification, activation, rollback, recovery, and cleanup stay in the trusted terminal.
Disaster recovery
Backup, recovery, and resume
Checking
Checking content-free recovery receipts.
Backup policy —
Latest backup creation —
Next backup step —
Incident recovery —
Operations resume —
Frontier resume —
Trusted terminal recovery sequence
Validate the exact backup: ./pixel restore /ABSOLUTE/BACKUP.tar.gz.age --identity /OFFLINE/AGE-IDENTITY --validate-only
Rehearse into a new empty root: ./pixel restore /ABSOLUTE/BACKUP.tar.gz.age --identity /OFFLINE/AGE-IDENTITY --rehearse /NEW/EMPTY/ROOT
Review the isolated result and automatic safety-backup destination before an exact --replace --confirm restore.
For containment, follow INCIDENT-RESPONSE.md, inspect broker authority state, and resume only with ./pixel ops-resume "reviewed reason" --confirm or ./pixel frontier-resume "reviewed reason" --confirm.
Terminal-only safety boundary. This page never reads a backup, decryption identity, private incident evidence, or current broker pause state. It cannot rehearse, restore, recover, or resume anything. A recorded successful pause is only a reason to inspect terminal state—not proof that authority is still paused.
Private-safe orientation
Diagnostics
Checking
Checking local incident receipts.
Content-free guidance. This view never shows private logs, action identities, local paths, prompts, accounts, credentials, or evidence hashes. Inspect private evidence only from the trusted host.
Attribution
Recent local actions
No control actions recorded yet.