Skip to content

Mainframe Assist — Developer Wiki

Welcome to the developer wiki for Mainframe Assist, an auto-remediation platform for failed z/OS batch jobs.

What is Mainframe Assist?

When a batch job fails today, resolving it is manual and slow: an engineer reads spool output, works out the root cause, hand-edits the JCL or program, resubmits, and hopes. Mainframe Assist changes that loop end-to-end:

  • :material-alarm-light: Auto-capture

    A JES-spool watcher on the mainframe bridge picks up every failure the instant it happens — no ticket required.

  • :material-brain: Diagnose

    An agentic brain (Claude on Azure AI Foundry) reads the spool the way a senior SRE would and proposes a scoped, safe fix plan.

  • :material-account-check: Human-in-the-loop

    Every plan is gated, reviewable, and reversible. HITL chat lets the on-call approve, tweak, or reject before anything runs on the mainframe.

  • :material-check-decagram: Execute & verify

    On approval, the bridge applies the fix, resubmits, and verifies against explicit success criteria before marking the incident resolved.

  • :material-school: Self-learning

    Verified fixes graduate into a deterministic KB. Repeat failures are resolved at $0 with zero LLM calls.

  • :material-shield-check: Safe by design

    Every change is scoped, gated, and audit-logged in Firestore, with full replay through the /remediations cockpit.

Where to go next

Success metrics

Metric Goal
% failures auto-resolved E2E Fixed and verified without manual coding
Median time (failure → verified fix) Minutes, not hours
% fixes resolved at $0 Deterministic KB path, no LLM calls
Engineer hours per batch failure Trend down as KB grows

System at a glance

flowchart LR
  subgraph Mainframe
    JES[JES Spool]
  end
  subgraph GCP["GCP — autofix-*"]
    BR[autofix-bridge<br/>watcher + executor]
    ORCH[autofix-orchestrator<br/>lifecycle + HITL + KB]
    UI[lucent-ui<br/>/remediations]
  end
  JES -- failure --> BR
  BR -- digest --> ORCH
  ORCH -- HITL chat --> UI
  UI -- approve --> ORCH
  ORCH -- signed plan --> BR
  BR -- resubmit --> JES
  JES -- outcome --> BR
  BR -- verify --> ORCH

Contribute a page

Every markdown file under docs/ is a wiki page. Add a new one, wire it into mkdocs.yml → nav, and run ./deploy.sh from the wiki repo root. See Getting Started.