Beta • Advisory-only by default

Pixsols Command Center — single path from chat to proof.

Start in Conversation Mode (3-model consensus + JEPA synthesis), promote proposals through Guardian, and see every plan and receipt in one place.

Single-page beta path

Land here, join beta, login with email + access code, and you are in the Command Center. No detours.

Conversation Mode

Advisory-only chat

Three-model consensus with JEPA-assisted synthesis keeps answers bounded. All calls write advisory receipts with consensus_record_hash linkage. No external effects.

Start here → ask questions → stay advisory until you promote.
Promotion Flow

Chat → proposal → Guardian

Promote any answer into a proposal. Guardian reviews, issues a token, and only adapters bound to that token may simulate or act. Receipts capture every hop.

Flow: chat → proposal → Guardian → token → adapter → receipts.
Plan Runner

Deterministic steps

Multi-step plans require precomputed hashes per step. Each step is gated, produces receipts, and surfaces provenance back into the Command Center.

No step runs without its hash and prior approvals.

Command Center tabs

After login you land directly in the Command Center. The tab strip mirrors the system pipeline so new users never guess.

Conversation

Default advisory workspace with 3-model consensus, JEPA notes, and hashes. Shows advisory budget and receipt pointers; no actions run.

Proposals

Promote chat into proposals, view Guardian decisions, and see the exact token envelope before adapters touch anything.

Plan Runner

Multi-step runs with per-step deterministic hashes. Each stage surfaces gate status, receipts, and what remains.

Receipts / Provenance

Receipt viewer with hash links, consensus_record_hash references, and export/verify links. Disk is the authority.

System

Explains Guardian, token, and adapter boundaries. Clarifies what is advisory, what is gated, and where proof artifacts live.

UI is advisory and non-authoritative. Pixsols does not ask for trust—verify every receipt yourself. Receipts on disk are the source of truth. Verification tools live at /verify.

Receipts and verification

Every proposal, decision, and plan step produces a receipt you can verify offline.

Receipts

Stored on disk with hashes and provenance. Conversation receipts stay advisory; Guardian receipts encode authority_effect.

Use the built-in viewer or export to verify.
Independent verification

Use pixsols-verify to check any receipt bundle offline. No hidden network calls.

Reference flow: Command Center → export → verify.
Fail-closed defaults

Unclear states freeze. No implicit approvals. Tokens bind to proposals and adapters; attempts without tokens are denied.

Guardian remains the sole authority.