Guided Local Workbench

Latticra Panel

Panel is Latticra's GUI-first installer and first-run control surface. It presents guided defaults, component choices, plan and receipt review, an embedded Console, and a dry-run-first path before any guarded user-local writes.

Panel Rule

Make the install path visible before it writes.

The Panel lane is intentionally narrow: dry-run mode is the default, authority status stays visible, receipts record what happened, and local-prefix writes require explicit guarded mode. The verified claim is user-local evidence, not root installation, distribution readiness, daily-driver safety, or runtime enforcement.

01

Open workbench

Start in the guided GUI with safe defaults and visible component selections.

02

Keep dry-run on

Generate the install plan while preserving denied host, root, network, and runtime authority.

03

Review evidence

Inspect plan details, component choices, engine log, embedded Console output, and receipts.

04

Enable guarded local mode

Only explicit local-prefix mode can write selected user-local wrappers, markers, config, and desktop metadata.

05

Verify locally

Confirm wrappers, prefix, payload tree, receipts, desktop entry, icon, launcher, and Seal report-only output.

First Impression

The GUI is the main operator-facing surface.

The protected design checkpoint names a maximized, resizable workbench with left navigation, central workspace, right Console/evidence panels, component tabs, authority tab, delivery controls, updater, evidence, and procedure views.

GUI first dry-run default no root
Latticra Panel visual asset for the guided local workbench.
Latticra Panel visual asset for the guided local workbench lane.

Evidence Snapshot

The successful install evidence is user-local and bounded.

These fields summarize the current public claim from the Panel local-install evidence records.

installer_present 1
user_local_install_verified 1
desktop_entry_present 1
receipts_present 1
root_authority 0
network_authority 0
runtime_enforcement 0
production_ready 0

Workspace Anchors

The UI is designed around inspection and control.

These protected anchors come from the Panel UI design checkpoint. They keep the app shaped like an operator workbench rather than a generic installer screen.

Dashboard

Build identity

Shows the current workbench posture, profile, authority state, and relevant local context.

Components

Selectable payloads

Guided profiles choose Lat, LIR, Seal, Nadia, Console, docs, examples, and developer helpers.

Authority

Visible boundary

Dry-run, local-prefix writes, network authority, manifest requirement, and receipt requirements stay explicit.

Delivery

Plan before action

Install behavior routes through plan preview, progress phases, receipts, and guarded local-prefix mechanics.

Updater

Managed updates

Updater preview/apply uses the guarded installer engine and keeps network fetch authority disabled.

Evidence

Human-readable receipts

Receipts record timestamps, profiles, prefix, authority state, component choices, and measurements.

Procedure

Stepwise operator flow

Procedure views keep dry-run, local mode, reset, uninstall, and verification steps visible.

Console

Panel-aware commands

The embedded Console supports quick metadata commands but is not an unrestricted shell.

Authority Boundary

The install button is real, but guarded.

Panel can run the installer engine and can write a user-local prefix only when the explicit safety posture allows it. That still does not make Panel a production installer or system manager.

Default mode

Dry-install validates configuration, checks the component manifest, generates a plan, and writes an operator receipt without writing the install prefix.

Guarded local mode

Explicit local-prefix mode may create selected user-local layout, component placeholders, markers, configuration files, CLI shims, desktop entry, and icon.

Denied claims

No root authority, system directory mutation, network authority, bootloader writes, kernel changes, systemd changes, SELinux changes, runtime enforcement, or production installer readiness.

Local Commands

Use these to inspect the guarded Panel lane.

The command examples are local developer checks. They do not expand the public install claim beyond the evidence records.

Run Panel from source

make -C installer gui

Dry-run and verify

make -C installer dry-run
make -C installer verify-local

Panel guard records

python3 scripts/check_latticra_panel_ui_design.py
sh scripts/test-latticra-panel-local-install-evidence-status.sh
sh scripts/test-latticra-panel-local-install-public-entrypoint-alignment.sh

Source Records

Read the exact record before repeating a Panel claim.