Skip to content

Mainframe Lab 01 · Reference architecture

Workflow Control Plane

A traceable flow for requests, checks, approvals, and handoffs—with explicit states instead of hidden automation.

n8nPostgresAPIsHuman approval

System map

Reference architecture flow

Reference architecture flow
  1. 01IntakeForm, email, or API
  2. 02ValidationSchema, required fields, duplicates
  3. 03OrchestrationRules, routing, retries
  4. 04ApprovalHuman decision for risky actions
  5. 05OperationsStatus, audit trail, alerts

Starting point

The problem this build examines

Requests arrive through forms and email, are checked manually, and then passed between several tools. Errors and follow-up questions are difficult to trace.

Approach

How the system is structured

The lab normalises inputs, validates required data, orchestrates the next steps, and pauses critical actions for human approval. Every run receives a status, owner, and audit trail.

Evidence

What this concept build demonstrates

How automation remains controllable: retry logic, an error path, approval steps, ownership, and an operations view.

Acceptance checks

  • Failures cannot cause silent data loss
  • Critical actions require approval
  • Every run has a status, timestamp, and owner
  • Restarting cannot create duplicate work

Typical handover

  • Process and data-flow diagram
  • Versioned workflow
  • Failure and recovery design
  • Runbook and handover checklist