01 Required
Color Palette
Colors are stateful. Accent hues map directly to execution intent, risk, and trust boundaries.
02 Required
Typography
Display stays technical, body stays readable, and mono owns all command-bearing UI.
Display / Chakra Petch
Orchestrate, Verify, Execute
Used for section headlines and shell identity where high recognition matters.
Body / IBM Plex Sans
Explain model behavior, summarize outputs, and document rationale in plain language without losing density.
Mono / JetBrains Mono
$ codex run --goal "patch login retry" agent.planner -> tasks:3 agent.reviewer -> risk:medium
03 Required
Spacing Scale
Compact rhythm optimized for dense telemetry while keeping read paths clear.
--space-1 / 6px--space-2 / 10px--space-3 / 14px--space-4 / 20px--space-5 / 28px--space-6 / 40px04 Required
Buttons
Actions encode safety level: execute, request review, or stop before side effects.
05 Required
Forms
Every prompt defines scope and permission policy before dispatching work to agents.
06 Required
Cards and Panels
Panel system is purpose-specific: intent, provenance, and post-run proof are separated.
Intent Panel
Clarifies objective and expected user-facing outcome before any tooling runs.
intent://refactor/auth/session-timeout
Provenance Panel
Shows source links, docs age, and command lineage for reproducibility.
proof://source-graph/7-edges
Rollback Panel
Captures snapshots and exact reversal commands when changes are deployed.
rollback://checkpoint/2026-02-23T19:24Z
07 Terminal Native
Terminal Components
Command stream blends human and agent events with explicit state and confidence context.
08 Terminal Native
Agent Panels
Agents expose role, utilization, and trust scope so operators can route work intentionally.
Codex Executor
write + testPlanner
decompose + orderReviewer
risk + regression09 Terminal Native
Execution Safety States
State language remains explicit, machine-readable, and operator-visible at all times.
- Read operations only
- No external writes
- Replayable command graph
- Write command detected
- Potential side effects
- Approval key required
- Policy rule violation
- Unsafe permission scope
- Automatic rollback prepared
10 Terminal Native
Confidence and Calibration
Confidence is paired with evidence and recency; this avoids false certainty and improves operator trust.
Patch Recommendation
0.82 calibrated
Evidence: 7 corroborating refs
Staleness: docs <= 21 days
Infra Migration Plan
0.64 exploratory
Evidence: 3 partial refs
Staleness: mixed recency
Release Rollback Path
0.93 verified
Evidence: runbook + dry-run pass
Staleness: validated today
11 Optional
Alerts and Notifications
Alerts are concise and actionable, always tied to a command or policy event.