Learn the workstation basics

What this guide is for

This guide explains how to move around Arizmic and keep your place while you work. It covers the shared workstation shell, navigation, page tabs, inspectors, command search, layout, themes, and keyboard behavior. The individual product guides explain what to do inside Data Manager, Signals, Strategies, Studies, Results, Portfolio, Notebooks, AI Companion, and Live.

Read the workstation in layers

Most pages use the same structure:

1. Primary navigation moves between the main destinations.
2. Page tabs switch between stable views inside a destination.
3. Main workspace holds the table, editor, chart, form, or review surface.
4. Inspector or drawer shows details and actions for the selected item.
5. Top controls expose search, global actions, AI Companion, status, and other cross-cutting tools when available.

The shell stays consistent so changing from Data Manager to Results does not require learning a new navigation system.

Know the main destinations

The primary navigation is divided into two practical groups.

Strategy development contains:

• Signals for reusable calculations and their declared data needs;
• Strategies for complete decision and execution rules;
• Portfolio for reusable combinations of Strategy configurations;
• Studies for designing and following Strategy or Portfolio runs; and
• Results for reviewing completed Run Outputs and Study Results.

Workstation contains:

• Data Manager for Catalog, local import, API import, Prepared Data, stored runs, stored studies, and Study templates;
• Live for supervised deployments and their operational state;
• Notebooks for Marimo-based Python investigations;
• System & Jobs for Jobs, benchmarks, settings, credentials, models, and system information; and
• Activity Log for application events and support context.

These groups organize navigation only. A task can move between them without copying an object or starting a separate session.

Use page tabs

Page tabs belong to the current destination. For example, Data Manager uses tabs for Catalog and its import, preparation, and storage views. System & Jobs uses tabs for Jobs, Benchmarks, System Settings, credentials, AI Models, and Information.

Choose a tab when you intend to change the current workspace. Do not use the browser Back button as a substitute for a visible page tab. Back and Forward are most useful after following a deep link to a selected object or returning from another destination.

Understand remembered routes

Arizmic remembers the most recent Data Manager and System & Jobs tab during the current workstation session. Returning to the destination can reopen that tab instead of resetting to its first page.

Some links also carry a selected Dataset, Strategy, Study, Result, Portfolio, Job, or Live object. The destination validates that identity before showing it. If the object has been removed or the link is incomplete, the page should fall back to a clear unselected or unavailable state.

Select an item and use its inspector

Tables and libraries usually keep collection actions in the main workspace and item-specific actions in an inspector or drawer.

1. Select a row or card.
2. Confirm its name, type, version, and state in the inspector.
3. Review prerequisites and warnings before using an action.
4. Close or resize the inspector when you need more room.

An inspector does not create a second copy of the item. If the selected item changes version or disappears, refresh the owning page rather than relying on stale inspector content.

Resize and reset the layout

The primary rail and supported split panes can be resized with the pointer or keyboard. Collapse the navigation when a dense table or chart needs more room. Use the visible separator rather than dragging arbitrary page edges.

If accumulated pane sizes make a workspace difficult to use, choose Reset layout from Workstation actions. Resetting presentation does not delete Datasets, Strategies, Studies, Results, or other saved work.

Responsive layouts move rails and inspectors into drawers on narrower screens. The Docs website is mobile-friendly, but the desktop workstation is designed for the minimum display size in System requirements.

Use command search

Command search provides a quick route to destinations and supported actions. Open it with the displayed command-search control or its documented shortcut, then type a destination or task such as Prepared Data, Study Results, or AI Models.

Search results identify the destination and action before navigation. Command search does not search inside every Dataset, Strategy, Result, Activity event, or Notebook. Use the owning page's search and filters for those collections.

If a command is unavailable, go to the owning page and review its prerequisites instead of trying to bypass the disabled state.

Work with the keyboard

Shared controls follow standard keyboard behavior:

• Tab and Shift+Tab move through interactive controls;
• Enter or Space activates buttons and appropriate selected controls;
• arrow keys move within tabs, menus, and other composite controls where indicated;
• Escape closes a temporary menu, drawer, or dialog without confirming its action; and
• visible focus identifies the control that will receive the next action.

Dialogs keep focus inside while open and return it to the triggering control when closed. If focus disappears after a page change, return to the primary navigation or reload the route and record the problem for support.

Choose a theme and presentation

Use Workstation actions to switch between the supported day and night themes. Theme changes affect presentation only; they do not change calculations, charts' underlying values, or stored objects.

Use operating-system or application zoom to improve readability. At high zoom, expect secondary controls and inspectors to reflow or move into drawers. Do not reduce zoom merely to expose a control that should be reachable by scrolling or keyboard.

Arizmic respects reduced-motion behavior where supported. Color is not meant to be the only indicator of success, warning, or failure. Read the accompanying label and status text before acting.

Keep your place during long work

Starting a Job and navigating away are separate actions. A queued Study, import, or preparation task continues under System & Jobs -> Jobs unless it is canceled or fails. Use the active-job status in the application header and the Jobs page to follow it.

When a Job finishes, open the linked object in its owning destination. Do not assume that returning to the page where the request started will display the final Result automatically.

If navigation feels wrong

Continue with Core Objects and Versions to understand what moves between these destinations.