WJb Docs - Basic

🧠 The Core Idea

WJb is built around one simple principle:

Workflows must be visible in code.

---

The Problem

Most background job systems hide important decisions:

Job
 ↓
Pipeline
 ↓
Middleware
 ↓
Retry
 ↓
Magic

As a result, developers often cannot quickly answer:

• Why did this job start?
• What exactly did it do?
• What will run next?
• Why was it retried?

The real workflow becomes scattered across configuration, attributes, and framework behavior.

---

The WJb Approach

WJb keeps the flow explicit and minimal:

Action
 ↓
Result
 ↓
Next Action

• An Action contains the business logic.
• The Result describes the outcome.
• The next step is decided directly in the Action.

Nothing is hidden behind pipelines or middleware.

---

Why This Matters

When the workflow lives in code:

• You can read it
• You can debug it
• You can test it
• You can change it safely

If you can open the Action and understand what happens next — the design is correct.

---

Simple Rule

If you cannot understand the workflow by reading the code,
the workflow is not explicit enough.

That is the core idea behind WJb.