BLUE / Overview
Checking systems
BU
BLUE user
BLUE WORKSPACE

AI triage

Open source LLMQWEN3.8 Flash Next

Start a triage

Main ticket only
JiraPIMSConfluence
Total analyses—
Completed—
In progress—Queue + active work
System statusCHECKINGWaiting for health signal

Recent analyses

BLUE · RUNTIME MAP

BLUE Hub architecture

One clear path from trusted entry surfaces to evidence-based analysis and reviewable results.

Managed AI Hub
01
Single Hub identityShared queue and audit trail
02
Analysis-only entryPortal and CLI do not write back
03
Guarded comment pathExisting tag watcher only
REQUEST → EVIDENCE → RESULT

How one analysis moves through BLUE

request / readinternal runtimeguarded write

Portal HTTPS, WSL CLI or the company tag watcher sends a normalized request to one AI Hub. The Hub reads the main Jira, PIMS or Confluence record, skips linked tickets, videos and attachments larger than 10 MB, and sends scoped evidence to the native Windows open-source LLM running QWEN3.8 Flash Next. Results are shown in Portal history. Only the authorized tag watcher may use the separate company comment path.

01
Trusted entry surfacesAll routes become one normalized request
↗

BLUE Portal

HTTPS ticket intake, status and history review.

⌘

WSL CLI / local evidence

Local logs and evidence-folder analysis requests.

◆

Company tag watcher

Authorized tag-triggered route; the only comment writer.

02SINGLE IDENTITY

AI Hub

WSL service · queue · policy · audit

  1. Normalize and queueOne request identity, dedupe and durable job state.
  2. Read scoped evidenceAI Hub reads Jira · PIMS · Confluence. Main record only.
  3. Dispatch and recordBounded evidence bundle, model call and audit events.
Scope filterNo linked tickets · skip >10 MB attachments and video
03LOCAL INFERENCE

Native Windows runtime

Open source LLM

QWEN3.8 Flash Next

Local inference · advisory analysis only

The model receives the scoped evidence bundle; it does not receive a browser session or write authority.

04
Two controlled result pathsReview is the default outcome
✓

Portal result + history

Suggestion, evidence, gaps, timing and audit trail.

Portal reads
↪

Company comment write

Only the existing authorized tag watcher may post.

Guarded watcher · not Portal / CLI
◎

Read policy

Only the main ticket is reviewed. Linked records, videos and files over 10 MB are left out.

↗

Write policy

Portal and CLI prepare analysis. Comments are posted only by the approved watcher.

—

Available here

Ticket triage, local log analysis and review history are ready to use.

Analysis History

⌕

New Triage

Enter a Jira, PIMS or Confluence reference.

✓

Main record only. Linked tickets, videos and attachments over 10 MB are skipped.

What happens next

  1. Collect source evidence
  2. Analyze with the open source LLM
  3. Review the suggestion in History
Each Portal submission creates a separate analysis record and does not post comments.

Log Analysis

Upload a text log up to 100 MiB.

⇧

Drop a log here

or

Text logs only · ≤100 MiB · no dump / ETL / archive in Portal V1
EVIDENCE POLICY

Raw log stays local

The model receives bounded excerpts with source SHA-256 and line ranges. Omitted ranges remain explicit coverage gaps.

100 MiBhard upload cap
Hash-boundsource + excerpt integrity
TTL cleanupstaging is temporary

CLI setup & help

Submit logs and triage requests from your workstation.

⌘

Install BLUE CLI

Run one command in WSL / Linux. BLUE installs for your user, then asks for your access code privately.

curl -fsS https://blue-hostxxxx.tail4c6b73.ts.net/install.sh | bash && export PATH="$HOME/.local/bin:$PATH" && hash -r

Requires Python 3.10+ and curl. No sudo, pip or manual package download. Your access code is never part of the command.

Use it nowUse blue immediately after installing; no new WSL shell is needed. To check the connection, run blue doctor.
Your accountThe access code identifies your BLUE account. Each workstation gets its own credential; existing permissions and code expiry still apply.

Inspect installer · Manual download

QUICK REFERENCE

When to use which surface

PortalReview history, evidence gaps and live job events.
CLISubmit repeatable triage from a trusted workstation.
Log uploadStage text evidence locally with SHA-256 coverage.
BSOD / nativeComing soon · native worker is not mounted in this profile; /bsod is unavailable.
BLUE is a dedicated engineering workspace identity. It is not an official Dell product or brand mark.