User Guide

Purpose

This section is the main user-facing guide once the runtime is installed and verified. It explains the workflows people actually perform with bijux, not the internal implementation or maintainer review process.

flowchart TD
    A[Installed runtime] --> B[Run everyday commands]
    B --> C[Configure behavior and output]
    C --> D[Use plugins when needed]
    D --> E[Use the interactive shell when it helps]

This flowchart shows the intended order for practical use: learn the everyday checks first, then control configuration and output, then add plugins, and only after that reach for the REPL when interactive work is genuinely faster.

mindmap
  root((User guide))
    Everyday use
      help
      status
      doctor
    State
      config
      output formats
    Extensions
      install
      inspect
      check
    Interactive use
      repl
      history

The mindmap summarizes the same territory by theme. It helps readers jump to the right guide depending on whether their question is about daily operation, state and output, extensions, or interactive use.

Read This Set In Order

1. Everyday Commands
2. Configuration And Output
3. Plugins And Extensions
4. Interactive Shell And History

Scope

These pages are intentionally practical:

• they describe the workflows users can rely on today
• they avoid repeating architecture and contract material
• they are narrower than the full reference pages

Next Step

If you are still validating the runtime, go back to Getting Started. If you need the exhaustive command inventory, use the Command surface.